Project Management by Scrum/Kanban/Process
0 likes734 views
The document describes how Lean and Agile project management techniques like Scrum and Kanban can be combined with a process engine. It provides an example story of a project going through the process. The story shows a project lead creating a new project and team. A product owner then adds tasks to the backlog. A team member discusses and completes tasks, moving them between backlog, todo list, in progress, and done states. The process engine allows tracking of roles, tasks, and conversations throughout the project lifecycle for accountability.
Project Management by Scrum/Kanban/Process
- 1. LEAN & AGILE PROJECT SYSTEM
- 2. SCRUM + KANBAN + PROCESS ENGINE
- 3. LEAN & AGILE PROJECTS? Classic project management is push, the Project Manager assigns tasks. Scrum has way fever rules and is mid-way between push and pull: The Product Owner adds tasks freely to a backlog, then the team discuss the backlog of tasks, chooses a few that the team can do in a specific time frame. Kanban has even fever rules and is pure pull: The Project Lead moves tasks from backlog to Todo List where Team Members can pick up a task to do it when ready.
- 4. COMBINE The following example uses Thingamy’s process engine: Starts with the Kanban method of pure pull and Todo List limit (this adds natural prioritizing without overwhelming the Team). Adds Scrum type Tasks discussions among the Team Members, Then puts it all into a proper process engine for fewest possible glitches, delivery of all pertinent information with each Task, and full capture of all for real accountability.
- 5. EXAMPLE STORY 4 Task Chapters: Backlog + Todo List + In Progress + Done 3 Role Characters: 1. Project Lead - starts a project, moves tasks from Backlog to Todo List. (Dennis in the following story.) 2. Product Owner: Creates new Tasks for the Backlog, reviews done tasks. (James in the following story.) 3. Team Member: Does tasks (as can the two others as well). (Peter in the following story.)
- 6. Dennis decides to start a new project:
- 7. Dennis gets a page up to define the new project:
- 8. In the next step Dennis must create or select a team:
- 9. He chooses to create a new team in the next step:
- 10. Then adds members to the Team:
- 11. And lastly he must set the Todo List limit as well:
- 12. Now to Peter - he sees that a new project has been started:
- 13. And that he has been added to a team so he can accept:
- 14. At the same time, James is notified that he can start to add tasks:
- 15. James clicks on the link and can fill in first task details:
- 16. When done he will always be asked:
- 17. And the system automagically notifies all team of new tasks:
- 18. The Backlog List allows the team to discuss a task:
- 19. Which Peter decides to do:
- 20. And James pipes in:
- 21. Prompting Dennis to move the task to the Todo List:
- 22. But Dennis the Project Lead can also move tasks back to the Backlog if his priorities changes:
- 23. Again all are notified; a task is now ready to be picked up:
- 24. In the meantime Peter had an idea, and messaged that:
- 25. And Dennis piped in:
- 26. So James hits the “Make this discussion into a task” and gets this:
- 27. And all get the message:
- 28. And the new task brought over the whole discussion:
- 29. Back to Peter who now hits the “Todo List”:
- 30. Getting all pertinent information so he can do the task:
- 31. When Peter’s done, James (he added the task) gets to review:
- 32. Reviewing and possibly sending back for more:
- 33. When James (task-adder) has accepted task as done he’s asked:
- 34. While Peter gets this in his face, the system knows he’s free:
- 35. All the while you can see “Who’s doing what?” for the team:
- 36. Or look at the “Full Overview” to keep abreast in real time:
- 37. THE END And so it goes until all’s done. After which every step, every word, can be looked up under Projects Done in the Full Overview.