23 August 2016
Basics of KanBan Approach of Agile Based Project Management
Objective
- To formulate a plan to deliver consistently & incrementally to client.
- Effective ways to prioritize the changes and adopt in phases.
- Make work flow clear to all and divide work in progress in parts to not burden the developers.
Some Rules
- Visualize your work flow.
- Limit work in progress.
- Analyze & improve the development along with change.
Time driven Kanban example
| Week1 | ||||||
|---|---|---|---|---|---|---|
| Task (To-Do) | Schedule | In progress | Done | |||
| 1 | Day | No | Taskid | Progress | 2/5 | 1 |
| 2 | Day1 | 1/2 | 1 | 1/2 | ||
| 3 | Day2 | 2/2 | 1 | 2/3 | ||
| 4 | Day3 | 3/3 | 2 | 2/3 | ||
| 5 | ||||||
| 6 | ||||||
For PM/Manager:
| Week1 | Task | Status | Completed (%) | Backlog |
|---|---|---|---|---|
| Dev1 | Task1 | 3/5 | 70 | Pending tasks |
| Dev2 | Task2 | 4/7 | 40 | |
| Dev3 | Task3 | 1/8 | 15 |
- Max 7 cards/jobs a day every job has a same single card.
- Identity Complete Workflow.
- Divide in bi – weekly Targets and pick each weekly. Target and divide the job/module to each developer and let him make his time-based kanban schedule.
- Maintain Backlog as a separate To-Do and keep prioritize and include in developer- wise, Kanban schedule, with a max of Event Driven & Time driven kanban sheet we can Include the events in To-Do:-
- Ready things: – to-do.
- Waiting :- Tasks waiting
- Backlog :- Task
With Best Regards,
Shri Pal Singh, Director – Brain Technosys Pvt. Ltd.
Leave a Reply
Be the First to Comment!