Midway through the year is a good time to review business and project results in a constructive, positive manner. Rather than dwell on disappointments, the main purpose should be to prioritize, refocus, and commit to improving the work for the remainder of the year.
While strategic planning and delivery processes have evolved over the last several years, the pursuit of annual goals and objectives—with convenient metrics to track them—remains at the forefront. It’s time that changed.
by Faizy S. Mansoury, PMP®, CISA, CPA, MA. M&E, Bacc. BAF
The project audit gives stakeholders confidence that governance is working, and that the project is being managed properly and producing its intended objectives. In this article, an auditor for the Office of the Controller and Auditor General of Tanzania shares the importance of utilizing the process groups from the PMBOK® Guide in his work.
Is benefits realization a significant challenge in your organization? Perhaps it’s time to question your approach, to acknowledge that the process might be fundamentally flawed and results in a false sense of understanding what’s happening.
How can you commit to work if you don’t know whether that work will deliver what you want? Benefits realization isn’t easy, but it’s certainly not impossible. The fundamental issue is that work—and the benefits aligned with that work—is being defined in the wrong way.
Innovation is difficult to measure, track and manage. An innovation accounting system can help to put facts at the forefront of your innovation processes and projects. There is no one-size-fits-all approach to innovation, but these six principles are a good foundation.
There is increased focus on measuring project performance in terms of business outcomes. What does that mean for agile projects? How should value be measured in an agile environment?
Agile has been “going mainstream” for more than a decade, but supporting evidence was more in the eye of the beholder. Maybe now it’s really happening. A new State of Agile report found growing adoption rates outside of software development and documented success in areas such as visibility and alignment.
A development team designed a feature to improve customer experience but things got worse. It turns out they didn’t identify the real problem or the right way to fix it. What they needed was a hypothesis for what was being changed, how that change would help, and how they would test it.
Most organizations have limited resources to invest in improvement initiatives. And a significant percentage of those resources don’t deliver results. That’s a huge problem. To begin to fix it, we have to understand where and why this waste is occurring.