Software is built on a variety of assumptions, and we need to understand what those assumptions are--and work around them in defining how we use the software. With so many options in the marketplace, how do you decide what’s good and what’s not? How do you navigate the promises of software vendors to know what you should be looking for, and how do you decide what will actually work for you?
60 items found
How do you make a fixed-price contract work? This article investigates the reasons why IT projects tend to overrun the budget--and the mitigating actions that can be applied.
Agile methods deliver many benefits in terms of their flexibility to cope with changing requirements and priorities. However, this adaptability and reluctance to be tied down on scope can create contract problems when trying to form supplier agreements or outsource work. Part 1 of our two-part series covers the challenges of agile contracting and offers some of the packaged solutions created so far.
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?
Does your project need outside help? You’ll need to consider a few things before making your pitch to the necessary senior leadership and actually bringing in an outside consultant. Here, we cover some key considerations.
Procurement management is one of the knowledge areas in PMBOK, but procurements for large computer systems or multi-year projects can easily take on a life of their own. This article will provide guidelines for issues that are unique to a procurement project. Ensuring that these guidelines are followed (or at least considered) by the appropriate stakeholder will assist the PM in successfully completing the procurement so that the real work can begin.
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.
The relationship forged with strategic providers can make the difference between success and failure within the organization. Here, the value proposition they represent is often based more on their service and support levels than price. In essence, SPs become de facto stakeholders with the organization--and thus require special consideration in terms of how the relationship is cultivated and managed.
The use of supplier relationship management (SRM) can be considered symbiotic in nature, since the mutually beneficial aspects of having such a two-way dependent/supportive partnership can make each party’s success tied to the other’s. Can we relate?
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?