Throughout the Getting Predictable blog, I talk about alignment. For many, the word “alignment” is a bit vague. Does it mean we agree? Does it mean I actively support you? If I don’t actively support you, but I don’t block you either, am I “aligned” with you? As it relates to projects, doesn’t alignment simply […]
It’s not often, but I believe we have all experienced the meeting that goes too smoothly. There’s anywhere from four to eight people, trapped with each other for an hour, around our favorite conference table.
In this blog I usually write about best practices that help set teams up for success. That is really what Getting Predictable is about.
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.
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.
Learn techniques on how to create more visibility in your projects in order to track progress and create alignment between the business and IT.
Learn the difference between visibility and transparency in order to ensure alignment and project success.
Learn how reaching alignment between the IT and Business before a project begins can reduce rework every time.