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>

 

Deep analysis of the tasks that must happen in an iteration - development, analysis, testing, etc.  Focus on the problems with staggering them too much, and suggestions on how to properly organize the team around those tasks.

When you define a product roadmap, you also define the release dates for your product. Change happens. Your market changes, your customers change, your requirements change. Unpredictable events happen. Your competitors release a new killer feature, your developers have an epiphany (or run into a roadblock). Should you change your release schedule?

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.

Object oriented approach to estimating the effort for a software project.