Home » Agile (page 20)

Agile

Minimum Valuable Problem

Defining and building a good minimum viable product is much harder than it sounds.  Finding that “one thing” you can do, which people want, is really about a lot more than picking one thing.  It is a combination of solving the minimum valuable problem and all of the other things that go with it.  Solving for both the outside-in needs and the inside-out goals is ...

Read More »

Making Release Frictionless, a Business Decision, Part 2

In Part 1, I talked about small stories/chunks of work, checking in all the time so you could build often and see progress. That assumes you know what done means. Project “done” means release criteria. Here are some stories about how I started using release criteria. Back in the 70s, I worked in a small development group. We had 5 or 6 ...

Read More »

Hidden Assumption of Agile

Agile cures common problems that we experience in software development, however, there are limitations to Agile.  It may seem like a silver bullet, but there are circumstances under which Agile is not the best choice for development, or at a minimum, not to develop the entire project. The problems with the waterfall model are well known and understood by most ...

Read More »

Surge or pivot? – notes on failure

Failure is good. We learn from failure. Failure is learning; the information content of a failure may be more than the information content of success. Failure isn’t failure, it’s an opportunity to pivot. Failure is capitalism’s Darwinian evolutionary mechanism to remove the less productive, the less relevant. Fail fast, fail cheap, learn, try again. Creative Destruction is the way capitalism remove legacy companies ...

Read More »

Three Considerations For Your Agile Project

As consultants, we have the privilege of helping our clients along their agile journeys. It is always interesting, as each client is on their unique path with various levels of success and challenge in their agile adoption. Most of them are also using traditional project delivery for some of their projects…. And, I have to admit, I love this! As ...

Read More »

You’re doing it wrong: Done-Done

This series is about how to do stuff right by explaining why we do those things we do. If you do, and get the wrong results, you might be doing it wrong. Last time, we talked about the Definition of Done. We use is as vision of where we want to be at the end of the iteration. The question is: What ...

Read More »

8 Tips for Collaborating with the Development Team

Manage the Product, not the Team Focus on your job as the product manager or product owner, and manage the product, not the team. Provide guidance on the product, including its market, value proposition, business goals, and key features. But let the ScrumMaster or coach tackle people, process, and organisational issues; let the development team figure out what needs to be done ...

Read More »

You’re doing it wrong: Definition of Done

In this series, we’re taking a look at what we do in agile, those pesky practices, and why we’re doing them. The purpose is the key here, and if you’re not getting the benefit, you might be doing it wrong, so try something else. So, let me ask you a question: Are you done, done-done, or done-done-done? What does “done”mean anyway? To answer ...

Read More »