Agile Racecar (ARC) & 4WeekStartup (4WS)

Screen+Shot+2019-05-21+at+11.48.09+PM.jpg
Get your own custom, hands-on, Agile Racecar & 4WeekStartup workshops!
Screen Shot 2019-05-19 at 10.36.11 AM.png
Screen Shot 2019-05-19 at 10.37.13 AM.png
Screen Shot 2019-05-21 at 11.47.22 PM.png
Screen Shot 2019-05-21 at 11.47.38 PM.png
Screen Shot 2019-05-21 at 11.48.41 PM.png
Screen Shot 2019-05-21 at 11.48.52 PM.png
Screen Shot 2019-05-21 at 11.49.10 PM.png
Screen Shot 2019-05-21 at 11.49.48 PM.png
Screen Shot 2019-05-21 at 11.50.12 PM.png
Screen Shot 2019-05-21 at 11.50.49 PM.png
Screen+Shot+2019-05-21+at+11.48.09+PM.jpg
Get your own custom, hands-on, Agile Racecar & 4WeekStartup workshops!
Screen Shot 2019-05-19 at 10.36.11 AM.png
Screen Shot 2019-05-19 at 10.37.13 AM.png
Screen Shot 2019-05-21 at 11.47.22 PM.png
Screen Shot 2019-05-21 at 11.47.38 PM.png
Screen Shot 2019-05-21 at 11.48.41 PM.png
Screen Shot 2019-05-21 at 11.48.52 PM.png
Screen Shot 2019-05-21 at 11.49.10 PM.png
Screen Shot 2019-05-21 at 11.49.48 PM.png
Screen Shot 2019-05-21 at 11.50.12 PM.png
Screen Shot 2019-05-21 at 11.50.49 PM.png
sale

Agile Racecar (ARC) & 4WeekStartup (4WS)

from 7,000.00
Number of Attendees:
Quantity:
Learn more about your custom Agile Racecar & 4WeekStartup workshop

User/Customer ACTIVITIES: Features That Evolve, Products That Just Work

Requirements Definitions | Interactive Workshop | Product Management - Advanced

You can bring in multiple "development teams" comprising at least one each of a Product Manager, UX designer, and Software Architect/Engineer, who will participate in this workshop.

  • Defining Product requirements entirely through ACTIVITIES performed by your Users/Customers - without needing to mention even a single FEATURE.

  • Then do the Interaction Design (UX) based on the ACTIVITIES, which in turn will lead to User Stories.

Your teams will then discover with hands-on exercises how to define Product requirements that delight customers and UX designers, reducing product complexity exponentially, reduce the number of  User Stories to a fraction (1/4th to 1/10th).

This will empower your best software architects and developers, and by showing them the path to ship software in lesser and lesser time - by simplifying and even removing User Stories from the Release backlog.

The development teams will learn how to come up with increasingly simplified User Stories by simplifying features that evolve through the Releases - without any change in the underlying Activity.