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