Successfully reported this slideshow.
Your SlideShare is downloading. ×

Myths of Product Development

More Related Content

Related Books

Free with a 30 day trial from Scribd

See all

Myths of Product Development

  1. 1. De-mystify Product Development @shoaibshaukat Melbourne, 2015 Lean Thinking Agile Product Development
  2. 2. Purpose De-mystify some prevailing product development practices?
  3. 3. Practice #1 “High Utilisation of Resources will improve performance.”
  4. 4. Structures to meet unpredictable demand are different from the structures to meet linear demand. Team 1 Analyse Develop Test Operate Team 2 Analyse Develop Test Operate Team 3 Analyse Develop Test Operate Production Issue Production Issue QA Environment Issue
  5. 5. Practice #1
  6. 6. Little’s Law The average number of things in the system is the product of the average rate at which things leave the system and the average time each one spends in the system. WIP = Avg. Exit rate * Avg. Time Spent in System Avg. Time Spent in System (Cycle Time) = WIP / Avg. Exit Rate Example: A team (5 members) can complete a task in one day – If there are 5 tasks in a batch then Cycle time will become 5 days. Cycle Time = 5 / 1
  7. 7. High utilization of resources increases number of queues and their size. Queues affect economic performance Make WIP inventory visible Change the Management Control System from efficiency to response Selectively increase capacity Limit the number of active projects
  8. 8. Practice #2 “Processing work in large batches improves the economics of the development process.”
  9. 9. Holding Costs = High Transaction cost = Low Holding Costs = Low Transaction cost = High
  10. 10. COST BATCH SIZE Transaction Cost Holding Cost Total Cost Optimal Batch Size
  11. 11. Small batches allows to slash WIP and accelerate feedback -> improves cycle times, quality and efficiency. WORK WORK WORK WORK WORK WORK
  12. 12. Practice #3 “Our development plan is great; we just need to stick to it.”
  13. 13. Our development plan is great; we just need to stick to it. • Planning must respond to change to deliver the right customer value. • Every thing that customers said are not necessary is a product/need. • Customer needs can change during the project. • Lean Startup (or Lean UX) - Build-Measure-Learn (Eric Ries) • Plan based on business value, time criticality and effort. • User preferences or market needs can change abruptly requiring a rethink of the product specifications. • Don’t commit to a solution too early – Leave the decision to last responsible moment – (Mary Poppendieck) • Customers can’t accurately specify their needs for solutions that don’t exist yet. • Familiarity with existing product/process attributes can interfere with ability to express the novel product.
  14. 14. Practice #4 “The sooner the project is started, the sooner it will be finished.”
  15. 15. The sooner the project is started, the sooner it will be finished. Focus: Stop starting – Start Finishing. Value is only realised when delivered to customers. New projects, specially if they use shared resources will almost always create queues and slow down the delivery. Create WIP limits Don’t start a project until it’s value is clearly defined and provides the most benefits to organisation.
  16. 16. Business, IT, Customers, Partners Concept Evolve Deliver Harness Business Business Business IT IT IT Concept Evolve Deliver Harness Concept Evolve Deliver Harness Concept Evolve Deliver Harness LeanExperimentation
  17. 17. Practice #5 “The more features we put into a product, the more customers will like it.”
  18. 18. The more features we put into a product, the more customers will like it …
  19. 19. Less is More. How? MVP (Minimum Viable Product) – a product with a minimum feature set – high enough in value to customer to satisfy a particular need Focus on understanding user needs - understand how they use the products and their problems. Weighted Shortest Job First Bring developers closer to end user. Invest in building capacity to understand user environment.
  20. 20. Practice #6 “We will be more successful if we get it right the first time”!
  21. 21. “We will be more successful if we get it right the first time”! Requiring success on the first pass forces the teams towards the less risky. Innovation is risky by nature! Focus on shorter build times, early feedback, continuous learning! Software product development is complex and risky by nature! Promote experimentation. Embrace failure but celebrate recovering and learning from failure. Invest in automating the tools that help you deliver and learn faster.
  22. 22. Key Take Away Points Make queues and information flow visible Quantify the cost of delays and factor it into your decisions Introduce resource slack where utilisation is highest. Shift focus of control systems from efficiency to response time. Reduce transaction costs to enable smaller batch sizes and faster feedback. Experiment with smaller batches; you can easily revert to large batches if this doesn’t work. Treat the development plan as a hypothesis that will evolve as new information becomes available. Start projects only when you are ready to make a full commitment. Aim for simplicity; Ask what features can be deleted, not just what can be added. Experiment early, rapidly, and frequently, with computer models and physical prototypes, in controlled and real- life customer environments.

