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