Recently a consultant asked me if I encourage teams to do a project postmortem or retrospective once a project is done. The goal is to review what worked well and what didn’t.
Every team needs a process they can embrace because they know that process will get them to the desired result.
In previous posts, I have discussed best practices around Change Control. Or, maybe I should say “lack of best practices” since so many organizations either fail to follow a defined process or simply don’t have one.
Recently a consultant asked me if I encourage teams to do a project postmortem or retrospective once a project is done. The goal is to review what worked well and what didn’t.
Learn how to be more effective in meetings and stop “chasing squirrels”.
Every team needs a process they can embrace because they know that process will get them to the desired result.
How about a project glossary that is used to explain the intention of a word, not just to define it? Learn how a project glossary can help create alignment.
In previous posts, I have discussed best practices around Change Control. Or, maybe I should say “lack of best practices” since so many organizations either fail to follow a defined process or simply don’t have one.
I had an “AHA” about a great way to eliminate the more painful conversations around career growth and how to focus on true opportunities. It centers around the question: “In a particular role, what problem are you trying to solve?”
Learn how to prevent a “death march” by knowing and recognizing limitations of all forms.
Are you a solutioner or a supporter? Uncover the difference and how to work together to set your teams up for success.
Estimate Change Requests by not only measuring the effort the change would take to implement but also the impact it has on the rest of the build.
Change controls don’t mean that the project has to go off the rails. Check out some of these best practices to manage and implement change.