Experience Effectively Applied Specification Workshop, Backlog - PowerPoint PPT Presentation

Experience Effectively Applied Specification Workshop, Backlog Refinement, Stakeholder Interaction and Their Flow Into (Unit)Test and Code m i c h a e l . m a i @ v a l t e c h . c o m Valtech. All Right Reserved.

Why this talk? Starting statements ◼ Developers are brilliant people, … ◻ but why does the outcome not match the business need? ◼ Should the business invest in more brilliant developers? ◻ This doesn’t seem reasonable, but what to change? ◼ It’s a slim dividing line between a well working process ◻ and one that doesn’t.

Michael Mai ◼ Organization Design Consultant ◼ LeSS Coach ◼ Coach for Technical Excellence michael.mai@valtech.com // https://valtech.com // http://www.agilesoftwaredesign.de

A man who carries a cat by the tail learns something he can learn in no other way. Mark Twain

01 Plant Watering Drone section

Rescue your plants Every days – every minute – office plants dies.

Product Vision FOR office habitants WHO like to have a work-able office with plants THE "Plant Watering Drone" IS A unique autonomous service THAT makes your office lovable by rescuing your plants UNLIKE regular office service OUR PRODUCT operates totally autonomous, no need for fueling, no need for charging, no need to tell living and dead plants apart.

Specification Workshop

◼ One topic ◼ Explore diversity ◼ Groups of thinkers discuss ◻ No expert ◻ Just team members ◼ Clarify questions with expert after groups pooled their brains ◼ … iterate SET BASED THINKING

Product Backlog Refinement

Collaboration Structure

Where can you contribute your expertise? … as a non -developer expert ◼ Pile of code ◼ Tabular form ◻ E.g. Unit Test ◻ With pictures

Unit Test

Live demo ◼ Download ◻ Slides, JAR and source code → http://www.agilesoftwaredesign.de/posts/2019/specification-workshop-refinement-collaboration-vienna/

02 Sum it up section

Relations Build up of verifiable statement (aka test) Refinement & Specification Workshop Sprint Planning 2 Unit Test as you go

Frequent mistakes ◼ Don’t mistake ◻ Learn & Validation data set ◼ Don’t mistake ◻ Collaboration tools (e.g. FitNesse) as your sole mean for acceptance testing ◻ Collaboration tools (e.g. FitNesse) as your sole mean for integration testing ◻ Collaboration tools (e.g. FitNesse) as your sole mean for system testing

Frequent mistakes ◼ Don’t fall for ◻ Premature optimization of meeting – developer need to clarify with experts, users and customer directly ◼ Don’t fall for ◻ Prescriptive formats – the Product Backlog consists of items , not (only) of user stories ◼ Don’t fall for ◻ Not testable criteria – each criteria need to be testable

Frequent mistakes ◼ Don’t fall for ◻ Calls like “we need this feature right now” – consider always the business side ◼ Don’t fall for ◻ Talking only tech in refinement – during Backlog Refinement understanding of the problem is key

KISS “Keep it simple, stupid” ◼ Use simple plain decision tables in FitNesse ◻ No library table ◼ Keep processes simple ◻ Understanding over documentation ◻ “living” documentation over 100s of pages of texts ◼ Keep meeting pointed ◻ Include experts, include team members, direct communication

thank you Slides and codes: http://www.agilesoftwaredesign.de/posts/2019/specification-workshop-refinement-collaboration-sgvie19/