Archive for the
‘Requirements Management’ Category

What are we trying to accomplish with a communications plan?  Effective project management is the efficient achieving of an organization’s objectives.  To do that, we have to keep our project team informed and working toward the target.  That includes our project sponsor and other stakeholders.  Ultimately our plan should be able to quickly answer the […]

The daily sprint meeting has connections to our risk management as well. We have seen from the previous posting the fact we are having the meeting daily can hasten our project’s (system’s) ability to respond.  The sprint master is now asking about the obstacles or impediments to achieving the objectives of the sprint. Impediments and […]

We felt the need to follow on from our previous blog on tracking testing results in the background using hidden ubiquitous spreadsheet or documents.  If all you have is a spreadsheet for tracking, then you make that visible to all relevant stakeholders.  If the company has a sanctioned or preferred way of handling “bugs” and […]

We break form our blog run on sprint meetings due to incoming flambé du jour. Sometimes we see organizations that are afraid to use the most fundamental of tools, for example, fault tracking from verification.  Instead of using a tracking and visibility tool, we pass back and forth excel sheets behind the scenes. Why would […]

We like this saying and see much merit and believe it to be an axiom.  We have touched upon this a bit in our blog on sponges.  We see areas where one part of the company or development process makes due or improvises with the malodorous input received.  The receiving entity may complain and attempt […]

The customer is the receiver of the output; the customer can be an internal end customer or an intermediary to the next “chain” of events on the way to the final customer. Ultimately, we are aligning our actions (Suppliers, Inputs, Processes, and Outputs) in a way that provides the biggest benefits for our final customer. […]

Our organization’s structure can confound what constitutes and output.  Consider the company that is structured as a “functional” organization, the output from one group will typically go to another group in the system.  This organization structure is sometimes referred to as “silo” since each part of the company, group or department is segregated by expertise.  This has […]

Each process produces some sort of, at least intermediate output. The ultimate output will be the resultant of the series of inputs, processes and outputs, and will be directed toward the ultimate end customer. Therefore the ultimate output capability is the collection of all of the inputs and processes of the systems of the organization. […]

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 see well-meaning people adopt an attitude “if it needs done, then I will do it” even if their job or position in the company does not define them as the person to solve the problem. I call this absorption and it is part of the much ballyhooed “can-do attitude” upon which many companies thrive.  […]