Managing prioritization with a whiteboard, and the Happy Brian List.

Project management for incremental delivery / iterative development projects by Johanna Rothman

A rolling wave plan is a continuous detailed schedule that's only a few weeks long. As you complete one week of detailed schedule, you add another week to the end of the schedule. With a four- week rolling wave schedule, I never have less than four weeks of detailed schedule, and I never have more than four weeks of detailed schedule.

Very insightful and fun view of how software is made - and how that process has evolved over time.  Great images, great way to explain to "other folks" how software gets created.

An introductory article about making sure you vesion control and maintain traceability over your requirements.

Requirements traceability is an important asect of good requirements management.  If you are new to requirements management or business analysis this is a good introduction to some good practices.

This link is to a series of blog posts on the V-model.  The V-model is a testing and validation framework for software development projects.

This article is useful for business analysts new to the software development world and highlights key quality gates in the development and implementation of software.  The articles focus on what a Business Analyst or Project Manager should know about the process.

The individual posts listed are

<font>Introduction</font>

<font>The value of testing</font>

<font>The V-Model and the development process</font>

<font>Verifying on the way into the development cycle</font>

<font>Testing and verifying on the way out of the development cycle</font>

<font>Extending the V-Model</font>

 

Advice about making sure that release dates are not set arbitrarily, but rather, have associated compelling events.

Commentary and thoughts extending an article by Scott Berkum.  Reviews each of the points from Scott's article and adds additional thoughts.

A two-question survey on which CMMI and RMM levels you use.  Please take a minute to respond to the survey - the data helps Tyner Blain (and ultimately everyone who wants to know) make strategic decisions.

“What CMMI level should we use?” is not the right question, but it is the question most people ask.

The CMMI (Capability Maturity Model Integration) of a software development process is the measure of that process’s capability. The goal of the measurement is to provide an assessment of the capability of a process with respect to creating software.

CMMI is the initialism for Capability Maturity Model Integration.

CMMI is a numeric scale used to “rate” the maturity of a software development process or team. Maturity can be thought of like enlightenment. An immature process is not much different from the old “infinite monkeys” yarn - maybe we get it right, but probably not. A fully matured or enlightened process not only does it right, but improves itself over time.