September 28-30, 2015

Warsaw, Poland

Niels Malotaux is an independent coach and expert in optimizing project performance. He has some 40 year experience in designing electronic and software systems, at Delft University, in the Dutch Army, at Philips Electronics and 20 years leading a systems design company. Since 1998 he devotes his expertise to helping projects and organizations to deliver Quality On Time: delivering what the customer needs, when he needs it, to enable customer success. To this effect, Niels has available very pragmatic approaches like Evolutionary (Evo) Methods, Real Requirements, Early Review and Inspection, Reliable Embedded Systems Design, and Zero Defects. Since 2001, he taught and coached well over 200 projects in 35+ organizations in the Netherlands, Belgium, China, Germany, Ireland, India, Israel, Japan, Romania, South Africa, the UK and the US, which led to a wealth of experience in which approaches work better and which work less well in practice. It’s about time to extend that experience to Poland.

Session: Examples how to move towards Zero Defects

Presentation Slides

How many defects would you like the users of the software to find? How many issues would you accept the users to experience? If you agree that the answer should be “Zero!”, then we can discuss how to achieve that. If you think that’s impossible, you’d better attend and learn, to avoid gradually being put out of business by those who did learn to achieve Zero Defects.

Some people think that we can produce better quality by better testing. Wrong! The most economical way to produce quality is by preventing any problems to creep in in the first place, making sure the users don’t experience any hassle. We’ll discuss a few cases where we used techniques that helped people move towards Zero Defects, like: design, review, the DesignLog, short-circuiting, and using “No Questions, No Issues” as a final test requirement.

Zero Defects is often is dismissed as an impossible dream. My experience tells otherwise. It doesn’t mean “turning a switch and then we don’t produce bugs anymore”. What it does mean you will find out in the presentation.

Session: Evo Planning to produce even more in shorter time

Presentation Slides

Evolutionary Delivery (Evo) is an Agile approach allowing teams to deliver more business value in shorter time, as has been shown in numerous environments like projects for space, building automation, and banking, in waterfall projects as well as Agile/Scrum teams.
Originally, Evo was focused on how to define the ‘real’ requirements for what we’re supposed to do, how to prioritize the order of value delivery, and actively learn from feedback. In order to operationalize this further, Niels added Evo Planning, which is aimed to even further improve both successful as well as timely delivery, continuously increasing the effectiveness, the efficiency, and the predictability of what we do. Evo is actually the mother of all Agile, but most Agile approaches didn’t take the full breath and hence lack some of the benefits.
We’ll introduce the basic Evo Planning techniques: TaskCycles to increase efficiency, DeliveryCycles to increase effectiveness, and TimeLine for oversight and predictability. TimeLine exposes the real status of the work, and when we discover early that we will be late, we effectively deal with it.

Dojo: Evo Planning to produce even more in shorter time

Evolutionary Delivery (Evo) is an Agile approach allowing teams to deliver more business value in shorter time, as has been shown in numerous environments like projects for space (40 man-year saved), building automation, and banking, in waterfall projects as well as Agile/Scrum teams.
Originally, Evo was focused on how to define the ‘real’ requirements for what we’re supposed to do, how to prioritize the order of value delivery, and actively learn from feedback. In order to operationalize this further, Niels added Evo Planning, which is aimed to even further improve both successful as well as timely delivery, continuously increasing the effectiveness, the efficiency, and the predictability of what we do. Evo is actually the mother of all Agile, but most Agile approaches didn’t take the full breath and hence lack some of the benefits.
We’ll introduce the basic Evo techniques: Real Requirements, TaskCycles to increase efficiency, DeliveryCycles to increase effectiveness, and TimeLine for oversight and predictability. TimeLine exposes the real status of the work, and when we discover early that we will be late, we effectively deal with it.
The content is similar to the session “Evo Planning to produce even more in shorter time”, but now we have time to do some exercises. You’ll run a project to deliver Quality on Time, and find out your baseline of estimation, defect delivery, design wit, and requirements recognition. If you bring a list of the most important things you have to work on in the next couple of weeks, you’ll even be able to experience yourself why Evo Planning makes you delivering better results in shorter time.
If you come as a team, you can experience how Evo Planning can make you work more effective and efficient as a team.
Managers can learn what they can and should expect from their development teams.
If you think you are already very effective and efficient, please come and see for yourself what others experienced when they thought the same.
Preparation:
Please read and prepare carefully. The better you prepare, the more you will learn.
Write down:
- The top-3 stakeholders of your work or project (Who is waiting for it?)
- The top-3 real requirements for your work or project (What are they waiting for?)
- How much value improvement the stakeholders expect (3 or 7?)
- Any deadlines (No deadlines: it will take longer)
- What you and your team should and can have achieved in the coming 10 weeks (Will you succeed? - Failure is not an option!)
- What you and your team think they should and can do the coming week in order to achieve what you’re supposed to achieve (Make sure not to plan what you shouldn’t or cannot do - At the end of the week everything you planned will be done)
- What value you will have delivered by the end of the week and how to prove it
- Any issues you expect with the above or otherwise with your work or project
If you find it difficult to write these things down, don’t worry, that’s why we run this workshop. If you come out of the workshop with any change in what you wrote down, this will allow you to work more on more important things, and less on less important things. Better focus on what really is important immediately saves time. The time you spent coming to this conference can be quickly regained by applying the techniques you can learn in this workshop. This may convince your boss to allow you to attend the conference and this workshop. Perhaps he’ll even come with you.


Notice: Undefined index: chkBlock in /home/abe/domains/agilebyexample.com/public_html/wp-content/plugins/eu-cookie-law-consent/index.php on line 35

Notice: Undefined index: chkDebug in /home/abe/domains/agilebyexample.com/public_html/wp-content/plugins/eu-cookie-law-consent/index.php on line 36