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 […]
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 […]
Consider a rather large project that like so many projects had some difficulties. The project team had a major component (subsystem) delivered from a supplier. The supplier has one set of processes and the customer organization another. This supplier delivers multiple versions of this major subsystem. The customer integrates this subsystem into the larger system […]
We have seen the word “layoff” used during a reduction in force. A reduction in force is a mass firing, often engendered by management ineptitude but sometimes driven by market forces. A layoff occurs when we temporarily dismiss an employee, but we provide preferential treatment for them when the market bounces back. Even with the […]
Teams must grow; teams cannot be simply appointed and anointed. We may have a designated group that evolves into a team, but this emergent phenomenon takes time. It takes time to discover the strengths and weakness if each member of the group, understanding that ultimately transforms into trust, the backbone value/concept for any successful team. […]
Occasionally, we are put in the position of removing an employee; that is, we must fire them. In many cases, we will not have enough documentation to validate the ineptitude of such an employee. Furthermore, we may not have a standard algorithm (procedure) to follow when removing this individual. Many companies add the impediment of […]
We have never seen a meaningful employee evaluation system. The abominations are generally designed as a tool to assess the performance of the employee with respect to corporate goals. When they present the illusion of quantification, the values are really qualitative and they will inflate over time as people are ‘soft’ about providing ‘real’ assessment. […]
People in education often like to implement “programs.” In fact, we call this syndrome “program-itis” because it leads to inflammation of the budget. As with many corporation, we see people who want to improve a situation decide to follow “best practices” without verifying that these are, in fact, best practices. They can only be best […]
The Pareto chart (not to be directly confused with the Pareto probability distribution function) is a simple approach to revealing significance in data. Before we plot our chart, we need to complete some initial work: Gather the data in a natural format (count, floating point [decimal], dollars, etc.) Sort the data from high to low […]