SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
Search
Test your basic knowledge |
Agile Development
Start Test
Study First
Subject
:
it-skills
Instructions:
Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can
study here
.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.
This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Reported gains in quality - productivity - and business satisfaction. Agile development has been widely seen as being more suitable for certain types of environment - including small teams of experts.
Agile Negative Impacts : Force Feeding
Agile Success
Iteration Review
PM Declaration of Interdependence (DoI)
2. Some methodologies focus on development practises (XP) - others focus on the management of the software project (SCRUM).
CMMI (Capability Maturity Model Integration)
Agile Methodology Variations
DOI : Value
Agile Principle : Excellence
3. Customer satisfaction by rapid delivery of useful software.
Agile Principle : Frequent Delivery
Working Software
Agile Principle : Rapid Delivery
Agile Iteration
4. Customer collaboration over contract negotiation
Agile Principle : Self-Organizing
Daily Team Meet
Individuals and Interactions
Agile Priority : Customer Collaboration Vs Contracts
5. In agile development - self-organization and motivation are important - as are interactions like co-location and pair programming.
Individuals and Interactions
Daily Team Meet Style
DOI : Tailor
Agile Methodology Variations
6. Mission-critical systems where failure is not an option at any cost (e.g. software for surgical procedures).
Agile Iteration
Agile Negative Impacts : Mission Critical
Agile Principle : Frequent Delivery
Agile & Continuous Testing
7. Large-scale development efforts (>20 developers) - though scaling strategies and evidence of some large projects have been described.
Agile Negative Impacts : Large
Agile's Ideal Project Type
Daily Team Meet Style
DOI : Shared Responsibility
8. Improve effectiveness and reliability through situationally specific strategies - processes and practices."
Agile Negative Impacts : Force Feeding
Method Tailoring
DOI : Tailor
Agile Priority : Customer Collaboration Vs Contracts
9. Dxpect uncertainty and manage for it through iterations - anticipation and adaptation.
Agile Principle : Co-location
Agile Criticism
DOI : Uncertainty
Agile Negative Impacts : Mission Critical
10. An iteration might not add enough functionality to warrant a market release - but the goal is to have an available release (with minimal bugs) at the end of each iteration. Multiple iterations might be required to release a product or new features.
DOI : Value
Agile Iteration Vs Release
CMMI (Capability Maturity Model Integration)
Quality / Agility
11. Sustainable development - able to maintain a constant pace.
DOI : Individuals
Agile Principle : Sustainable pace
Agile & Continuous Testing
Responding to change
12. Forcing an agile process on a development team.
Agile Principle : Rapid Delivery
Agile Principle : Self-Organizing
Responding to change
Agile Negative Impacts : Force Feeding
13. In contrast - focus on planning the future in detail. A predictive team can report exactly what features and tasks are planned for the entire length of the development process. Predictive teams have difficulty changing direction. The plan is typicall
Agile Negative Impacts : Large
Agile & Planning
Agile Negative Impacts : Distributed Locations
Predictive Methods & Change Predictive methods
14. Deliver reliable results by engaging customers in frequent interactions and shared ownership.
Team Stakeholder Representative
Agile Principle : Co-location
Working Software
DOI : Engagement
15. One of the differences between agile and traditional testing methods - such as the waterfall model of software design - is that testing of the software is conducted at different points during the software development lifecycle.
Agile & Continuous Testing
Team Stakeholder Representative
CMMI (Capability Maturity Model Integration)
DOI : Individuals
16. Responding to change over following a plan
Responding to change
Method Tailoring
Agile Priority : Responding to change Vs Plans
Iteration Benefit
17. Distributed development efforts (non-colocated teams). Strategies have been described in Bridging the Distance[40] and Using an Agile Software Process with Offshore Development
Agile Principle : Simplicity
Agile Software Development
Agile Negative Impacts : Distributed Locations
Agile Principle : Daily co-operation
18. Agile development is focused on quick responses to change and continuous development.
Iteration Review
Responding to change
Agile Principle : Co-location
Agile Negative Impacts : Distributed Locations
19. Working software over comprehensive documentation
Predictive Methods & Change Predictive methods
Daily Team Meet
Agile Priority : Working Software Vs Docs
Working Software
20. Welcome changing requirements - even late in development
Agile Priority : Customer Collaboration Vs Contracts
DOI : Shared Responsibility
Quality / Agility
Agile Principle : Changing Requirements
21. Face-to-face conversation is the best form of communication (co-location)
DOI : Uncertainty
Agile Principle : Simplicity
Agile Principle : Co-location
Agile Principle : Sustainable pace
22. An adaptive team will have difficulty describing exactly what will happen in the future. The further away a date is - the more vague an adaptive method will be about what will happen on that date. An adaptive team cannot report exactly what tasks the
Agile & Predictions
DOI : Uncertainty
Agile Principle : Rapid Delivery
Agile Principle : Adaptation
23. Regular adaptation to changing circumstances
Agile Negative Impacts : Large
Agile Iteration Vs Release
Agile Principle : Adaptation
DOI : Value
24. Continuous attention to technical excellence and good design.
Agile Principle : Excellence
DOI : Individuals
Iteration Benefit
Team Stakeholder Representative
25. Projects are built around motivated individuals - who should be trusted
Agile Principle : Motivation & Trust
DOI : Individuals
Agile Software Development
DOI : Shared Responsibility
26. No matter what development disciplines are required - each agile team will contain a customer representative. This person is appointed by stakeholders to act on their behalf and makes a personal commitment to being available for developers to answer
Agile Iteration
DOI : Value
Team Stakeholder Representative
Agile Criticism
27. Minimizes overall risk and allows the project to adapt to changes quickly.
Cross-Functional Team Sizes
Agile Principle : Excellence
Agile Priority : Customer Collaboration Vs Contracts
Iteration Benefit
28. Behaviour Driven Development where the scenarios are written before the code and form part of an automated suite of tests that can verify whether the code meets the required functionality and/or quality standards.
Method Tailoring
Agile Priority : Interactions Vs Processes
Agile Principle : Sustainable pace
Behaviour Driven Development
29. These meetings - sometimes referred as daily stand-ups or daily scrum meetings - are held in at the same place and same time every day and should last no more than 15 minutes. Standing up usually enforces that rule.
Working Software
Daily Team Meet Style
Team Stakeholder Representative
Agile Principle : Co-location
30. Working software will be more useful and welcome than just presenting documents to clients in meetings.
DOI : Uncertainty
Quality / Agility
Working Software
CMMI (Capability Maturity Model Integration)
31. Working software is delivered frequently (weeks rather than months).
Agile's Ideal Project Type
Agile Principle : Frequent Delivery
DOI : Value
Team Stakeholder Representative
32. Boost performance through group accountability for results and shared responsibility for team effectiveness.
Agile Principle : Self-Organizing
DOI : Shared Responsibility
Customer collaboration
Agile Principle : Adaptation
33. Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning.
Agile Principle : Co-location
Agile & Planning
Agile Principle : Simplicity
Daily Team Meet Style
34. At the end of each iteration - stakeholders and the customer representative review progress and re-evaluate priorities with a view to optimizing the return on investment (ROI) and ensuring alignment with customer needs and company goals.
Agile Principle : Self-Organizing
Agile Software Development
Iteration Review
Agile Negative Impacts : Force Feeding
35. A group of software development methods based on iterative and incremental development - where requirements and solutions evolve through collaboration between self-organizing - cross-functional teams. Encourages rapid and flexible response to change.
Agile Principle : Sustainable pace
Agile Principle : Changing Requirements
Agile Principle : Adaptation
Agile Software Development
36. Most agile implementations use a routine and formal daily face-to-face communication among team members. This specifically includes the customer representative and any interested stakeholders as observers. In a brief session - team members report to
Agile's Ideal Project Type
Agile Principle : Adaptation
Agile & Planning
Daily Team Meet
37. The practical implication is that agile methods allow project teams to adapt working practices according to the needs of individual projects. The practical implication of dynamic method adaptation is that project managers often have to modify structu
Agile Principle : Changing Requirements
Customer collaboration
Method Tailoring
Agile Success
38. Close - daily co-operation between business people and developers
Agile Principle : Daily co-operation
CMMI (Capability Maturity Model Integration)
Predictive Methods & Change Predictive methods
Agile's Ideal Project Type
39. Self-organizing teams
Agile Negative Impacts : Large
Agile Iteration
Agile Principle : Co-location
Agile Principle : Self-Organizing
40. One common criticism of agile software development methods is that it is developer-centric rather than user-centric (requirements and code - not product design).
Agile Criticism
DOI : Uncertainty
Iteration Benefit
Cross-Functional Team Sizes
41. Low criticality; Senior Developers; Requirements Change Often; Small Number of developers; Culture That Responds to change.
42. Requirements cannot be fully collected at the beginning of the software development cycle - therefore continuous customer or stakeholder involvement is very important.
Agile Principle : Simplicity
Customer collaboration
Agile Principle : Self-Organizing
Agile Software Development
43. Simplicity- The art of maximizing the amount of work not done - is essential
Agile & Planning
Agile Principle : Rapid Delivery
Agile Principle : Simplicity
CMMI (Capability Maturity Model Integration)
44. A process improvement approach whose goal is to help organizations improve their performance. CMMI can be used to guide process improvement across a project - a division - or an entire organization.
Agile & Planning
Iteration Benefit
CMMI (Capability Maturity Model Integration)
Agile Negative Impacts : Mission Critical
45. A set of six management principles initially intended for project managers of Agile Software Development projects. [2005]
Method Tailoring
Agile Negative Impacts : Mission Critical
Team Stakeholder Representative
PM Declaration of Interdependence (DoI)
46. Specific tools and techniques - such as continuous integration - automated or xUnit test - pair programming - test-driven development - design patterns - domain-driven design - code refactoring and other techniques are often used to improve quality a
Quality / Agility
Agile Principle : Adaptation
Agile Principle : Excellence
DOI : Engagement
47. Individuals and interactions over processes and tools
Agile Iteration Vs Release
DOI : Uncertainty
Agile Priority : Interactions Vs Processes
DOI : Tailor
48. Each iteration involves a team working through a full software development cycle - including planning - requirements analysis - design - coding - unit testing - and acceptance testing when a working product is demonstrated to stakeholders.
Agile Iteration
Predictive Methods & Change Predictive methods
Agile Software Development
Agile Priority : Interactions Vs Processes
49. Increase return on investment by making continuous flow of value our focus.
Agile Negative Impacts : Large
Agile Priority : Customer Collaboration Vs Contracts
Team Stakeholder Representative
DOI : Value
50. Team size is typically small (5-9 people) to simplify team communication and team collaboration. Larger development efforts can be delivered by multiple teams working toward a common goal or on different parts of an effort. This might require a coord
Cross-Functional Team Sizes
Daily Team Meet
Agile Success
Iteration Review