Uploaded byZach Nies
Frame, Build, Measure, Learn: Responding to Change
Zach Nies discusses the necessity of adapting to market changes by framing, building, measuring, and learning in the software development process. He emphasizes the risk of losing market share if companies fail to respond to shifts and highlights the importance of agile practices over traditional planning. The document promotes a balance between execution and exploration to effectively navigate uncertainties in business.
More Related Content
Similar to Frame, Build, Measure, Learn: Responding to Change
Frame, Build, Measure, Learn: Responding to Change
- 1. Frame, Build, Measure,Learn: Responding to Change" Zach Nies – Chief Technologist! www.rallydev.com @zachnies! ©2014!
- 2. Zach Nies Chief Technologist RallySoftware Faculty University of Colorado at Boulder @zachnies www.rallydev.com @zachnies! ©2014!
- 3. The biggest risk youface is changing" www.rallydev.com @zachnies! ©2014!
- 4. Risk: failing to respond tomarket shifts" www.rallydev.com @zachnies! ©2014!
- 5.
- 6.
- 7.
- 8. 90% We have 80% marketshare" 80% 70% Market Share 60% 50% 40% 30% 20% 10% 0% Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Desktop www.rallydev.com @zachnies! Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 2014 Mobile ©2014!
- 9. 90% We need a mobileapp" 80% 70% Market Share 60% 50% 40% 30% 20% 10% 0% Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Desktop www.rallydev.com @zachnies! Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 2014 Mobile ©2014!
- 10. 90% Mobile app specification begins" 80% 70% Market Share 60% 50% 40% 30% 20% 10% 0% Q32011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Desktop www.rallydev.com @zachnies! Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 2014 Mobile ©2014!
- 11. 90% 80% 70% Market Share 60% 50% 40% 30% 20% 10% Startup competitor ships 1.0" 0% Q32011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Desktop www.rallydev.com @zachnies! Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 2014 Mobile ©2014!
- 12. 90% 80% 70% Market Share 60% 50% 40% 30% 20% 10% Startup competitor ships 1.1" 0% Q32011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Desktop www.rallydev.com @zachnies! Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 2014 Mobile ©2014!
- 13. 90% App defined Dev begins" 80% 70% Market Share 60% 50% 40% 30% 20% 10% 0% Q3 2011 Q42011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Desktop www.rallydev.com @zachnies! Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 2014 Mobile ©2014!
- 14. 90% 80% 70% Market Share 60% 50% 40% 30% 20% 10% Startup competitor ships 1.2" 0% Q32011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Desktop www.rallydev.com @zachnies! Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 2014 Mobile ©2014!
- 15. 90% Mobile app ships" 80% 70% MarketShare 60% 50% 40% 30% 20% 10% 0% Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Desktop www.rallydev.com @zachnies! Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 2014 Mobile ©2014!
- 16. 90% 80% 70% Market Share 60% 50% 40% 30% 20% 10% We forever losthalf our market share in one year" 0% Q3 2011 Q4 2011 Q1 2012 Q2 2012 Q3 2012 Q4 2012 Desktop www.rallydev.com @zachnies! Q1 2013 Q2 2013 Q3 2013 Q4 2013 Q1 2014 Mobile ©2014!
- 17.
- 18.
- 19. Time needed to change marketexpectations" www.rallydev.com @zachnies! ©2014!
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37. Huge market shifts canhappen in a year" www.rallydev.com @zachnies! ©2014!
- 38. Are you Agile enough tobalance" www.rallydev.com @zachnies! ©2014!
- 39. operating the business and respondingto change?" www.rallydev.com @zachnies! ©2014!
- 40.
- 41. Create a planto predict the future" www.rallydev.com @zachnies! ©2014! http://www.flickr.com/photos/isaacmao/380257543
- 42. Market research" Product definition" Productrequirements" Detailed plan" Alpha release" Beta release" Final release" FIRST CONTACT WITH CUSTOMERS" www.rallydev.com @zachnies! ©2014!
- 43. Market research" Project definition" Productrequirements" Detailed plan" Alpha release" Beta release" Final release" FIRST CONTACT WITH CUSTOMERS" www.rallydev.com @zachnies! ©2014!
- 44. Market research" Project definition" Projectrequirements" Detailed plan" Alpha release" Beta release" Final release" FIRST CONTACT WITH CUSTOMERS" www.rallydev.com @zachnies! ©2014!
- 45. Market research" Project definition" Projectrequirements" Detailed plan" Alpha release" Beta release" Final release" FIRST CONTACT WITH CUSTOMERS" www.rallydev.com @zachnies! ©2014!
- 46. Market research" Project definition" Projectrequirements" Detailed plan" Development" " Final release" FIRST CONTACT WITH CUSTOMERS" www.rallydev.com @zachnies! ©2014!
- 47. Market research" Project definition" Projectrequirements" Detailed plan" Development" User acceptance testing" " FIRST CONTACT WITH CUSTOMERS" www.rallydev.com @zachnies! ©2014!
- 48. Market research" Project definition" Projectrequirements" Detailed plan" Development" User acceptance testing" Final release" FIRST CONTACT WITH CUSTOMERS" www.rallydev.com @zachnies! ©2014!
- 49.
- 50.
- 51.
- 52.
- 53.
- 54. Obscure the uncertainty with detailsof a false precision" www.rallydev.com @zachnies! ©2014!
- 55. Embrace, reveal and mitigate theuncertainty" www.rallydev.com @zachnies! ©2014!
- 56. Why does this feelunnatural?" www.rallydev.com @zachnies! ©2014!
- 57.
- 58. “the greatest prosperity canexist only when that individual has reached his highest state of efficiency; that is, when he is turning out his largest daily output.”" www.rallydev.com @zachnies! ©2014!
- 59.
- 60.
- 61.
- 62. Assumes: Certainty is high" Goal: Maximize individual efficiency" www.rallydev.com @zachnies! ©2014!
- 63.
- 64.
- 65. Works when:" " Certainty ishigh" www.rallydev.com @zachnies! ©2014!
- 66. Is your business getting morecertain?" www.rallydev.com @zachnies! ©2014!
- 67.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 75.
- 76.
- 77.
- 78. Assumptions Canvas Name: Key Assumption Reminderswill help gift givers Dependent Assumptions Key Assumption Suggestions will motivate givers Dependent Assumptions We know when We can give giving events reasonable will happen suggestions Text messages are acceptable reminders We can send timely text messages We can get receiver preference data Date: Key Assumption Falsified Assumptions We can make money through partner referrals Dependent Assumptions Partners want referral leads We can get Other Assumptions Other Assumptions Facebook adds Recipients will drive want gifts on traffic time A mobile first enough parter product inventory strategy Our leads will buy gifts I-1 www.rallydev.com @zachnies! ©2014!
- 79.
- 80.
- 81.
- 82.
- 83.
- 84.
- 85.
- 86.
- 87.
- 88.
- 89.
- 90.
- 91.
- 92.
- 93.
- 94. Scrum Machine Daily Scrum Product Backlog Refinement Sprint Planning Sprint 1-2Weeks Burndown Chart Product Backlog www.rallydev.com Sprint Backlog @zachnies! Sprint Demo & Review Sprint Retrospective Product Increment ©2014!
- 95.
- 96.
- 97.
- 98.
- 99.
- 100.
- 101.
- 102.
- 103.
- 104.
- 105.
- 106.
- 107.
- 108.
- 109.
- 110.
- 111. One last thingto keep in mind" www.rallydev.com @zachnies! ©2014!
- 112. Technology adoption is ahuman phenomenon " www.rallydev.com @zachnies! ©2014!
- 113.
- 114.
- 115. Need an Agileand human centered approach! www.rallydev.com @zachnies! ©2014!
- 116.
- 117.