Project control is not about the minutiae, it’s about the big picture. Here we provide some guidelines on how to move from micro-level project management to a more macro-level control phase.
248 items found
PM principles state that there should be absolute clarity in obtaining the requirements. If the fog of ambiguity clouds this phase, the delivered project will never be accepted by the stakeholders. Here we examine some of the glaring issues in the requirements management process.
Does the use of agile project management require new contract models in order to be successful? Can agile project management be used with traditional fixed-price contracts? Does agile project management require a new type of contract (and if so, what kinds)? Furthermore, wouldn’t a new type of contract discourage the use of agile PM?
Stakeholders need to know the status of a project. A good status report will report status and also foster communication to benefit the project’s health. Here, we explore some of your options.
Transitions can be difficult when management and stakeholders change--something that happens on a regular basis in the government. Some basic guidelines can keep the project on track.
Where evolving procurement requirements come from, and why, is in reality no different than how requirements evolve in any organizational area. The challenge is that they compound themselves, layering restriction upon constraint upon requirement. What can an organization do to improve its procurement efforts? What can be done to make procurement work in support of projects rather than be a barrier, roadblock or black hole?
This two-part article will provide you with some insight into some of the most frustrating aspects that vendors experience when they attempt to decipher the hieroglyphics found in the proposal documents. The first part will focus on the content of the RFP.
This will be the first in a series of articles that will look to provide the background of issues involved with managing an agile software development project under a traditionally linear and sequential project procurement process. Software development has been deliberately chosen for the example industry since that’s the domain for which agile is most typically used, but for those using agile in other industry domains, the general issues and proposed solution should work equally well within your industry.
They approved the scope statement?! Freeze the client! Sigh...if only it were that simple. Maybe it's time to learn to love change instead of struggling against it.
Project management is becoming recognized on an international scale. In support of this, there are a number of efforts underway to promote a global view of how we think about, discuss and practice project management. But to what extent is project management a universal language? To what extent can it be? Or are we all simply sowing confusion as we use the same words to mean very different things?