There’s more to vendor management than deliverables and deadlines. Let's look at a few basic concepts that will help PMs avoid some of the biggest pitfalls.
66 items found
Although the 71st anniversary of Operation Dynamo, which took place during the second World War, was celebrated earlier in the summer, we can still continue to celebrate its achievements in the extraordinary results that the use of "crowdsourcing" in projects can deliver.
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.
Some RFPs are bad…really bad. It makes you wonder how clear the purchasing organization is on what they are trying to achieve. Here, we look at the process that an organization goes through in preparing and issuing an Request For Proposal--and identify some best practices.
In the ever-increasing speed trip down the ramp of badly made cost-cutting decisions, many mainstream manufacturers are compromising on the quality of their products. To help address this, we all need to more carefully monitor the quality of our supplier goods.
RFPs are a double-edged sword for many vendors. In the first article, we looked at the challenges with layout and content. In this second installment, we look at the challenges vendors experience in the process from the point they are made aware of the RFP to the submission of the bid.
Have you ever thought about the RFP process from the other perspective--the potential vendor who responds? An RFP response is more than just a proposal to supply products and/or services; in many cases it is an opportunity to showcase a potential vendor to the procuring organization. But when some vendors reply to RFPs, you have to wonder what they thought that they were bidding on. In this article, we flag some of the things vendors should consider.
An effective contingent work team can be procured more easily when you get involved in development of the SOW. Your non-involvement may result in a costly Emergency Executive Intervention.
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.
Some substantive updates to the definition of Scrum artifacts may seem like minor clarifications to terms and definitions, but they have quite profound implications. In this article, we discuss these changes and how they affect the ScrumMaster (or project manager) tasked with delivering a “done” increment.