Do You Want to Be Agile?

Start Using These 4 Decision Gates Today.

Do You Want to Be Agile?

Do You Want to Be Agile?

Start Using These 4 Decision Gates Today.

Do You Want to Be Agile? Start Using These 4 Decision Gates Today.

Want to Avoid Driving Your Project Into A Death March?

Software development projects can get out of hand, and it’s hard to know when to hit the brakes.

Do you ever feel pressure to push forward from your boss, shareholders, or customers, but your gut tells you this project is going nowhere?

Decision gates help you know when it’s time to reassess a project. They allow you to evaluate your project status and provide insight into the best path forward.


Want to be agile?

Critical points consistently pop up in any software development project where more information is available, enabling you to make better decisions.

Not all projects are the same. And not all projects are healthy.

So you need to reassess your projects’ health regularly to ensure you are not hanging onto an unhealthy project on a death march towards failure.

Want to make better software project decisions?

As you uncover new information, it sometimes becomes clear the costs or risks of moving forward outweigh the business value.

The trick is to know as soon as possible and adapt.

Why break your project activities into discrete phases?

You need a clear delineation between project phases to get control and avoid runaway projects on death marches.

Never make your next move without considering both the gains and the risks.

Why Now?

“Whereas a novice makes moves until he gets checkmated, a Grand Master realizes 20 moves in advance that it’s futile to continue playing.” - Bill Gaede

Here’s the thing.

Many companies don’t plan for the maintenance and support costs that pile up rapidly if their product becomes popular.

The short-term pressures like finding product-market fit and getting and holding market share distract from planning for long-term sustainability.

The catch is that newer systems with limited functionality are much simpler than mature systems. When a product is brand new, too simple, and immature, it has a low level of complexity because it doesn’t have to adapt to changes in the outside world (yet).

Because of limited foresight, a lack of planning, or an unsustainable software foundation, many companies end up rebuilding their entire system at a massive risk and cost.

Greenfield projects initially avoid the high overhead of maintenance and support because they are not in production. Brownfield projects can sometimes survive a rebuild, but each comes with a high level of risk (for example, how do you know you got it right the second time around?).

What to do?

Regardless of the type of project you are running, you need a post-launch survival plan for your systems.

Therefore, you must plan and establish your maintenance practices ahead of time.

Most initial system development operational models do not scale. And every single one has a tipping point.

Here’s what typically happens:

  • Your technical resources slowly leak away from adding business value as they have to switch focus to growing maintenance pressures.
  • In time, the velocity of providing value to customers degrades. Development velocity decay increases your risk of being outperformed by competitors.
  • Suppose you start with a feature-centric or domain-centric foundation and are not profitable enough to jump to a more sustainable model; you’ll eventually crash and burn under the weight.

Maintenance overhead handicaps your company from innovating.

If you don’t start with a model that paves the way for constant change, competitors will eventually deliver better ways to meet customer needs faster.

This also means establishing a deliberate design for safely failing fast.

Want to avert disaster?

  • Protect yourself by building for sustainability up-front.
  • Assess your project health regularly (every sprint, if possible).
  • Don’t forge ahead without evaluating your project at critical cost escalation points.

Use this alternative “small-spin zoom-in” model. It’ll pay off quickly.

While this model may already be part of your overall project plan, it’s also an excellent tool for driving feature development.

In maintenance and support mode, you can establish the same logical sequence as your overall project on a smaller scale.

Establishing “small-spin zoom-in” feature phases helps you keep your fingers on the pulse of your project.

Here are the project and feature phases where you pivot.

  • Explore & Conceptualize: In the first phase of product development, your team ideates and defines your product objectives. This phase includes market research, customer analysis, and product concept development.
  • Specify & Design: This phase is when your product development team plans and designs the overall structure of the software application. They also decide which technologies and tools to build the software. This phase also includes surfacing business constraints, discovering use cases, and creating prototypes and mockups of the software to help visualize how the final product will look and work—and validating assumptions with customers.
  • Build & Deliver: This is the largest, riskiest, and most expensive stage. Your costs increase 10x or more than all other prior phases because you need to use labor to execute your plans. Keep it as small as possible, ship fast, and prepare ahead for surprises.
  • Maintain & Support: While maintenance and support are primarily about extending your system, it also covers defect fixes, debt pay down, and technological innovation. During this phase, you can zoom in and have each feature follow this development model.
  • Retire & Cleanup: All software eventually dies. It could be in months, or if you plan for it, your systems can live for decades. It’s up to how much you invest before construction. Retirement is the final phase when you replace your system.

Assessment Gate Points

At each phase, avoid failure.

Track and categorize all risks.

Then plot your next move by determining if you should push forward, pivot, or cut your losses.

  • No additional risks: Proceed to the next step
  • Manageable risks: Proceed to the next step with a list of critical risk-mitigating actions to execute immediately.
  • Unmanageable risks: Do not proceed to the next step. Invest in research to find solutions or stop the project.
  • Nonviable project: Do not proceed to the next step. Cut your losses. Cancel construction and reassess.

Assessment Gate Workflow

Any project suffers when you overlook early planning activities, move forward with incorrect assumptions, or can’t adapt to changes in business circumstances.

Knowing everything up front is impossible, so preparing for the unexpected is your best bet.

In summary:

The best time to ensure success is early in your project by planning.

Start with a solid plan to pave the way for constant change.

It doesn’t have to be perfect. You can always pivot when you have more information.

A healthy system has a support structure that can grow, change, and last, both from a technical and a process point of view.

By following the steps above, you can systematically improve your team’s ability to know when to move forward, when to pivot, and when to cut your losses on a project.

The more flexible and adaptable your process is…

  • The less likely you are to miss critical cost-escalation points
  • You can avoid unplanned technical and business changes overwhelming your team.
  • You increase your chances of success while reducing the waste of time and money.

Even though long-term success isn’t usually planned for at the beginning, every product manager needs to be ready to handle the pressures of success.

Planning for the day you need to support your system is like forecasting the weather for a trip. While seeing what things will look like when you arrive is vital, preparing for the storms that might hit along the way is also essential.

The best way to ensure your project works out is to plan for what you don’t know, establish a solid operational evaluation foundation, and set appropriate project expectations.

Best wishes and warm regards, —Matt


By the way…

Are you ready to run successful software development projects?

Truthshield has seasoned technical product owners who know what it takes. Whether you’re just starting or you’ve been in the industry for years, we have the skills and expertise to help you produce successful software.

Use our comprehensive services to provide your business with the technology, experience, and tools you need to succeed.

We help you execute your software products successfully.

We’ll even turn your idea into working software if you want it the easy way.

Click here now or reach out to set up a call to discuss what you need to succeed.

LET'S WORK TOGETHER

How are we doing?

If you found value here, do me a favor and let us know by taking 5 seconds to share this article. Thanks!
Pinterest
LinkedIn
Reddit
XING
WhatsApp
Hacker News
VK
Telegram

RELATED POSTS


Do You Want to Be Agile?