|
by Peter Schuh
 A traditional-sounding name for a blog about agile processes, but let's face it - that's the stuff our customers grade us on.
Do we work with them to identify, assess, and plan functionality in a practical and predictable manner? And do we communicate on the details, report fictionless status, and deliver the goods when we said we would? This blog is about using agile practices and techniques to plan and deliver in real world environnents.
|
|
Written by Peter Schuh
|
|
Monday, 30 August 2010 01:32 |
|
| |
There are two factors that are almost prerequisite to project failure. These are: 1. The team does not communicate sufficient details on project status and issues. 2. Stakeholders do not pay sufficient attention to project status and issues (or the lack thereof). This does not mean that a communicative team and responsive stakeholders guarantee success. [...] ShareThis |
|
|
Written by Peter Schuh
|
|
Monday, 23 August 2010 01:48 |
|
| |
One thing that makes me happy about my current gig is the managers whom I work alongside. I’ve been in environments that were not nearly so healthy. One in specific where the egos of my fellow managers were matched only by the thinness of their skins. This made most every conversation painful. Sometimes even when [...] ShareThis |
|
Written by Peter Schuh
|
|
Thursday, 19 August 2010 00:38 |
|
| |
This was a recent statement of mine to my German (as in born and raised there) wife: “You know, we’re going to have to teach our daughters that there are other forms of defense besides a swift punch in the nose.” And the rebuttal: “Punching the nose is a perfectly appropriate defense.” ShareThis |
|
Written by Peter Schuh
|
|
Monday, 16 August 2010 01:07 |
|
| |
Andrew Wicklander over at Ideal Project Group has a great post on the answer “not yes.” I hear this answer an awful lot when taking teams agile (or more agile). “Not yes” is the answer you hear when you request permission to do something that’s not well understood by the requestee (such as initiate a [...] ShareThis |
|
Written by Peter Schuh
|
|
Wednesday, 11 August 2010 00:30 |
|
| |
It’s 2010. I’m shocked that I still hear this excuse. Hardware is cheap. Continuous integration and deployment tools are commonplace. Virtual machines are everywhere. If a team can’t get its migration strategy straight at the beginning of a project, and consistently deploy-then-test on something that resembles a production environment (or at least the user-acceptance testing [...] ShareThis |
|
Written by Peter Schuh
|
|
Monday, 09 August 2010 00:10 |
|
| |
For some this is a heinous anti-practice. For others it’s standard operating procedure. Either way it’s the fast track to project ruin. Plan and Ignore is the practice of quickly drafting a project plan (typically to satisfy an external demand; typically in Microsoft Project) then tossing the plan and never looking back. This happens for [...] ShareThis |
|
Written by Peter Schuh
|
|
Wednesday, 04 August 2010 02:30 |
|
| |
A very recent realization about management: If you find a carrot big enough you can use it as a stick. I’m still trying to sort out the pros and cons of this one. ShareThis |
|
Written by Peter Schuh
|
|
Monday, 02 August 2010 01:00 |
|
| |
Martha: What did you do? The Doctor: I named her. The power of a name. That’s old magic. — Doctor Who, “The Shakespeare Code” I like to put names to things, especially problems. I’ve found that by naming something, particularly those things that are not immediately intuitive, the individuals who pick up the name have [...] ShareThis |
|
Written by Peter Schuh
|
|
Thursday, 22 July 2010 06:07 |
|
| |
Mike Cohn blogged about the Risk Burndown Chart a few months back.
I love this idea!
It’s a burndown of the overall risk on your project. In a process-heavy environment, it’s a very easy way to get some usefulness out of the issue and risk logs that managers are required to maintain. In an agile environment, it [...] ShareThis |
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 Next > End >>
|
|
Page 1 of 7 |
