Show:
Level 1
Level 2
Level 3
Level 4
100
Give at least two examples of standard behaviors that are leading indicators of iterative software projects success?
+ Demonstrable, objectively measured progress + Incrementally increasing functionality + Continuously improving quality + Continuous risk reduction + Decreasing level of change + Increasingly accurate estimates + Increasing enthusiasm, morale, collaboration, and effective teamwork + Convergence on an accurate business solution
100
What are the three software projects categories based on resolutions type?
+ Successful projects + Challenged projects + Failed projects
100
Who specifies the technical and business objectives of the project?
+ Management and developers specify technical objectives + Management and customers specify business objectives
100
What does "incrementally increased functionality" iterative software project success indicator mean?
Each iteration delivers more demonstrable functionality than the one before it without compromising the quality of functionality delivered in earlier iterations.
200
What are the key characteristics of successful iterative projects?
The production of an appropriate solution that will be delivered on time and on budget and that will address the real needs of the stakeholders.
200
Give at least two examples on how you can demonstratively and objectively measure iterative software project progress?
+ Number of products and documents produced + Number of lines of code produced + Number of activities completed + Amount of the budget consumed + Amount of the schedule consumed + Number of requirements verified to have been implemented correctly
200
What is the main reason behind why some projects initially show slow progress, but accelerate later?
The projects are technically challenged at the beginning. As the project team gains more experience and how to control change and reduce project risks in subsequent iterations, the project shows accelerated progress.
200
What is the best approach to avoid feature creep?
Rank and prioritize new features; what are the users willing to give up to get the new feature.
300
How would you measure the iteration stability?
The reduction in items being changed or amount of rework.
300
In early iterations, why stability is more important than functionality?
Because too much emphasis on added functionality may degrades quality.
300
Define one way to measure the quality of an increment or functionality produced by the iteration?
Assess the difference between the actual amount of code delivered and the amount of code that actually passed the testing.
300
Why do software development projects suffer from "feature creep"?
+ Requirements evolve and expand overtime. + It is natural for users to think about new things they would like when they see the results of iterations.
400
Give at least two reasons why sometime the increment produced by an iteration differs from that produced by the preceding iteration?
+ amount of effort + team productivity + stability of requirements + stability of products produced by earlier iterations
400
In addition to completing the project in iterations, what can you do within the iteration to reduce the risk?
Select requirements that confronts specific risks for implementation during the iteration.
400
How would you define the success a project that has been iteratively managed?
It depends on the project; for some projects getting to market early is more important than meeting the original specifications, for other projects delivering an exciting new set of functionality is more important than achieving high level of quality. Time to market versus product quality.
400
What type of an iterative approach should you adopt to increase the project chances of success?
An approach that enables stakeholder expectations to converge and actively attacks the project risk.