Posts Tagged
‘project management’

LO / OD Application by Shawn P. Quigley and Jon M Quigley We will need to start this discussion with a question: “What have you ever done that did not teach you something?” It is by the nature of any activity especially those that require coordination and preplanning either learning or development occurs. Most commonly […]

In an earlier blog post, we compared the WBS Dictionary to the Agile Definition of Done. However, we never reviewed any connection between conventional project management Work Breakdown Structure (WBS) and the decomposition of the product backlog to produce the sprint backlog.  Before we can describe what completion of the item looks like, we must first […]

I was exploring twitter as I sometimes do in the morning when I came upon this interesting post.  It is true, to paraphrase Rudyard Kipling, waterfall is waterfall and agile is agile, and never the twain shall meet[1].  So?   The goal of any project is to successfully deliver the objectives of that project and […]

This may or may not be a true story, but I promise it happens every year.  We start with the customer organization and a supplier that the customer refers to as a partner supplier. This “partner” supplier collaborates with the customer to develop custom components for a larger system the customer sells to their customers. […]

Requirements and Benchmarking One of the things we can do to understand and develop our own requirements is to explore other products that are similar to our proposed product or that solve the same or similar customer problem.  Where there are similar needs met, benchmarking is a way for us to understand how other suppliers have […]

There are a number of factors that can influence the approach we take to managing the requirements.  I provide a brief list below (this is not an exhaustive list): the technical sophistication of the product the risk associated with a mistake distribution of the team The more technically complicated the product the more diligent our […]

Scope, Requirements, and Work Breakdown Structure The scope of the work and the requirements provide us with information from which we can build the Work Breakdown Structure or WBS.  In fact, even before we are able to start doing the work to build the expected results of the project, our work breakdown structure should capture […]

The customer can seldom articulate the technical details of the product.  The customer may define the product or need in terms of function and performance, but building the product from these documents will be extremely difficult or perhaps impossible.  We will need some type of document to begin describing in technical terms the product that […]