Remove 2002 Remove Cadence Remove Closing Remove Technical Review
article thumbnail

Project Boards and Project Steering Groups: An Introduction

Rebel’s Guide to PM

And will make the decision to close the project down early if it can no longer meet its objectives. It’s fine to have a different cadence at different points in the project lifecycle. Make sure you have the latest info on project budgets and how close the project is to meeting its goals. Action review and next steps.

article thumbnail

Compendium of Works to Increase Probability of Project Success

Herding Cats

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Business, Technical, Systems, Risk, and Project Management. Table of Contents (Click the Name to go to Section).

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Questioning Agile Dogma

Leading Agile

When I first learned about Agile methods in 2002, the principles seemed to offer an ideal solution to many organizational issues common at the time. How can the same principle be a good idea in 2002 and a bad idea in 2019? As a result, the organization never benefited from the full potential of the technical staff. Stable Team.

Agile 115
article thumbnail

What’s Worse Than Not Automating Your Software Delivery Pipeline?

Leading Agile

An unattended software delivery pipeline frees technical staff to spend more time on value-add activities rather than tediously performing repetitive tasks by hand, such as. Reviewing code by eyeballing it to ensure compliance with coding standards. Two closely related conceptual errors appear to be quite common.