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