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