Friday 9th October, 2015
2:50pm to 3:20pm
This session will demonstrate some key techniques that help decompose large problems.
Decomposing problems is a key skill that all software developers need, but we’re often not very good at it. Whether it’s stories that take longer than an iteration, or features that can’t be delivered in the expected release, we’ve all seen the problems that tackling an over-large problem can cause.
We’ll work through two detailed examples to demonstrate the value of delivering small, low-fidelity pieces of work early rather than prematurely focusing on fully-polished final versions. One example will walk through development at the implementation level using TDD, while the second will work through an epic, taking it down to stories that can be implemented in one or two days.
By the end of this session, you’ll see that small IS beautiful, and understand just how small, small can really be.
Dispassionate software developer/consultant/coach working with teams adopting and refining their agile practices. bio from Twitter
Consultant, coach, designer, analyst and developer for over 30 years.
Seb has been involved in the full development lifecycle with experience that ranges from Architecture to Support, from BASIC to Ruby. Recently he has been helping teams adopt and refine their agile practices, with a particular focus on collaboration and automated testing.
Regular speaker at conferences and occasional contributor to software journals. Contributing author to “97 Things Every Programmer Should Know” (O’Reilly) and lead author of “The Cucumber for Java Book” (Pragmatic Programmers).
Sign in to add slides, notes or videos to this session