Posts Tagged
‘configuration management’

I have been brought back to this topic many times over the past few months. Hits production is sort of like “hitting the fan.”  We release our product after development and then put our fingers in our ears hoping to not hear the metaphoric explosion at the plant. It is no wonder.  We have the […]

We like the title Random Acts of Product Development.   It often appears that product development is a collection of ill-conceived and poorly executed tasks.  Those planning refuse to recognize dependencies between groups and tasks and are unable or unwilling to acknowledge they are really working within a system – blinded by the solely important launch […]

We have recently had a discussion on what it takes to quality assure software. The discussion focused on FMEA and the role it plays in quality assurance.  The discussion began to sound as if the FMEA was the panacea for poor quality. There is no silver bullet. To be sure the FMEA (which is essentially […]

Once we have our captured our requirements. We identify the substance of the content for the iterations from the development.  In fact, recall from the requirements prioritization blog post. That work has given us some insight into how the iterative packages could be developed and what content or capabilities are to be delivered.  In the […]

One under or ineffectively used tool is the specification or requirements review, which is a form of design review. In this case we are reviewing the design while it is still easy and cheap to make adjustments.  Experience suggests, if we do not just forget to do this activity, it is a hastily arranged activity […]

The initial product requirements provide the product baseline. Our project planning will be focused upon delivering meeting these requirements. In a phased development process, we will prioritize the requirements (shown earlier) and deliver iterations.  This staged delivery allows us to gain additional insight into the product.  We may learn things that necessitate changes to the […]

We now have linked our scope through to the various levels of requirements. We are then able to prioritize the delivery of the various project obligations.  The prioritization may be based, for example upon: Technical need Customer need Regulatory requirements Complexity and Risk Technical needs are the dependencies to getting the product features working, for […]

This may sound difficult, but there are some rules for good requirements.  According to the International Council on Systems Engineering (INCOSE http://www.incose.org/chicagoland/docs/Writing%20Effective%20Requirements.pdf), requirements should have the attributes below (similarly can be found at IEEE): Necessary –  driven by the objective of the project and business Verifiable – ability to objectively confirmed that the requirement is […]

So how do we ensure we get meaningful requirements? We have a number of ways to understand our objective and learning about the Interviews customer clinics Simulation Digital mock ups Prototype physical mock ups Instrumentation Other information gathering (standards, regulations, etc.) We start with interviews of customers, stakeholders and project sponsors. Interviews also include customer […]

Requirements are fundamental to project success as the scope definition.  Additionally, there are dependencies that impact the ability to produce suitable requirements.  A few of those things are: Well defined scope of the work Sponsor and customer involvement Capability of the requirements authors Prioritized functions or abilities The needs or objectives of the customers or […]