iterative planning

Summary for a Project’s Boundaries: Drivers, Constraints, & Floats

In my experience, too many projects are under too much pressure. The sponsors want all of the features, completed in too-short time, with no defects. And, if possible, the sponsors think the project should cost nothing, the team should not need any training, and the team can work in any way, regardless of the desired …

Summary for a Project’s Boundaries: Drivers, Constraints, & Floats Read More »

Create & Manage the Project’s Bounds, Part 3 (Constraints and Floats for Infrequent Delivery)

I wrote about how to pick a driver in Part 1. In Part 2, I wrote about how you might finesse some of the constraints and floats if you can release frequently. What if you’re like this organization, Acme? Acme has been working towards agility for the last couple of years. However, they still have …

Create & Manage the Project’s Bounds, Part 3 (Constraints and Floats for Infrequent Delivery) Read More »

Create & Manage the Project’s Bounds, Part 2 (Constraints and Floats)

In Part 1, I wrote about the origins of drivers, constraints, and floats. I needed them when we only could release the project once to the customers. You saw the questions that help people choose the project driver. What about the constraints and floats? I think of constraints as bounding the project inside the driver, …

Create & Manage the Project’s Bounds, Part 2 (Constraints and Floats) Read More »

Create & Manage the Project’s Bounds, Part 1

Do you know your project’s bounds? Do you know what your sponsors want from your project? For many years, I heard about the “iron triangle.” Sometimes, the triangle was “Scope, Quality, Cost.” Sometimes, it was “Scope, Date, Cost.” It was always three things out of a minimum of four possibilities. I never saw a triangle …

Create & Manage the Project’s Bounds, Part 1 Read More »

Product Planning, Information Persistence, & Product Lifetime

I’ve been thinking a lot about planning recently. Many of my clients want to create long-term plans, based on data with short validity, even for products in a high state of change. I suspect the first question is how much change do you need in your product, not how good your information is, or how …

Product Planning, Information Persistence, & Product Lifetime Read More »

Tactical Ideas for Agile Budgeting, Part 1

Too often, organizations want to budget for an entire year. The managers run around for two or three months in advance of that fiscal year, attempting to predict a ton of things: Estimates for not-well-defined projects or features, Capital equipment or tool needs, “Headcount” aka, people needed. Then, the organization doesn’t finalize the budget until …

Tactical Ideas for Agile Budgeting, Part 1 Read More »

Estimation Article Posted: When to Estimate and When Not to Estimate

Do estimates make you slightly crazed? Maybe you want to roll your eyes at the organization’s confusion between your estimate (guess) and a commitment. You’re not alone. I wrote an article about estimation, How to give IT project estimates—and when not to estimate at all. If you’ve ever struggled with estimating work, give it a read. …

Estimation Article Posted: When to Estimate and When Not to Estimate Read More »