1.
Vineet ShuklaProduct Management
Cook your product better
story map and no estimate
is the new recipe

2.
context

3.
Things that matter to a team

4.
practices

5.
velocity

6.
timelines

7.
Various charts

8.
feature completion

9.
cost

10.
where is value?

11.
Can we measure value?

12.
Do teams care about value ?

13.
In the end, do we only care about

14.
numbers?

15.
practices?

16.
Yay !!! we followed everything in scrum & XP
Yay !!! we achieved our velocity 

17.
is the team aligned to
product vision?

18.
is team caring about
user feedback?

19.
is team aware what kind of queries do
back officeget ?

20.
is team collaboratively
taking a call on
what to deliver first / next?

21.
is team thinking about the product ?

22.
is it necessary to estimate
every sprint / iteration?

23.
do they know when can we
go live?

24.
do they have enough
visibility?

25.
and a lot more questions came to our mind …

26.
Some of the issues we faced:
•Visibility of the product roadmap
•Next highest priority feature(s)
•Go live dates
•Are we building the right product ? (feedback from beta customers)

27.
how did we solvethese ?

28.
improved Visibility
http://www.cforia.com/images/Visibility_Page_Header.jpg

29.
prioritized at high level as a team

30.
did a lot of
design studios
Design studio is a team activity where a business scenario is shared and the team comes up with various ideas. They draw the user flow and then share it with the team. This helps the team understand what’s coming up and prioritized what’s MVP for that feature.

31.
did story mapping
Feature / Story breakdown
Prioritization

32.
on-boarded beta customers

33.
collaboratively kicked-off a story
and followed INVESTreligiously
I : Independent
N : Negotiable
V : Valuable
E : Estimable
S : Small
T : Testable

34.
and it wasn’t easy 

35.
For our velocitywe looked at number of cards which the team completed within a certain timeframe. That gave us “number of cards completed” per sprint.

36.
we then summedthe number of cards per sprint on the story map wall and calculated projected velocity.
It was always better to start development than spend hours estimating. Velocity would anyways change 

37.
During our planning session we identified goals and focussed as a team to achieve those goals.

38.
We identified two or three goals and prioritizedthem and we did a quick check every alternate dayon how are we doing on our goals.

39.
all these helped us as it gave better clarity and control on what we want to deliver. This also helped as team was empowered and they started valuing product more than the numbers.

40.
Thank You
Vineet Shukla
Vineet.shukla1@gmail.com