Author Ken Pugh
Picked this book up to add to my LEAN and Agile knowledge. A tough read as it is very reference
based, so plan on taking your time and re-reading several portions of it, especially if you do not have
experience with LEAN or Agile before. It is effective in showing how the two methodologies can work
together and are aligned in their thinking on empowered teams and facilitating managers.
– Manifesto for Agile Software Development page xxxi
- The principles are the focus on this page, like any list of things (aka 7 Habits – I like 4 of them), you should read through the book and come back to this page in integrate into your lean/agile process what will most benefit you. Unless you have a scrum master, then they will beat you until you bleed to follow all of them.
– Questions to ask you and your organization on page 23
- Of this short list, the most important is ‘What are impediments to smaller, more frequent deliveries in your organization?”
- Why do so many projects/initiatives focus on the big bang deliverable at the GO LIVE, instead of 10 smaller go lives that reduce risk, improve success of hitting each go live and remove stress from the humans in the effort.
- Yes, have either a PM or a project coordinator generate these maps, then spend 2-4 hours every two weeks updating them to keep them fresh and relevant, which works well for a consulting firm with a PMO.
- If you are a company looking to embrace agile, well you likely do not have the bandwidth to do this effort. I suggest in place to focus each team member on 3 priorities that are directly tied to the corporate strategy and focus weekly on activities that are impeding work on those 3 each day/week.
- I know skipped a whole heck of a lot of pages, but if you know about LEAN, Agile, Scrum and so forth those pages are refresher and connecting the methodologies.
- The chart at the bottom of the page is simple, but take note of the size of the boxes as I relate the amount of time you should take in training and adopting efforts for each of those boxes. Thus the most time on setting a good foundation of understanding and building acceptance.
I use this to tie my training and experience in project management, LEAN, and Agile together. Is it something I use often, no I will not. But, it will be something I look at when I begin a new project that is either LEAN or Agile or both.