I come to believe that most product development environments and processes are just to damn confusing. Not by nature, but manmade. Let’s look at bug tracking. I’ve spent too many hours of my live with QA and product managers to prioritize a list of bugs. P1, P2, P3 and P4. P1 and P2 need to [...]
Archive for January, 2010
Things ought to be simple
Posted in Communication, Leadership, Management, SCRUM, tagged Batch Processing, SCRUM, Value on 25. January 2010 | 1 Comment »
Agile EVM
Posted in EVM, SCRUM, tagged Agile, Controlling, EVM, Project on 20. January 2010 | Leave a Comment »
Today, I was asked by a colleague how to control costs and schedule in SCRUM projects. Well, I’m a friend of earned value management (evm), explained him the basics and how to handle this approach in classic project management processes. It kept bothering me, so I researched for a combination of agile development and earned [...]
Doomed to Failure
Posted in Communication, Leadership, Management, tagged Communication, Leadership, Management, Project on 15. January 2010 | 1 Comment »
Today I want to tell you about a bet with a good friend. This friend is part of a software-project team, which was assembled by the upper management. The project is of prime importance and top management was in involved in the whole project acquisition process. The project did not really start till today, but [...]
Agile is Lessons Learned
Posted in Communication, SCRUM, tagged Scrum Agile Communication Learning on 12. January 2010 | Leave a Comment »
Does Agile have lessons learned? They are part of the process especially in Scrum. Scrum is about transparancy, inspection and adaption. At the end of each sprint there is a sprint review in which the product increment is demoed to all stakeholders and the product owner. The results of this inspection are reflected with the [...]
Über den Sinn und Unsinn von Lessons Learned
Posted in Lessons Learned, PMI on 9. January 2010 | Leave a Comment »
Gemäß dem PMBOK in der neusten Version 4 definieren sich Lessons Learned wie folgt: “The learning gained from the process of performing the project. Lessons learned may be identified at any point. Also considered a project record, to be included in the lessons learned knowledge base”. Diese “Knowledge Base” stellt dann ein Archiv, mit historischen [...]
