Test your basic knowledge |

Agile Development

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. A set of six management principles initially intended for project managers of Agile Software Development projects. [2005]






2. 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






3. Regular adaptation to changing circumstances






4. Deliver reliable results by engaging customers in frequent interactions and shared ownership.






5. Working software is the principal measure of progress






6. Self-organizing teams






7. Some methodologies focus on development practises (XP) - others focus on the management of the software project (SCRUM).






8. 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.






9. Face-to-face conversation is the best form of communication (co-location)






10. In agile development - self-organization and motivation are important - as are interactions like co-location and pair programming.






11. Large-scale development efforts (>20 developers) - though scaling strategies and evidence of some large projects have been described.






12. Responding to change over following a plan






13. Minimizes overall risk and allows the project to adapt to changes quickly.






14. Boost performance through group accountability for results and shared responsibility for team effectiveness.






15. Working software will be more useful and welcome than just presenting documents to clients in meetings.






16. Continuous attention to technical excellence and good design.






17. Working software over comprehensive documentation






18. 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


19. 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






20. Forcing an agile process on a development team.






21. 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.






22. 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






23. Customer satisfaction by rapid delivery of useful software.






24. 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






25. Working software is delivered frequently (weeks rather than months).






26. 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






27. 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.






28. Improve effectiveness and reliability through situationally specific strategies - processes and practices."






29. 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.






30. 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.






31. Close - daily co-operation between business people and developers






32. Unleash creativity and innovation by recognizing that individuals are the ultimate source of value and creating an environment where they can make a difference.






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.






34. 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.






35. Customer collaboration over contract negotiation






36. Mission-critical systems where failure is not an option at any cost (e.g. software for surgical procedures).






37. 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.






38. Individuals and interactions over processes and tools






39. Welcome changing requirements - even late in development






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).






41. Increase return on investment by making continuous flow of value our focus.






42. 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






43. Simplicity- The art of maximizing the amount of work not done - is essential






44. Distributed development efforts (non-colocated teams). Strategies have been described in Bridging the Distance[40] and Using an Agile Software Process with Offshore Development






45. Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning.






46. Agile development is focused on quick responses to change and continuous development.






47. 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.






48. 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






49. Projects are built around motivated individuals - who should be trusted






50. Requirements cannot be fully collected at the beginning of the software development cycle - therefore continuous customer or stakeholder involvement is very important.