Language is important. Words, have meaning, lots of meaning. All too often people throw words around without much thought. In an article by Chris Ward and Leonardo Legorreta, called "Beyond Waterfall and Agile Methods: Towards a New Contingency Model for IT Project Management" I found this table. I love it. Let's try to push our [...]
What Type of Project Manager are you? Is agile a fit for your style of PM? Some of my frustration with Agile / Waterfall coming out.
If you don't use the Emotional Time-line Diagramming technique in your Sprint Reviews you should. In this video I describe the technique and my experience using it last week.
Sometimes you need to sacrifice a little to break the dam and gain a lot. [sorry this one is a little shaky]
Many people believe that using agile means not doing planning. baloney. Why the heck do you think Mike Cohn wrote "Agile PLANNING and estimating." The difference is that on an agile project planning happens in different ways, in pragmatic ways, in progressive stages of greater and greater planning. So how do you do it? [...]
Our last sprint was good. But not what I know the team is capable of doing. During the sprint demo we found that they didn't have a whole lot to demo. I took a look at the sprint backlog and found that there were a lot of stories that were not demonstrable. They were things [...]
In a recent sprint planning session we had a discussion about Who our customer is in an Enterprise Agile project. You see Enterprise agile finds all the holes in the pure agile model. In an Enterprise project the customer is sometimes a mixture. We found it useful to identify two customers: Technical Customer Business Customer [...]
Every spring there is a tulip festival up north of Seattle, WA. It reminds me that in the spring everything is new. Most Enterprise organizations are still exploring/piloting agile. In these organizations team members are not typically mature in their ability to self-organize. The Project Manager’s role becomes one of helping teams learn how to [...]
Not all Web Projects should use Agile...Methodologies are made for the cookie-cutter-made-from-the-mold, normal projects. But the real world is not normal, the real world is messy and mixed up and doesn't fit well.
1. Nothing is "normal" 2. Know your goal & purpose 3. Clarify everything you (or others) don't understand 4. Listen more than you talk 5. Serve the team & project 6. Keep it light 7. Trust your team 8. Simplify complex ideas 9. Get lots of input 10. Get a guide 11. Over Deliver