PLANNED AGILE.

DEVELOPERS

WHAT IS PLANNED AGILE?


Planned agile uses interactive prototyping tools to collaborate with stakeholders during the design phase of the project. The result is an accurate prototype of the project before development starts.

What are the rules for Planned Agile?

There are a few recommendations for including Planned Agile in your agile processes. 

Key Recommendations:

  • Everyone understands the the importance of the prototype.
  • Management buy-in. Stakeholder accountability.
  • Start development after the prototype is signed off.
  • Interactive prototype, not just screenshots strung together.
  • Maintain the prototype. Changes during development are reflected in the prototype.
  • Link the Prototype to user stories and tasks.
  • Determine the (graphic) libraries the developers will use before creating the prototype.  Use prototype elements that conform to those tools.
  • Include the developers in the iterative design reviews.  
  • When possible, adapt the product to the software library.  

Is Planned Agile right for your organization?

Planned Agile is a great addition to a SCRUM methodology.  It works with any Agile Methodology that iterates during the development phase (you’re designing while you’re developing). 

 You keep all of your agile processes. You just shift the iterative design and feedback from development to a prototyping phase.  Stakeholders have the same level of input and feedback.  Using the prototype, your projects will finish sooner with less rework.

COMPARISON BETWEEN METHODS

“Traditional”Agile

Planned Agile

Preproduction

Gather Requirements 

Write User Stories

Create Backlog 

Sprint Zero


Preproduction

Gather Requirements 

Write User Stories


Create Prototype

Feedback/ Iterate 

Refine Prototype 

Tech Reviews 

Sign off


Create Backlog

Sprint Zero

Development

Programmers

Plan - 10%

Code - 20%

Refactor - 30%

Replan - 15%

Recode -25%

Development

Programmers

Plan - 5%

Code - 80%

Refactor - 5%

Replan - 5%

Recode -5%

80% Coding

15% Rework

20% Coding

70% Rework

Who will create the mockups?

Creating a good mockup involves: design, basic programming, and business analytic skills. 

You can hire a prototype designer.  Other good candidates include: business analysts, designers, or other employees with technical skills. Many prototyping tools allow team development, so tasks can be shared among prototyping teams.

Prototyping software tool requirements

Not all prototyping software tools are a good fit for Planned Agile.  Many prototyping tools are great at creating a mockup of a page. But they lack features that add interactivity and stakeholder feedback.  The prototyping software must be able to create an interactive prototype that can emulate all the features of the software.  The user must get the experience of using the program, not just looking at a bunch of screenshots strung together.  Axure RP is an example of a prototype tool that meets these requirements.   

Planned Agile is NOT waterfall development.

In waterfall development, the stakeholders don’t see the final product until it is completed. 

Planned Agile shifts the iterative stakeholder input from the development to the design phase.

Both have the same amount of stakeholder input.

HOW IS THIS A REVOLUTION?

This is a revolution! Because, we want people to break two of the five tenets in the Agile Manifesto.

  • Working software over comprehensive documentation
  • Responding to change over following a plan. 

Planned Agile is an iterative design methodology.


“Traditional Agile” is an iterative development methodology.