Editor's Notes

  • Product development is the process of designing, creating and marketing new products or services to benefit customers. Sometimes referred to as new product development, the discipline is focused on developing systematic methods for guiding all the processes involved in getting a new product to market.
  • This brownbag has only one purpose i.e. look at some product development process/practices and explain them in the light of Lean thinking.
  • October 2010 – Ryder Cup at Celtic Manor (close to London Heathrow)
    Mark Pain – award winning sport photographer
    Cigar guy (bewilderment, confusion, dazed, surprising)
  • In product development the WIP inventory is predominantly invisible.
  • Large batch size – low transaction cost but high holding costs

    Small batch size – high transaction cost but low holding costs
  • How to determine optimal batch size.
  • Small batcheshelp do the continuous deployments.
    Small batches help with localising the problems and we can rectify the problem before it spreads.
    E.g. Would you like your design team to make an upfront design to find out about the problems later by developers or would you prefer to design in small batches and take regular feedback from developers?
    Small batches are less risky.
    Small batches provides early feedback.
    Small batches makes you more efficient by reducing overhead – sounds counter-intuitive but people get better at doing things they do more often. So if you do test planning, testing on a 2 weekly cycle on a small batch – you learn and improve faster.

  • Last responsible moment: in practice this means delaying commitment by building capacity to change into the system. It involves a commitment to work towards a minimum viable products that defers the implementation of features that might be required for future. It is a call to resist gold-plating or dwell too long on the upfront design of the complete solution.
    Your understanding of a solution will evolve along with your understanding of the implication of any decision.
  • A project must not start unless its delivery can be realised by the business in a timely manner. A project delivered by IT but not utilised by business is equal to a project not delivered.
  • Product development teams seem to believe that adding features creates value for customers and subtracting them destroys value. This attitude explains why products are so complicated: Remote controls seems impossible to use, computers take hours to set up, cars have so many switches now and even humble blenders come with some many controls.
  • Getting companies to buy into and implement the principle that less can be more is hard because it requires the extra effort in two areas of product development:

    Defining the problem: Articulating the problem that the developers will try to solve is the most underrated part of the innovation process. Too many companies devote far too little time to it. But this is important as it is where most teams develop a clear understanding of what they goals are generate hypothesis that can be tested and refined through experiments. The quality of a problem statement makes all the difference in a team’s ability to focus on the few features that really matter.

    Determine what to hide or omit: Often customers would prefer a product that just works effortlessly rather than all the technical brilliance build into it. Determining what features to omit is just as important – and perhaps more important than – figuring out which ones to include.Unfortunately many companies in an effort to be innovative throw in every possible bell and whistle without fully considering important factors such as the value to customers and ease of use. When such companies do omit some planned features/functionality, it’s typically because they need to cut costs or have fallen behind schedule or because the team has failed in some other way.

    Instead managers should focus on figuring out whether the deletion of any proposed feature might improve a particular product and allow the team to concentrate on things that truly heighten the overall customer experience. Treat each alleged requirement as hypothesis and testing it in small, quick experiments with prospective customers.

    Dev teams often assume that their products are done when no more features can be added; Perhaps the logic should be reversed: Products get closer to perfection when no more features can be eliminated. As Leonardo da Vinci once said: “Simplicity is the ultimate sophistication.”
  • Many product development projects fail to meet their objectives for budgets, schedules and technical performance. Poor planning, rigid processes and weak leadership all play a role. But another cause that’s
  • To avoid mistakes teams follow a linear process in which each stage (specify, design, build, test, scale, launch) is carefully monitored at review “gates”. Work on the next phase can not commence until the project passes through the gate.

    Successful tests in late stages are celebrated, and surprises, no matter how valuable they are, are considered setbacks. Unfortunately, such a linear process flow can cause project overruns because test feedback is delayed, teams cling to bad ideas longer than they should, and problems aren’t unearthed until it’s expensive to solve them.

    A tolerance for “getting it wrong the first time” can be the better strategy as long as people iterate rapidly and frequently and learn quickly from their failure. Advances in simulation and rapid prototyping technologies have made operating in this fashion vastly easier and less expensive.