Dual Track Agile

Remember that our higher order objective is to validate our ideas the fastest, cheapest way possible.  Actually building and launching a product idea is generally the slowest, most expensive way to validate the idea.

https://svpg.com/dual-track-agile/

https://svpg.com/discovery-sprints/

 

How Much Time Should You Spend in Product Discovery?

 by 

https://www.producttalk.org/2018/04/time-in-product-discovery/

I just outlined four key discovery activities:

  1. Defining a desired outcome
  2. Discovering opportunities
  3. Choosing a target opportunity
  4. Discovering solutions

 

View at Medium.com

  • Design thinking (or any upfront discovery method) turns a Business initiative into a prioritised set of Epics
    • answers large questions
      • eg, verticle to play in, Business model, platform to build
  • Lean UX refines those questions into a feature-sized set of customer validated hypotheses
    • answers medium questions
      • eg. targeting specific parts of the service or product offering – perhaps the riskiest assumption or the highest volume and highest value item
  • Agile delivery refines the feature-sized set of customer validated hypotheses into smaller timeboxed activities that result in a beta (code based) launch to a small pool of customers to test within the real world
    • answers detailed questions

 

A similar but slightly different point of view

https://zenexmachina.wordpress.com/2017/07/18/better-together-agile-lean-ux/

 

Screen Shot 2018-04-22 at 4.10.21 pm.png

https://www.devbridge.com/articles/how-to-set-up-dual-track-scrum-in-jira/

  • Plan in Quarters
  • The notion of a hypothesis is not to prove that you are right, alternatively it’s to disprove the wrong ideas quickly

Top 10 Key Tips for Successful Agile Projects

Here are the most popular techniques reported by Agile professionals:

https://www.nngroup.com/articles/ux-success-agile/

Don’t waste time on details that could be worked out further down the line. As Sophie Paxton explains, “prototypes are, by their very nature, disposable” — they need to be just good enough. When creating your wireframes and prototypes, you just need to produce consumable but not necessarily deliverable-worthy designs so that you can communicate them quickly and effectively to the developers.
https://uxplanet.org/5-ways-to-make-your-ux-workflow-agile-8bfcc6d34f1

CONFIGURING ESTIMATION AND TRACKING

https://confluence.atlassian.com/agile/jira-agile-user-s-guide/configuring-a-board/configuring-estimation-and-tracking

See also: