How to Say 'No' the Agile Way |
||||||||||||
|
|
Home > Articles > How to Say 'No' the Agile Way March 29, 2010 I originally wanted to write about how to start an agile project, possibly the pilot agile project in your organization--if it was starved of resources, people, machines, space, whatever. But I can’t write that article because no advice is worth the space. You shouldn’t even start that project.
An important tenet of agile project management is that both the team and management fully commit to the project. It’s the same idea as when an agile team commits to backlog items for an iteration--it’s got to be a full commitment all around.
Let me be clear about what a starved project is: That’s a project where you’re busy counting the FTEs (Full Time Equivalent) because no one is assigned to this project full time. Or it’s a project with no testers. Or a project with no database people (even though the database is an integral part of the project). Or it’s a project with no testbed, even though you can’t move the product directly to production; you have to test it first.
Please login/register to read the entire article.
sponsored announcements and special offers
Position yourself for success with Florida Tech's MBA in Project Management, accredited by PMI® GAC. There's no GMAT or GRE required, and you'll also qualify for 1,500 experience hours that can be used toward earning a prestigious PMP® credential.
The Enterprise PPM and PMO Blue Print. Learn strategies and best practices for taking a top-down, enterprise-wide approach to PPM processes and system deployment. To learn more and register now, click here!
|
| ||||||||||
|
| ||||||||||||