Related Content
 |
Losing the Battle One Hill at a Time: Scope Creep in an Agile World Some issues/hills are important and worth going all in – but most probably aren’t. Project managers must choose their battles wisely and develop scope discipline.
|
|
 |
If Things Aren’t Going Well, When Do You Want to Know? Ask people to describe the number one job of a project manager and few will get it right. Payson Hall discusses the most important part of project manager's role.
|
|
 |
Your Project Might Be in Trouble If... As I start my fifth decade working on projects, primarily in the IT and software development space, I wanted to share some patterns I have observed that suggest a project is in trouble, Jeff Foxworthy style. |
|
 |
Contracted IT Projects: A Primer for Client Project Managers If you’ve never managed an IT project for your organization that had significant work outsourced to a vendor, what’s learned on the job can be VERY painful and VERY expensive. Here are some things to watch out for.
|
|
 |
Are You Testing The Quality Into Your Software? The test team shouldn’t have the onus to improve the software quality, rather the quality should already be built into the software. A few subtle indicators can reveal if the quality isn’t being built into the software. |
|
 |
Requirements Discipline: Avoiding “Death by a Thousand Paper Cuts" Absent an effective requirements baseline it is difficult to distinguish clarifications and error correction from enhancements and changes to the original ask. |
|
 |
A Culture of Criticism in Software Companies Author Qaiser Munir outlines his experience with the culture of blame in software development toward those considered to be responsible for "quality". |
|
 |
A Tale of Toxic Sponsorship It is difficult to succeed without effective sponsorship—and almost impossible if your sponsor is toxic, as this true tale explains. |
