Value Stream Mapping 11 Jan 20 CSI ZG514 Intro to DevOps 59 BITS Pilani Pilani

Value stream mapping 11 jan 20 csi zg514 intro to

This preview shows page 59 - 69 out of 96 pages.

Value Stream Mapping 11-Jan-20 CSI ZG514 - Intro to DevOps 59
Image of page 59
BITS Pilani, Pilani Campus Example-Value stream Mapping- Initial State 11-Jan-20 CSI ZG514 - Intro to DevOps 60 Current State of SW Development Source:
Image of page 60
BITS Pilani, Pilani Campus Example-Value stream Mapping – Future state 11-Jan-20 CSI ZG514 - Intro to DevOps 61 Future State of SW Development – Value is added
Image of page 61
BITS Pilani Pilani Campus 7 G UIDING P RINCIPLES OF L EAN D EVELOPMENT A PPLICABLE TO D EVOPS 11-Jan-20 CSI ZG514 - Intro to DevOps 62
Image of page 62
BITS Pilani, Pilani Campus Waste is effort spend on anything not adding value. Three type of Wastes: Muda: Just “Waste” Needed – e.g. Compliance Not Needed -e.g. Gold platting Muri: “Unevenness” Stopping and Starting, Context Switching Mori: : “overburden” Overburdening a person, process, or system. What is Waste? 11-Jan-20 CSI ZG514 - Intro to DevOps 63
Image of page 63
BITS Pilani, Pilani Campus Principle 1: Eliminate Waste. Principle 2: Build Quality In. Principle 3: Create Knowledge. Principle 4: Defer Commitment. Principle 5: Deliver Fast. Principle 6: Respect People. Principle 7 : Optimize the Whole. We will discuss these lean principles in detail. These principles are vey much applicable to Devops. 7 Principles of Lean Software Development 11-Jan-20 CSI ZG514 - Intro to DevOps 64
Image of page 64
BITS Pilani, Pilani Campus Type of waste in SW Development Unnecessary code or functionality: Delays time to customer, slows down feedback loops Starting more than can be completed: Adds unnecessary complexity to the system, results in context-switching, handoff delays, and other impediments to flow Delay in the software development process : Delays time to customer, slows down feedback loops Unclear or constantly changing requirements: Results in rework, frustration, quality issues, lack of focus Bureaucracy: Delays speed Slow or ineffective communication: Results in delays, frustrations, and poor communication to stakeholders which can impact IT’s reputation in the organization 1. Eliminate Waste 11-Jan-20 CSI ZG514 - Intro to DevOps 65
Image of page 65
BITS Pilani, Pilani Campus Pair programming: Avoid quality issues by combining the skills and experience of two developers instead of one Test-driven development : Writing criteria for code before writing the code to ensure it meets business requirements Incremental development and constant feedback Minimize wait states: Reduce context switching, knowledge gaps, and lack of focus Automation: Automate any tedious, manual process or any process prone to human error 2. Build Quality In 11-Jan-20 CSI ZG514 - Intro to DevOps 66
Image of page 66
BITS Pilani, Pilani Campus Pair Programming Code reviews Documentation Wiki – to let the knowledge base build up incrementally Chat, Chatops Thoroughly commented code Knowledge sharing sessions Training Use tools to manage requirements or user stories 3. Create Knowledge 11-Jan-20 CSI ZG514 - Intro to DevOps 67
Image of page 67
BITS Pilani, Pilani Campus Don’t make decision/commit if you can differ it at later point in time. Keep options open.
Image of page 68
Image of page 69

You've reached the end of your free preview.

Want to read all 96 pages?

  • Winter '19
  • Pilani Campus, Lean software development

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture