Agile Process Frameworks
This sections describes Agile Process Framework.
Scrum process
Scrum is an iterative and incremental framework, which focuses on a flexible, holistic product development strategy where a development team works as a unit to reach a common goal. Scrum is the most widely known and practiced agile process framework.
Learn more about
Scrum in Wikipedia
.
Kanban process
Kanban puts an emphasis on just in time delivery while not overloading the software developers. In this approach, the process, from definition of a task to its delivery to the customer, is displayed for participants to see and developers pull work from a queue.
Kanban promotes the following core practices:
1. Visualize: Visualizing the flow of the inherently invisible knowledge work and making it visible is core to understanding how work proceeds. A common way to visualize the workflow is to use a card wall with cards and columns. The columns on the card wall representing the different states or steps in the workflow.
2. Limit WIP: Work-in-process (WIP) at each state in the workflow is limited. New work is pulled into a state only when there is available capacity within the local WIP limit.
3. Manage flow: Flow of work through each state in the workflow is monitored, measured and reported to evaluate positive or negative effects on the system.
4. Make policies explicit: With an explicit understanding of how things work and how work is actually done, it is possible to move to a rational, empirical, objective discussion of issues.
5. Implement feedback loops: Collaboration to review flow of work and demand versus capability measures, metrics and indicators is vital.
6. Improve collaboratively, evolve experimentally: Kanban encourages small continuous, incremental and evolutionary changes that stick, using scientific approaches.