Remove 2002 Remove Cadence Remove Process Remove Technical Review
article thumbnail

Project Boards and Project Steering Groups: An Introduction

Rebel’s Guide to PM

It’s fine to have a different cadence at different points in the project lifecycle. If you are expecting the project oversight committee to make a decision at the meeting, make sure that they have information in advance of your meeting so that they can review the different options. Action review and next steps. Key decisions.

article thumbnail

Compendium of Works to Increase Probability of Project Success

Herding Cats

Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Management Processes (#MP). Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Business, Technical, Systems, Risk, and Project Management. Management Processes.

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? When I applied those principles in real-world situations, they worked remarkably well. What has changed?

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. The company wanted to automate their dispatching process. Automate what?