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. Regular adaptation to changing circumstances
Agile Principle : Adaptation
Agile Principle : Frequent Delivery
DOI : Engagement
Agile Negative Impacts : Distributed Locations
2. Improve effectiveness and reliability through situationally specific strategies - processes and practices."
DOI : Tailor
Agile Criticism
Working Software
Cross-Functional Team Sizes
3. 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.
DOI : Tailor
Agile Negative Impacts : Mission Critical
Iteration Review
Method Tailoring
4. Projects are built around motivated individuals - who should be trusted
DOI : Engagement
Predictive Methods & Change Predictive methods
Method Tailoring
Agile Principle : Motivation & Trust
5. Unleash creativity and innovation by recognizing that individuals are the ultimate source of value and creating an environment where they can make a difference.
Agile Principle : Excellence
DOI : Individuals
Customer collaboration
Iteration Benefit
6. 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.
CMMI (Capability Maturity Model Integration)
DOI : Uncertainty
Agile Priority : Responding to change Vs Plans
Agile Principle : Sustainable pace
7. Agile development is focused on quick responses to change and continuous development.
Responding to change
Agile Negative Impacts : Large
DOI : Value
DOI : Engagement
8. 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 Negative Impacts : Distributed Locations
Method Tailoring
Agile Principle : Software measures progress
Individuals and Interactions
9. Face-to-face conversation is the best form of communication (co-location)
Agile Principle : Motivation & Trust
Agile Principle : Daily co-operation
Agile Principle : Co-location
Quality / Agility
10. 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 Methodology Variations
Agile Success
Method Tailoring
Agile's Ideal Project Type
11. 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
Agile Iteration Vs Release
Quality / Agility
Cross-Functional Team Sizes
Iteration Benefit
12. Close - daily co-operation between business people and developers
DOI : Engagement
Agile Principle : Daily co-operation
Team Stakeholder Representative
Quality / Agility
13. Minimizes overall risk and allows the project to adapt to changes quickly.
Iteration Benefit
PM Declaration of Interdependence (DoI)
CMMI (Capability Maturity Model Integration)
DOI : Value
14. Customer satisfaction by rapid delivery of useful software.
Agile Principle : Rapid Delivery
Agile Negative Impacts : Mission Critical
Agile Negative Impacts : Distributed Locations
DOI : Engagement
15. Working software will be more useful and welcome than just presenting documents to clients in meetings.
Working Software
Quality / Agility
Agile Negative Impacts : Large
Agile Priority : Interactions Vs Processes
16. Low criticality; Senior Developers; Requirements Change Often; Small Number of developers; Culture That Responds to change.
17. Mission-critical systems where failure is not an option at any cost (e.g. software for surgical procedures).
Agile Negative Impacts : Mission Critical
Agile Iteration Vs Release
DOI : Engagement
Customer collaboration
18. One common criticism of agile software development methods is that it is developer-centric rather than user-centric (requirements and code - not product design).
DOI : Value
Agile & Predictions
Daily Team Meet Style
Agile Criticism
19. 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
Predictive Methods & Change Predictive methods
Agile Priority : Interactions Vs Processes
Quality / Agility
Agile Principle : Rapid Delivery
20. Some methodologies focus on development practises (XP) - others focus on the management of the software project (SCRUM).
Agile Priority : Working Software Vs Docs
Agile Principle : Changing Requirements
Agile Priority : Interactions Vs Processes
Agile Methodology Variations
21. Working software is delivered frequently (weeks rather than months).
Agile Principle : Frequent Delivery
Agile Negative Impacts : Force Feeding
Agile Principle : Software measures progress
Predictive Methods & Change Predictive methods
22. In agile development - self-organization and motivation are important - as are interactions like co-location and pair programming.
DOI : Individuals
Individuals and Interactions
Predictive Methods & Change Predictive methods
Agile Principle : Motivation & Trust
23. Dxpect uncertainty and manage for it through iterations - anticipation and adaptation.
Agile & Planning
Agile Principle : Changing Requirements
DOI : Uncertainty
Team Stakeholder Representative
24. 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
Cross-Functional Team Sizes
Team Stakeholder Representative
Agile Principle : Co-location
Agile Criticism
25. Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning.
Agile Iteration
DOI : Uncertainty
Agile & Planning
Agile Criticism
26. Simplicity- The art of maximizing the amount of work not done - is essential
Agile Iteration
DOI : Uncertainty
Agile Principle : Simplicity
Daily Team Meet
27. 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 Priority : Responding to change Vs Plans
Cross-Functional Team Sizes
Agile Principle : Simplicity
Daily Team Meet
28. 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.
Customer collaboration
Cross-Functional Team Sizes
Agile Software Development
Agile Methodology Variations
29. 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 Iteration Vs Release
Individuals and Interactions
Agile & Continuous Testing
Agile Priority : Working Software Vs Docs
30. 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
Individuals and Interactions
Agile Negative Impacts : Distributed Locations
Agile & Predictions
Behaviour Driven Development
31. Customer collaboration over contract negotiation
PM Declaration of Interdependence (DoI)
Agile Priority : Customer Collaboration Vs Contracts
Agile Principle : Rapid Delivery
Agile & Planning
32. Responding to change over following a plan
Team Stakeholder Representative
Agile Priority : Responding to change Vs Plans
Agile Negative Impacts : Large
Agile Priority : Customer Collaboration Vs Contracts
33. Forcing an agile process on a development team.
PM Declaration of Interdependence (DoI)
Agile Principle : Simplicity
Agile Priority : Responding to change Vs Plans
Agile Negative Impacts : Force Feeding
34. Continuous attention to technical excellence and good design.
DOI : Value
Agile Iteration
Agile & Continuous Testing
Agile Principle : Excellence
35. Self-organizing teams
CMMI (Capability Maturity Model Integration)
Agile Principle : Motivation & Trust
Agile Principle : Self-Organizing
Agile Principle : Changing Requirements
36. Requirements cannot be fully collected at the beginning of the software development cycle - therefore continuous customer or stakeholder involvement is very important.
DOI : Value
Agile Principle : Changing Requirements
Customer collaboration
Agile Principle : Co-location
37. 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.
Agile Iteration Vs Release
Behaviour Driven Development
DOI : Engagement
PM Declaration of Interdependence (DoI)
38. A set of six management principles initially intended for project managers of Agile Software Development projects. [2005]
DOI : Value
Agile Principle : Excellence
Iteration Review
PM Declaration of Interdependence (DoI)
39. 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.
DOI : Tailor
Agile Priority : Working Software Vs Docs
Agile Iteration
Daily Team Meet Style
40. Deliver reliable results by engaging customers in frequent interactions and shared ownership.
DOI : Engagement
Agile & Continuous Testing
Agile Principle : Adaptation
Agile Negative Impacts : Large
41. Increase return on investment by making continuous flow of value our focus.
DOI : Value
Agile Priority : Interactions Vs Processes
Agile Criticism
Agile's Ideal Project Type
42. Welcome changing requirements - even late in development
Cross-Functional Team Sizes
Agile Principle : Software measures progress
Agile Principle : Changing Requirements
Agile Negative Impacts : Large
43. Boost performance through group accountability for results and shared responsibility for team effectiveness.
Agile Iteration Vs Release
PM Declaration of Interdependence (DoI)
Iteration Review
DOI : Shared Responsibility
44. 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 Success
Agile Principle : Co-location
Quality / Agility
Customer collaboration
45. Working software is the principal measure of progress
Predictive Methods & Change Predictive methods
Agile Principle : Software measures progress
Agile Principle : Changing Requirements
Agile Software Development
46. 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.
Iteration Review
Agile's Ideal Project Type
Agile Success
Behaviour Driven Development
47. Working software over comprehensive documentation
PM Declaration of Interdependence (DoI)
Agile Priority : Working Software Vs Docs
Agile Criticism
Agile Iteration Vs Release
48. Large-scale development efforts (>20 developers) - though scaling strategies and evidence of some large projects have been described.
Agile Negative Impacts : Large
Cross-Functional Team Sizes
Agile Principle : Software measures progress
Iteration Review
49. 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.
Agile Principle : Adaptation
DOI : Value
Daily Team Meet Style
Responding to change
50. 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
Agile Principle : Sustainable pace
Iteration Review
Iteration Benefit
Quality / Agility