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