GAM730 Week 3:06 Vision Meeting – Wednesday

Define the vision
“In the 1960s at NASA (National Aeronautics and Space Administration), no matter who you asked what they were doing, control center staff, janitors, programmers, everyone would respond they were putting a man on the moon. A vision like this motivates and excites people and moves them in a common direction to meet it.” – Jim Jones, IBM Manager
The vision focuses on the benefits to the stakeholders, rather than the technical solutions. It includes information about the business, demographics, competition, how the product fulfills a market need, along with a brief overview of the functional requirements. In order to create a robust and future-proof vision, the whole team must be involved in its creation. As with everything in Agile, the vision can change throughout the development process but you want, to begin with, good foundations.
Create a vision that includes:
  1. The mission (vision) – one inspirational and exciting sentence that is easily understood by all.
  2. The business outcomes – the descriptive factors or measures that when compared with the outcome, prove the mission has been achieved.
  3. The business drivers – what the priorities are with regards to the business objectives (speed of delivery, quality, features, risk versus opportunity, and so on).

Once you have the vision you can begin to create user stories. 
  • Assess the needs of the stakeholders with user stories, e.g. As a , I need to , so that .
  • Explore whether there are existing products that already meet the stakeholder’s needs.

Affinity diagram task
As a team, create an affinity diagram that helps you better understand the needs of your stakeholders.
KJ Method:
  1. Generate user stories for all relevant stakeholders (principal, end user, partners, insider).
  2. Group the user stories into related groups.
  3. Identify natural themes, problem areas, and feature sets.
  4. Confirm the user stories are in the proper groups.

Leave a Reply