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