1- What does NOT match with Agile Manifesto?
• Process and tools over individuals and interactions
• Working software over comprehensive documentation
• Responding to change over following a plan
• Contract negotiati
...
1- What does NOT match with Agile Manifesto?
• Process and tools over individuals and interactions
• Working software over comprehensive documentation
• Responding to change over following a plan
• Contract negotiation over customer collaboration
2- Which of the following statements about changing requirements in software development, are correct?
• In traditional way of software development, once the requirements are base lined,
further changes should undergo heavy change control process
• Changes are acceptable till design but once development starts, any further changes should be rejected
• In traditional way of software development, once the requirements are base lined, further changes can be easily accepted with light process
• Organizations must adapt to rapidly changing market conditions to stay relevant in business
3- Which of the following statements BEST describe why Agile is winning?
• Products produced by an Agile approach are cheaper than those produced by any other approach
• Agile increases the chances of delivering early business value to the market and quickly incorporate the feedback from the market usage
• Products have faster time to market but may not meet immediate customer needs
• Products are expensive when compared with products produced by other approaches, but are of top quality.
4- Why were the `practitioners of alternative software development methods` not satisfied with the traditional waterfall method?
• Waterfall is not a lightweight process
• The practitioners did not like to work in a formal system and hence did not like any ‘methodology’ at all
• Waterfall experience did not add value to their resume
• Waterfall model failed to meet the demand for speed and was not friendly towards changing business needs and priorities
5- Which of the following BEST represent the Scrum approach to planning?
• Planning is a continuous activity done faintly by Scrum Master and Product Owner
• Detailed planning is done upfront and not revisited
• Whole team together does just enough upfront planning followed by continuous planning throughout the project
• Only planning in Scrum is one of the planning events
.........................................CONTINUED..........................................
[Show More]