Pivotal's Extreme Programming practices

1. © Copyright 2018 Pivotal Software, Inc. All rights Reserved.
20 June 2019
Erika Ito
Andrew Wright
Pivotal Practices
Balanced Team & PCF Demo

2. Balanced Team
© Copyright 2019 Pivotal Software, Inc. All rights reserved.

3. How can we be more agile?

4. How can we structure our teams to be more agile?

5. Balanced Team at Pivotal
Product
Design
Development
Product
Management
© Copyright 2018 Pivotal Software, Inc. All rights reserved.

6. Who are we?
© Copyright 2019 Pivotal Software, Inc. All rights reserved.
Balanced Team

8. Top Open Source Contributor
https://pivotal.io/open-source

9. Our mission is to transform how the
world builds software

10. 10

11. Enable clients to deliver value fast, forever.
Enable through agile
immersion
Deliver business and
user benefits through
live features
Fast releasing quickly
and often
Forever ongoing
basis with no team
burnout
What is Pivotal Labs?

12. Who am I?
Erika Ito
Product Designer at Pivotal Labs
At Pivotal Labs for 3.5 years
Graphic designer → UI designer → Web designer
Mom (has a 11 months old daughter👶🏻)
I’m on Medium! @erikaito

13. What is Balanced Team?
© Copyright 2019 Pivotal Software, Inc. All rights reserved.
Balanced Team

14. Waterfall product development
Plan Design Build
Product
Resease

15. Waterfall product development
Designer
Makes it look pretty
PM
Comes up with
the plan
Dev
Code it
Product
Resease
Months to Years

16. Iterative Cycles, shorter feedback loops
Start Iterate Iterate Iterate
Iteration 1 Iteration 2 Iteration 3
Learn
Build
MeasureLearn
Build
Measure Learn
Build
Measure Learn
Build
Measure
Iteration 4
Agile Product Development

17. History of Agile development
www.the-agilesphere.com
Waterfall Scrum
Agile
Manifesto
1970 1995 2001

18. Team structure didn’t change much...
DesignerPM Dev
Feature
Resease
DesignerPM Dev
Feature
Resease
DesignerPM Dev
Feature
Resease
Week(s) Week(s) Week(s)
Iteration 1 Iteration 2 Iteration 3
Shorter release cycles but linear product development

19. History of Agile development
www.the-agilesphere.com
Waterfall Scrum
Balanced
Team
Agile
Manifesto
1970 1995 2001 2010

20. Balanced Teams
Desirability
“What pains exist today for the
user? How might we solve those
pains? Are they able to use the
system effectively? Will they adopt
this product?
Viability
“By solving these specific user
problems with these specific
solutions, are we creating valuable
business outcomes? How might we
measure those outcomes?
Feasibility
“What are the technical
complexities necessary to satisfy
the project and product goals best?
How can we build a system that
will respond well to change?
Product
Design
Will users like this?
Development
Can we build this?
Product
Management
Will this help the
business?
© Copyright 2018 Pivotal Software, Inc. All rights reserved.

21. All core team members are co-located
Engineers
Designers
PMs

22. Discussions happen as needed
Engineer
DesignerEngineer
Designer
PM

23. Ideate solutions together
Engineer DesignerEngineerPM
DesignerPM

24. Benefits
© Copyright 2019 Pivotal Software, Inc. All rights reserved.
Balanced Team

25. ● Flexibility for change
○ Contexts are shared as needed
○ Questions are asked as needed
● Shared understanding = increased bus count
○ Team is not blocked when someone is out
○ Anyone can take vacations anytime
● Shared product ownership
○ All the roles work together to achieve product goals instead of trying to
“get just their job done” individually
○ Everyone is incentivized to achieve the same success criteria
Benefits

26. Resources
- Balanced Team History: http://www.balancedteam.org/balanced-team-history/
- “Balanced Team” presentation by Janice Fraser: https://www.youtube.com/watch?v=Z_Q4Q8rCVpU
- History of Agile: https://the-agilesphere.com/2016/09/18/the-history-of-agile/

27. Balanced Team
Thank you!

28. Spring Boot and Pivotal Cloud Foundry
Live Demo

30. What we will do
1. Create a “Hello World” page
2. Integrate API with a MySQL database

31. Spring Initializer: https://start.spring.io

32. Built in to IntelliJ Ultimate: