The Disciplined Agile Delivery (DAD)
Wiki
Disciplined Agile Delivery (DAD)
190 items found
Page: 1 2 3 4 5 6 7 8 9 10 11......19 next>
PRINCE2 - Overview
Wiki
PRINCE2
Scrum
Wiki
Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Sprint
Wiki
The Sprint is an iteration of work, typically 1 month or less in duration, where a potentially releasable product increment is produced. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. The Sprint contains several other events such as Sprint Planning, Daily Scrums, the Sprint Review and the Sprint Retrospective, in addition to the development work.
Facilitation
Wiki
A set of techniques used by a workshop leader, or facilitator, to improve the operation of a workshop or project team meeting. The benefits of applying facilitation techniques include:
DSDM (Dynamic Systems Development Method)
Wiki
Dynamic systems development method (DSDM) is an agile project delivery framework, initially used as a software development method. First released in 1994, DSDM originally sought to provide some discipline to the rapid application development (RAD) method. In later versions, the DSDM Agile Project Framework was revised and became a generic app...
DSDM:a Brief History
Wiki
In the early 1990s, rapid application development (RAD) was spreading across the IT industry. The user interfaces for software applications were moving from the old green screens to the graphical user interfaces that are used today. New application development tools were coming on the market, such as PowerBuilder. These enabled developers to share their proposed solutions much more easily with their customers – prototyping became a reality and the frustrations of the classical, sequential (waterfall) development methods could be put to one side.
MoSCoW Requirements
Wiki
All requirements are important, but they are prioritized to deliver the greatest and most immediate business benefits early. Developers will initially try to deliver all the Must have, Should have and Could have requirements but the Should and Could requirements will be the first to be removed if the delivery timescale looks threatened.
MoSCoW method
Wiki
The MoSCoW method is a prioritization technique used in management, business analysis, project management, and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement; it is also known as MoSCoW prioritization or MoSCoW analysis.
Pareto Diagram
Wiki
Pareto diagram is vertical bar charts that identify the critical few from the uncritical many. A histogram, ordered by frequency of occurrence, that shows how many results were generated by each identified cause.
ADVERTISEMENT
ADVERTISEMENTS
|
"Life begins at 40, but often so does arthritis and the habit of telling the same story three times to the same person." - Sam Levenson |
