Agile software development has proven to be more successful than traditional methods. However there are many Agile methodologies (Scrum, Kanban, Lean, XP). It is difficult to make a right choice.
Do you what to know the differences between Scrum and Lean? Perhaps you struggle with your existing Scrum implementation and looking for a better methodology. So did I. I spent many hours looking for continuous improvement beyond Retrospectives and Sprint Reviews. And I found my answer in applying Lean Principles.
This session will help you to increase your understanding of Lean and Scrum. It will also give you some practical examples of implementing Lean in Scrum teams.

 
 

Outline/Structure of the Talk

The materials will be delivered in a lecture format.
There are no exercises planned for this session, although I plan small interactions with the audience:
e.g.: The audience will use thumb voting as an example of feedback technique

Session has the following outline:

1. Introduction and check-in (2 minutes). It will include small check-in exercise to draw attention from attendees.

2. Introduction to Lean (10 minutes). This section will cover history of Lean, differences between Lean in Manufacturing and Software Development, 7 principles of Lean Thinking in Software with examples for each of these principles.

3. Principles of Lean within Scrum (5 minutes). During these 5 minutes I will identifying Lean Principles within Scrum roles, events, processes and artefacts.

4. Lean beyond Scrum (7 minutes). Examples of applying Lean thinking to Scrum team to eliminate waste, amplify learning, build integrity (i.e. product backlog iceberg, test driven development etc)

5. Lean Startup (13 minutes). This session will cover Innovation is Software Development and Learning Experiment as a tool to achieve Innovation. I will cover Lean Startup practices such as Minimum Viable Product, Lean Canvas, Deploy First Code Later, Vanity Metrics.

6. Wrap-up (5 minutes). In this section I will summarise the session and will reiterate main learning points.

7. Questions (3 minutes).

Learning Outcome

This session will clarify similarities and differences between Lean and Scrum.
It will show audience how to carry out continuous improvement techniques beyond Retrospectives and Sprint Reviews using Lean Thinking.
This knowledge will also help people to reboot struggling Scrum teams.

Target Audience

Scrum Masters, Agile Project Managers, Agile Coaches, Managers and Team Leaders

schedule Submitted 6 years ago

Public Feedback


    • Liked Tarang Baxi
      keyboard_arrow_down

      Tarang Baxi / Chirag Doshi - A Practical Guide to Setting up Distributed Agile Projects

      45 Mins
      Talk
      Beginner

      A practical guide to setting up a new agile project team. Based on years of agile delivery and coaching experience for projects in a number of distributed and offshore models, for teams sized from 10 to 200 people, and spread across 4 continents, and 8+ locations. Some areas that will be touched on:

      • People - how to organize distributed teams, cultural factors to consider, ways to build trust, and how to avoid timezone burnout.
      • Process - how to communicate effectively, plan collaboratively, setup distributed practices (standups, retros, pairing, etc), effectively divide work on a common codebase, maintain visibility, and track progress.
      • Tools - (tips provided as a handout) which hardware and software tools should you absolutely invest in to help overcome communication,  visibility and collaboration challenges
    • Liked Dinesh Sharma
      keyboard_arrow_down

      Dinesh Sharma - Offshoring Agile Projects - Myth, lies and Facts

      45 Mins
      Talk
      Advanced

      Offshoring in an agile environment (especially with Indian IT organisation) is always a hot topic within agile communities. You will often find people talk about challenges rather than opportunities with offshoring agile projects e.g.

      • communication challenge,
      • lack of focus on quality,
      • rigid offshore organisation environment,
      • lack of agile practice knowledge,
      • lack of trust etc.

      Although these constraint-cum-challenges often directly linked to offshoring but it can exists in a non-offshore environment as well. For example, to see how you can work effectively with distributed teams you don't need run a project in offshore environment, just split your teams and ask them to sit on a different floor without seeing each other face to face and all these so called offshore challenges will appear in an onsite environment as well.

      So lets understand various Myths, lies and facts about offshoring agile project and understand key ingredients to make it successful.