Kanban

Lean Kanban Project Management

Transcript

1. Manage your Drupal Project the lean way! Mahesh Nattanmai Site Building/Theming/Project Management
2. Little bit about me 1. 15 yrs in IT industry 2. 7 yrs in ECM (Interwoven, documentum, Sharepoint,etc) 3. 4 yrs in Open source cms (Drupal, Joomla, Wordpress, CMS Made simple) 4. 8 yrs in Project Management (Waterall, Scrum, Kanban) 5. Twitter: @njmahesh, D.o.user: njmahesh
3. Traditional Waterfall
4. Scrum Figure 1. Scrum Process Overview: Here's the basic Scrum process skeleton, showing the key components.
5. Scrum Table 1. Scrum Process: Here are the major checkpoints for a team using Scrum.
6. Scrum People : Scrum Master Product Owner Process : Sprint Planing Daily Scrum Sprint Retrospective Artifacts : Product Backlog Release Backlog Sprint Backlog Sprint Burndown Product Burndown
7. Scrum 1. Less Management overhead with self led teams. We long ago set as a goal for our corporate culture that teams function effectively without continual management oversight. With Agile, team member accountability is built into the process by virtue of the daily Scrum meeting. 2. Better communication among team members. Programmers don’t necessarily like to talk to each other and to other team members. It’s often part of their makeup to be more comfortable “in the computer zone” than in meetings, etc. Scrum fosters and requires communication in many ways. 3. Change is welcome. Breaking up big projects into smaller sprints that each deliver working product means change can be embraced and implemented in short time frames. 4. Focus on prioritization. With the fast paced nature of sprints the product owner and stakeholders are always forced to reprioritize what is important. 5. Its quality based. Each sprint consists of completing a programming plan, a test plan, and a documentation plan. Thus, the team prepares for release with each iteration. This differs from a more traditional approach where programming works for several months then hands off to testing who then hands off to documentation.
8. Kanban - Lean Project Management •is a Japanese word that literally means visual card. •It focuses on enhancing visibility and team communication. •In any project, work is organized on a kanban board, which has a number of columns that represent the phases that work has to go through in order to be considered complete.
9. Kanban Board This is your project's kanban board, which serves as a visual representation of your project's status. From here, you can manipulate story cards, each of which represents a task that must be completed in your project.
10. Kanban Board To see the stories in your backlog, click the Backlog tab. You can then drag the stories from the backlog to your board to indicate that work has begun. As a story progresses through your value stream, drag the card to the next phase. When the story is complete, you can remove it from the board by dragging it to the archive.
11. Kanban Board Stories moved to "Ready" Phase
12. Kanban Board Stories moved from "Ready" to "In Progress" Phase
13. Kanban Board Stories moved from "In Progress" to "Complete" Phase
14. Kanban Board Stories moved from "Complete" to "Archive" Phase
15. Kanban Board From "Backlog" to "Archive" A Central Hub for Communication Team is just as likely to be scattered out over 3continents and 4 time zones,
16. Email, IM and RSS Notifications This is your project's work screen, which lets you slice and dice your stories in a tabular format. Filter it from Whole Project, Backlog, Board and Archive
17. A Placeholder for a Conversation
18. Work Board This is your project's work screen, which lets you slice and dice your stories in a tabular format. Filter it from Whole Project, Backlog, Board and Archive
19. Kanban Board
20. Kanban Board
21. Lead & Cycle Time Lead Time: How long does it take, from the moment the customer requests something, for us to deliver it? Cycle Time: How long does it take, from the moment we start working on something, for us to deliver it? Understanding Lead Time and Cycle Time is the key to effective planning and scheduling. Instead of relying on estimates and guesswork, you can plan based on past performance and real data.
22. Performance • analyze workflow and remove any bottlenecks • monitor and improve your work efficiency
23. Kanban - Lean Project Management 1. Kanban Board for each Project 2. Add Roles & Users for your team to assign the tasks 3. Set Notification (Email, IM (gmail, live, aol, icq) 4. Backlog (List of Tasks) 5. Add Stories Title Size Priority Deadline Assign to Tags Color code Details Attach Comments Link to other Task Block
24. Kanban - Lean Project Management Typical Setup: Features Email IM RSS Feeds GitHug Integration Ipad/Iphone Ver API Cumulative Flow Charts Lead/Cycle Time Kanban Board User Capacity
25. Kanban - Benefits •Organize your work into projects •Invite people and build project teams & user Kanban Boards to collaborate in real time •Visualize, control and optimize your workflow with Kanban board •Use sticky notes to organize your work •Know what and when you should do and deliver •Limit work in progress to achieve better response times
26. Kanban Tools • AgileZen - $29/Month/10 Project/10 Users/10 GB Space • Kanbanery - $19/month/10 Project/10 Users/10 GB Space • LeankitKanban - ($15/Month/Unlimited) • KanbanPad – Free
27. Agilezen • Nice, Clean UI • Projects • Collaborators • File storage • Email notifications • IM notifications • SSL encryption
28. Kanbanery • Create or Copy Task Boards Easily with Templates. • GitHub Integration. • iPhone and iPad apps. • API and several 3rd party apps. • Stay up to date. • Advanced Reporting. • Content-rich tasks. • Work with existing systems. • Realtime Updates.
30. Giveaways LeanKit Kanban AgileZen Kanbanery Professional Edition $15/month/user for 10 user 10 user/unlimited Boards $1500 Pro $29/month 10 Projects/Users/GB $400 Personal $9/month 5 Projects/Users/GB Unlimited (Life Time) 5 1 2 Your Name Email ID Social (just kidding!) njmahesh@gmail.com