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