Kandan Software development cycle .pdf

Software development cycle

1. Kanban in Software
Development
By: Nischal Giri, Rupen Rai, & Sudan Chapagain.
Kanban

2. History
oDeveloped by Taiichi Ohno at Toyota in the 1940s.
oOriginally used in manufacturing for lean production.
oAdopted in software development in the 2000s.
oPopularized by David J. Anderson.
Anderson is the author of the book "Kanban: Successful Evolutionary Change for Your
Technology Business," which played a significant role in spreading awareness and understanding
of Kanban principles and practices
oAdapted to Agile methodologies.

3. What is it?
oKanban is a visual management tool.
oFocuses on optimizing workflow and minimizing waste.
oIn software development, it helps visualize tasks and their progress.
oUtilizes Kanban boards to represent work stages.
oKanban boards visually depict work at various stages of a process using cards to represent
work items and columns to represent each stage of the process. Cards are moved from left to
right to show progress and to help coordinate teams performing the work.
oEmphasizes limiting work in progress (WIP).

4. Example

5. Real world Example

6. Core concepts
1.Visualizing Workflow
Creating Kanban boards to visualize the flow of work through SDLC phases.
2.Limiting Work in Progress (WIP)
Setting WIP limits to prevent overloading teams and maintain focus.
3.Managing Flow
Ensuring smooth and continuous movement of tasks through each SDLC
phase.

7. Advantages
Flexibility
Adaptable to various project types and team sizes.
Visual Management
Provides clear visibility into work progress.
Reduced Waste
Minimizes idle time and bottlenecks, enhancing efficiency.
Focus on Flow
Emphasizes completing tasks rather than starting new ones, enhancing throughput.
Improved Communication
Facilitates better collaboration and transparency among team members.

8. Disadvantages
Dependency on Visual Management
Relies heavily on the clarity and accuracy of the Kanban board.
Lack of Structured Timeboxing
May lead to tasks taking longer than anticipated without explicit time constraints.
Potential for Overloading Teams
Without strict WIP limits, there's a risk of overwhelming teams with too many tasks.
Limited for Predictive Planning
Kanban's focus on flow makes it less suitable for projects requiring strict time-based
planning.
Requires Discipline
Requires disciplined adherence to principles and practices to realize benefits effectively.

9. Thank you!