Modern Software Practices - by Damon Poole

1
Presentation copyright © 2009-2010 AccuRev, Inc.
May be used with permission only. Contact dpoole@accurev.com for permission.
www.synerzip.com
Modern Best Practices for Software
Development and Process Improvement
Damon Poole – CTO, AccuRev

2
www.synerzip.com
About Damon Poole
 Founder and CTO of AccuRev, a leading provider
of Software Development Tools
 Creator of multiple Jolt-award winning products
 20 years of process improvement leadership
ranging from small co-located teams to 10,000-
person global development shops.
 Frequent speaker at software development events
 Constant interaction with software development
shops of all sizes across many industries

3
www.synerzip.com
Modern Practices
Refactoring
User
Stories
Whole
Teams
Collocation
Backlog
Unit Tests
Continuous
Integration
CI
Multi-Stage
CI
One Piece
Flow
S
I
D
C
WT
D
T
T
Burnup
Chart
Velocity
Planning
Poker

4
www.synerzip.com
Some Practices Have Whole Books Written
About Them

5
www.synerzip.com
The Structure of the Work
Specify
Design
Code
Integrate
Document
Write tests
Test
S D
C I
W
TD

6
www.synerzip.com
The Telephone Game

7
www.synerzip.com
The Telephone Game
?
?
?
?
??
??

8
www.synerzip.com
The Telephone Game
?
?
?
?
??
?? ?
?
?
?

9
www.synerzip.com
The Telephone Game
DS C I
W
T
D
What the…

10
www.synerzip.com
Requirements
 3.4 Customer Identification
• 3.4.1 A web “cookie” shall be used to uniquely identify visitors
• 3.4.2 Each customer shall be associated with a cookie
• 3.4.3 Cookies shall be stored in an RDBMS
 3.5 Sale presentation
• 3.5.1 Each item for sale shall have a button marked “buy” next to
the item
• 3.5.2 Selecting the “buy” action shall trigger an order placement
action
 3.6 Fulfillment
• 3.6.1 By default, all orders shall use the on-file default shipping
information
• 3.6.2 If available, all orders will use the customer’s default payment
method
• 3.6.3 It shall be possible for the customer to cancel any order for
up to 4 hours after they place that order.

11
www.synerzip.com
User Stories
 “As a user I want to order what I am browsing
with a single click.”
 As a <user role> I want to <achieve some goal>

12
www.synerzip.com
Why Use User Stories
 Keeps focus on the customer’s perspective
 Provides a single description used by customer,
product owner, scrum master, developer, tester,
and documenter
 Short term high bandwidth high value
communication
 Separates need and implementation (like an API)
 Simplifies planning
 Well suited for Agile (assumes many quick turns)
 Encourages innovation and creativity at all levels

13
www.synerzip.com
One Piece Flow
Within a release
DS C I
W
T
D
DS C I
W T
D
DS C I
W
T
D

14
www.synerzip.com
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
Within a release
One Piece Flow

15
www.synerzip.com
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
DS C I
W
T
D
Within a release
One Piece Flow

16
www.synerzip.com
S I
D
C
WT
D T
T
One Piece Flow
Developer Test & Doc

17
www.synerzip.com
Collocation
•2-4 megabit
•High latency
•Not always avail.
•Gigabit
•Low latency
•Usually available
5 File servers
5 Db servers
4 App servers
4 Build servers
4 Test environments
San Jose
Boston
ChennaiKiev

18
www.synerzip.com
Collocation
•Low bandwidth
•High latency
•Not always avail.
•High bandwidth
•Low latency
•Usually available
San Jose
Boston
ChennaiKiev
Architect
Developer
Doc writer
Product Manager
Tester

19
www.synerzip.com
Collocation
Infrequent
coordination
San Jose
Boston
ChennaiKiev
Architect
Developer
Doc writer
Product Manager
Tester
Manager
Constant
communication

20
www.synerzip.com
Cross Functional/Whole Team
Developer(s)
Tester(s)
Manager
Doc WriterProduct Manager

21
www.synerzip.com
Testing
System
Integration
C C
C C
C C
C C
C C
C C
Unit

22
www.synerzip.com
Modern Unit Testing
 JUnit & JMock for Java
 NUnit & NMock for C#
 Works best when part of Continuous Integration
 Supports refactoring

23
www.synerzip.com
Refactoring
C C C
C C
C C
C C
•Same functionality
•Better organized
•More maintainable
•Easier to add new functionality
•Joining and splitting methods
•File content changes
•File renames
•Works best with Unit Testing and CI

24
www.synerzip.com
$5M
per lane
$11M
per lane

25
www.synerzip.com
Splitting Work Along Technical Lines
Value A

26
www.synerzip.com
Splitting Work Along Technical Lines
Value A
Back end,
infrastructure
Middle layer
Front end

27
www.synerzip.com
Splitting Work By Value
Value B Value C
Back end,
infrastructure
Middle layer
Front end
Value D

28
www.synerzip.com
Continuous Integration
 Fully automated, 1-step build used by everybody
 Fully automated, 1-step testing used by everybody
 Integration
• Integrate new changes into baseline
• Build
• Test
 Faster feedback
 Everybody on the same page
 Longer runway

