To help teams make effective day-to-day decisions that support Lean-Agile principles, we’ve created a simple yardstick at LeanKit called FSGD — Frequent, Small, Good, Decoupled. Easy to remember and apply, “Fizz Good” is a way of breaking down work that reduces the need for cross-team scheduling, estimation and coordination. The results? Faster delivery of customer value. In this webinar, Daniel Norton, co-founder and Chief Mobile Officer at LeanKit, explains how FSGD can help your organization and how to get started.

1. Frequent
Small
Good
Decoupled FSGD
( Fizz Good )

2. what Fizz Good
and
what doesn’t

3. Hurray! Never Again
LeanKit for Construction and Connections and Mobile and
Marketing and SSO and ….
http://leankit.com/blog/2015/07/does-this-fizz-good/

4. We love Lean,
Kanban,
Agile, DevOps
AND

5. FSGD
( Fizz Good )
Frequent
Small
Good
Decoupled

6. Frequent
Small
Good
Decoupled
Annually
Quarterly
Sporadic

7. Release Frequently for …
(IMPROVE IT LATER IF NECESSARY.)
• Feedback
• Visibility into the work
• Opportunity to reprioritize
• Maybe you're done
• Critical issues
• Unplanned work
• Changing business realities

9. "We are getting away from
2 years, 3 years, 4 years,
5 years, to design, build,
test and then deliver a
product. We live in a
world of high levels of
agility; being able to
build, measure, learn;
being able to get on a
faster cadence and a
faster loop where we can
deliver value more
frequently."

10. … and we
don’t just
mean to the
customer

11. It’s tough to
limit WIP with
variable batch
sizes

12. Frequent
Small
Good
Decoupled
Big

13. Some things
are just
naturally big?

14. Some things
are just
notoriously big

15. Why?
Why?
Why?
Why?
Why?
Five Why's
Root Cause Analysis

16. 5 Why example: notoriously big things
Why does it have to be so big?
It does lots of things and has lots of components
Why does it do so many things?
Because they are interrelated.
Why can't they be broken into several releases?
Because it is costly to deploy each of them
Why is that?
Because we do not have an automated testing and release process

17. Round Robin
Scheduling
• Breaking work into smaller
slices
• Just-in-time decision making

18. Round Robin
Scheduling

19. Round Robin
Scheduling

20. Round Robin
Scheduling

21. Round Robin
Scheduling

22. Round Robin
Scheduling
• Smaller batch size allows
flexible reprioritization without
context switching

23. Round Robin
Scheduling

24. Round Robin
Scheduling

25. Round Robin
Scheduling
• What next?
• Project B?
• Bugs?
• Maybe Project C?
• Your choice!

26. Round Robin
Scheduling

27. Round Robin
Scheduling

28. Round Robin
Scheduling
• Oh no. Project B Part 2 is
taking too long.
• Too big!
• Too fat!

29. Stop Digging

30. Round Fat Robin
Scheduling
• Move it aside
• Choose next priority

31. Fat Robin
Scheduling
• Small & Decoupled allow us to
complete, and gain value from,
other portions of the project

32. Fat Robin
Scheduling

33. Fat Robin
Scheduling

34. Fat Robin
Scheduling

35. Fat Robin
Scheduling

36. Fat Robin
Scheduling

37. Fat Robin
Scheduling
• Back to that fat robin
• Break him up into smaller
pieces

38. Fat Robin
Scheduling
• Flow as usual

39. Fat Robin
Scheduling

40. Fat Robin
Scheduling

41. Fat Robin
Scheduling
• What about critical issues?

42. Fat Robin
Scheduling
• Stop the line
• Tools down on other work
• Do not simply add more work
to the team

43. Fat Robin
Scheduling
• Critical issue resolved, back to
usual flow

44. Fat Robin
Scheduling

45. Fat Robin
Scheduling

46. Fat Robin
Scheduling

47. Fat Robin
Scheduling

48. Fat Robin
Scheduling

49. Fat Robin
Scheduling

50. Fat Robin
Scheduling

51. Fat Robin
Scheduling

52. Fat Robin
Scheduling

53. Fat Robin
Scheduling

54. Frequent
Small
Good
Decoupled
Garbage

55. Tested
Logged
Documented
Reviewed
@ifandelse
github.com/ifandelse

56. Frequent
Small
Good
Decoupled
Garbage
Gold-plated

60. Frequent
Small
Good
Decoupled Coordinated

61. Marketing
Team
Browser
Team
Mobile
Team
API
Team
Sales
Team
Releasing a New Feature

62. Decoupled Coordinated

63. Example: Custom Icons

64. Example: Custom Icons

65. Example: Custom Icons
New field in the database, prepopulated … SHIP IT!

66. Example: Custom Icons
Use that to relabel UI in browser … SHIP IT!

67. Example: Custom Icons
Use that to relabel UI in mobile … SHIP IT

68. Example: Custom Icons
Add edit field to browser board edit UI … SHIP IT!

69. Example: Custom Icons
All the pieces are in place. It just works.

70. Example: Custom Icons
ANNOUNCE IT (prewritten … whenever)

71. "These services need to be able
to change independently of
each other, and be deployed by
themselves without requiring
consumers to change. ...
Without decoupling, everything
breaks down for us."

72. Frequent
Small
Good
Decoupled
Coordinated
Damaging

73. Frequent
Small
Garbage
Decoupled

74. Frequent
Small
Good
Damaging
Frequent
Small
Good
Decoupled
Frequent
Small
Garbage
Decoupled

75. Frequent
Small
Good
Decoupled
Frequent
Small
Good
Decoupled
Frequent
Small
Good
Decoupled
Frequent
Small
Good
Decoupled
Frequent
Small
Good
Decoupled

76. Results

77. LeanKit Mobile Team Releases

78. LeanKit Mobile Team Releases
Beta

79. LeanKit Mobile Team Releases

80. Frequent
Small
Good
Decoupled

81. View our FSGD (Fizz Good) content and download this presentation: leankit.com/FSGD
2014 by LEANKIT – Daniel Norton, Jon Terry and Chris Hefley
FSGD (Fizz Good) – A LeanKit Way of Working
FSGD (Fizz Good) is made available under the Creative Commons Attribution-ShareAlike 4.0 International License:
http://creativecommons.org/licenses/by-sa/4.0/