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