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