29
www.synerzip.com
Continuous Integration
Continuous
Integration
Specify Design Code Integrate
Write tests
Test
Crunch Time
Doc
Big
Bang

30
www.synerzip.com
CI
ws
ws
ws
ws
ws
ws
main
Continuous Integration on Mainline Only
Minutes Hours
Team A
Team B

31
www.synerzip.com
CI
CI
CI
Team A
Team B
ws
ws
ws
Multiple Stages of Continuous Integration
Minutes Hours
int
Daily
ws
ws
ws

32
www.synerzip.com
CI
CI
CI
CI
Team A
Team B
ws
ws
ws
Multiple Stages of Continuous Integration
Minutes Hours
int
Daily
ws
ws
ws
staging ship

33
www.synerzip.com
Managing Priorities
Priority Definition
0 Must have/committed
1 Very important
2 Significant value
3 Minor value
4 Unsure

34
www.synerzip.com
Managing Priorities
Priority Actual Meaning
0 Maybe

35
www.synerzip.com
Managing Priorities
Priority Actual Meaning
0 Maybe
1 Definitely not
2 Definitely not
3 Definitely not
4 Definitely not

36
www.synerzip.com
Backlog Based Prioritization
Business
Value
Issue Story Points State
432 User wants layout pleasing to the eye 2 reviewed
420 User wants example templates to choose from 3 reviewed
419 Admin wants zero installation 5 reviewed
612 Manager wants dashboard view 5 reviewed
599 Admin wants LDAP integration 5 reviewed
831 Admin wants self-serve password reset 2 reviewed
692 User wants automatic todo list generation 2 reviewed
432 User wants easy task entry 1 reviewed
119 User wants subscription-based e-mail notification 5 reviewed
332 Marketing wants fancy splash screen 3 reviewed
516 Admin wants 1-click license update 2 reviewed
533 User wants app to be ready in 3 seconds or less 5 reviewed
619 User wants app to work using Chrome 5 reviewed
$$$
$

37
www.synerzip.com
Using Story Points for Estimation
 Different people may take different amounts of time
to perform the same task
 Estimating in hours mixes together the scope of the
work that needs to be done with the speed at which
a particular individual can do that work
 Story points are a relative measure of the scope of a
user story
 Story points separate out the “what” from the “who”
 To use story points, you need to create a relative
scale of scope for reference

38
www.synerzip.com
Planning Poker
 An Agile estimation technique
 Often uses story points as estimation units
 Leverages the collective wisdom of the whole
team
 Helps to build a sense of team and shared
responsibility
 “We’re all in this together”
 Discourages division by type of work performed

39
www.synerzip.com

40
www.synerzip.com

41
www.synerzip.com

42
www.synerzip.com

43
www.synerzip.com

44
www.synerzip.com
We’re all
in this
together

45
www.synerzip.com
Velocity
Velocity
10
20
30
40
0
StoryPoints
Time

46
www.synerzip.com
Bringing it All Together
new reviewed todo wip coded tested done
Burnup
10
20
30
40
0
StoryPoints
Backlog

47
www.synerzip.com
Modern Practices
Refactoring
User
Stories
Whole
Teams
Collocation
Backlog
Unit Tests
Continuous
Integration
CI
Multi-Stage
CI
One Piece
Flow
S
I
D
C
WT
D
T
T
Burnup
Chart
Velocity
Planning
Poker

48
www.synerzip.com
Additional Practices for Agile
Product
Owner
$$$
$
Retro-
spectives?
Short
Iterations
Iteration
Review
Daily
Standup

49
www.synerzip.com
Poll/Resources/Q&A
 Damon Poole
dpoole@accurev.com
http://damonpoole.blogspot.com
http://twitter.com/damonpoole
 Continuous Integration, Paul M. Duvall
 User Stories Applied, Mike Cohn
 Refactoring, Martin Fowler
 JUnit Recipes, J.B. Rainsberger
 The Art of Unit Testing, Roy Osherove

50
www.synerzip.com 5050
50
Questions?
www.synerzip.com
Hemant Elhence
hemant@synerzip.com
469.322.0349

51
1. Software product development partner for small/mid-
sized technology companies
 Exclusive focus on small/mid-sized technology companies
 By definition, all Synerzip work is the IP of its respective clients
 Deep experience in full SDLC – design, dev, QA/testing, deployment
 Technology and industry domain agnostic
2. Dedicated team of high caliber software professionals
 Seamlessly extends client’s local team, offering full transparency
 NOT just “staff augmentation”, but provide full mgmt support
3. Actually reduces risk of development/delivery
 Experienced team - uses appropriate level of engineering discipline
 Practices Agile development – responsive, yet disciplined
4. Reduces cost – dual-shore team, 50% cost advantage
5. Offers long term flexibility – allows (facilitates) taking
offshore team captive – aka “BOT” option
Synerzip in a Nut-shell

52
Some of Our Clients

53
53
Call Us for a Free Consultation!
www.synerzip.com
Hemant Elhence
hemant@synerzip.com
469.322.0349
Thanks!

Modern Software Practices - by Damon Poole

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie Modern Software Practices - by Damon Poole

Ähnlich wie Modern Software Practices - by Damon Poole (20)

Mehr von Synerzip

Mehr von Synerzip (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Modern Software Practices - by Damon Poole