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