When one PM was asked to list the key requirements for a PMIS that would enable it to better support project and organizational effectiveness, he thought about past project, portfolio and program management experiences. The result? A “dream list” of features for a PMIS to support large, traditionally managed projects...a list that was surprisingly agile.
You think you have a handle on how to deliver your projects. Then a mandate comes down that your development team is “going agile”. This is an understandably scary proposition for some people. Here we look at general patterns, models, values and practices that lead to success when thoughtfully practiced by motivated individuals.
Is all hope lost for managing quality on projects? Should we just throw in the towel, or is there a better way of being able to measure and manage quality?
The following recommendations will help keep quality management in mind before the company contracts with a supplier for services.
Working on the program level, quality management becomes complex because of differing elements being measured and differing criteria. A program management plan with a quality management section can fit the bill.
Working on the program level, quality management becomes complex because of differing elements being measured and differing criteria. A Program Management Plan with a quality management section can fit the bill. In the concluding installment, we look at how you can guide this complexity.
Managing quality during a software development project can be difficult and time consuming when you have been misinformed about true quality indicators and practices. Actively managing quality on an agile project can be both simpler and harder than traditional approaches. Here are some basic practices to save time and unnecessary rework--and improve stakeholder satisfaction before and after delivery.
Risk management on projects has become a doom-and-gloom exercise in finding all of the bad things that might go wrong and coming up with plans of what to do about them. Project budgets inflate and schedules extend as mitigation and insurance strategies grow and contingency budgets balloon. We highlight the negatives to such an extent that we forget to focus on the positives. Time to turn that frown upside down...
Any project team that doesn’t manage its current and legacy technical debt will eventually discover that it is impossible to produce features. It’s a slippery slope. Here’s what an agile project manager can do to work with a project team and a product owner.
The Mayans may have had the first timeboxed project--they had a strict 2012 timebox cutoff with little room for extension (you know, since the world would no longer exist). Although agile methods have been preaching the benefits of fixed timeboxed schedules since their creation, it still raises concerns with many stakeholders. That's because timeboxing with flexing scope is the worst form of project compromise--until, that is, you try the alternatives.
|
"You do not really understand something unless you can explain it to your grandmother." - Albert Einstein |
