Best practices, lessons learned and advice from your peers in the trenches.
Change management requires continuous communication, active sponsorship, stakeholder buy-in and tailored training. Project leaders can use this spreadsheet-based assessment tool to evaluate their organization's change readiness and to provide guidance on better preparing for change initiatives.
Red and green signify more than holiday spirit for most project managers. Along with yellow, these colors are used to indicate the status of a project — be it real, implied or imagined. Here are some helpful thoughts to keep in mind when using red, yellow and green to represent your project's health.
Do team members and executives in your organization see retrospectives as a waste of time and expense? If so, maybe your retrospectives aren’t providing the value they should, from establishing a culture of team learning and stressing continual improvement, to tracking metrics and celebrating successes.
Some organizations expect project managers to be “miracle workers” who produce results without the active support or involvement of leadership. And sometimes project managers are able to leverage resources, meet deadlines and achieve deliverables under these conditions. But it’s not a long-term strategy for success.
Organizational silos and poor communication are often the result of “turf wars” in which groups or teams value their interests over cross-functional cooperation for the good of the entire enterprise. Here are some ideas to help project managers operate in this environment and overcome its harmful effects.
Many organizations live in perpetual ‘fire-fighting’ mode, a space in which short-term results often supersede long-range plans and strategies. While this can certainly make it more difficult to fully realize the benefits of sound project management practices, there are techniques to accommodate a ‘high-drama’ culture throughout the project lifecycle.
From simple problems to complex, and everything in between, there are many pitfalls that can plague a project. And with low-performing organizations wasting nearly 12 times more resources than high-performing ones on failed projects, there’s no time like the present to address the causes and implement much-needed changes.
Software measurement by itself does not resolve budget, schedule or staffing issues for projects or portfolios, but it does provide a basis upon which informed decisions can be made. Here are examples of how to use metrics to determine present capabilities, assess whether plans are feasible, and explore trade-offs if they are not.
When a risk does not affect project objectives but could still impact another part of the organization, it should be “escalated” to the appropriate owner to ensure that it is recognized, understood and managed. Here is an overview of this key risk response strategy in practice.
Many business leaders are unacquainted with the wealth of knowledge about how software projects behave. No surprise, they are unable to explain why these projects fail repeatedly, much less do something about it. Here are five fundamental “laws” of software development that all executives (and teams) should understand and follow.