Skip to main content

Scrum Breakfast/September Introduction to Lean and Agile

Usually I moderate the monthly Scrum Breakfast and leaving the speaking to rotating volunteers. As the Lean Agile Scrum Conference in Zurich takes place next week, I thought an introduction to the basic topics and current trends in project (and company!) management would be an optimal warm-up to the conference. So I am going to take the floor with an

Introduction to Lean and Agile

As a Project Manager, Software Engineer, Line Manager, Business Analyst, Developer, Tester you have probably heard a lot about Lean and Agile. Perhaps you are using some of the major practices, like Scrum, Kanban or Extreme Programming (XP). Why all the hype? Is this just hype, or is a more profound change happening which is driving companies to a leaner, more agile approach to creating value and developing software?

This talk will give your an overview of the current trends in Management and Engineering Practices, in particular as they relate to software product development.
  • What are Lean and Agile?
  • What are the primary practices of each?
  • What are the challenges and failure modes of each?
After attending this talk, you should understand how Lean and Scrum relate to each other, how are they different and what you should watch out for when implementing them in your company.


08:00 
08:35 
Registration, Coffee & Gipfeli
08:35 
09:50 
Talk & Discussion 
09:50 
10:50 
Networking, Coffee & Informal Discussion
Free Coaching! Bring a problem or help with the solution! 3x 20 Minute Sessions in the coaching room.

Time, Location, Registration:
  • Date: Wednesday, 1 September 2010
  • Location: SwissICT, Vulkanstrasse 120, 8048 Zurich (above the Jeep-Dealership).
  • Registration through the SwissICT
  • The LAS core team will meet from 11.00 to 12.30. Interested people are more than welcome!
P.S. If you are not yet a member, please support the SwissICT and become a member! They provide the venue, coffee and gipfeli without charge so this can stay a free event.

Comments

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…