Facebook
LinkedIn
RSS Feed
Newsletter
Jurgen Appelo brings us some insight on solving different problems with software development. I have no idea why the heck he’s trying to make a manifesto out of this thing. Manifesto is such a worn word already.
I’ll try to summarize Jurgen’s post for you and I’ll try to be brief.
There’s no silver bullet.
End of summary. Of course I strongly encourage you to read the whole story since all points are valid, but that’s the conclusion. Software development world became so complex there is no single panacea for every sickness. Actually there never was.
I see a place for orthodox agile followers and I see a place for heavy-weight and highly formalized approaches. It’s like with programming languages. Is Java better from C++? There’s no universal answer. How about Java family versus .NET family? Still no answer which is true every time.
When I hear there’s single best methodology which will be best for me, no matter what I do, who is my client and how my team looks like I call it bullshit. So should you.
More on PM Methodologies: Be Selective!
Raven Young brings us 5 easy tips to for adopting PM methodology. One of those nailed it:
“Be Selective: Never adopt a Standard in its entirety, unless you believe it's a 100% fit. Instead, you're best to select those parts which you believe can be integrated into your company culture, with the least disruption to your project activities.”
We Don’t Need No PM Methodology
As regular readers of Software Project Management probably know I don’t evangelize any specific project management or software development methodology. Depending on a project, its size, external constraints and business environment the best choice can differ from very flexible approach to formalized heavy-weight methodology. Or maybe no methodology at all.
