Selecting an Appropriate Level of Product Requirements Definition — My Teams Say, “We Don’t Need Requirements, Just Your Money!”

target

Introduction For 20 million years (approximately), one of the age-old discussions in product, IT and software development is whether a team needs clear requirements to build a great product. Occasionally, engineering team members can persuade you (the leader) that requirements are no longer necessary in today’s world (aka “Agile,” “Lean,” “Concurrent,” “Value-driven,” “XYZ-style.”) However, let …continue reading >

Improving Product/System/IT Development with CMMI® for Development* – Quick Look

cmmi-dev-1p3

The CMMI-DEV model is a collection of practices aimed at organizations that develop products, systems and IT solutions. The model is organized into five levels, each level defining more advanced practices to improve schedule, budget, risk and quality performance. The levels provide a road map for sustained incremental improvement. Example development organizations that use CMMI-DEV …continue reading >

When Scrum Uncovers Stinky Issue and Then Gets Blamed

Introduction Scrum is a simple and useful approach for managing software development projects. When performed correctly, it breaks work into manageable pieces and assesses technical risk. Some teams, however, run into trouble very quickly because Scrum is blamed when it uncovers stinky issues. In many cases Scrum is highlighting an existing problem, not causing it. …continue reading >