Are your technical and business teams at odds with each other? They don't have to be. Join us tomorrow to discover the secret to gaining alignment.
Dominica DeGrandis, Director of Learning and Development at LeanKit, will share how clarity on priorities, cross-functional dependencies and team metrics drive unity.
You'll learn how to:
- Balance business requests with maintenance work
- Prioritize up, down and across the hierarchy
- Get visibility on cross-functional dependencies
Dominica will share her observations while working at a SaaS company on the methods used to create clarity.
From Divided to United - Aligning Technical and Business Teams
1. From Divided to United –
Aligning Technical & Business Teams
@dominicad
ddegrandis.com
@dominicad
Dominica DeGrandis
Director, Learning
& Development
www.leankit.com
3. improving alignment with clarity
@dominicad
Customers pleased?
Work transparent?
Team structure/measures?
Communication effective?
4. Nashville, TN August 2015
@dominicad
Katie
Sr. Product Marketing Manager
What do you do
when you are unable
to do what you were hired to do?
5. system limits + delayed delivery =
@dominicad
high demand on
application impacts
architecture
and
features not delivered as
expected,
results in sad panda
8. @dominicad
Customers determine business goals
After innovation of
a new tool,
what are the
priorities based
on customer
demand?
feature
#1
feature
#2
feature
#3
9. @dominicad
capacity limits provoked priority convo
collective
agreement by
leadership
reached after
energetic
discussion
✔ prioritize top
3 features
21. Optimize your workflow –
Avoid starting new projects until
done with current project.
@dominicad
22. All team boards roll up to the roadmap
Each team has a team board
where work is broken down into smaller chunks.
roadmap team board
23. From theme to working software
A3
the most valuable thing that fits within a
sweep
(≤ 5 weeks)
DIV: Deployed, Iterative, Value
(≤ 5 days)
Task
DIV
Task Task
Task
A3
DIV
Task
DIV
Task Task
Task
24. Sequence of DIVs add up to A3 value
DIVs deployed
to prod
donein production
26. MKT MKTFIN
UXMKT
MKT MKT
SLS DEVUXUX
SLS CSS
QAUX
DEVOPS SLS
SLS
1
2
3
4
6
5
DEV
DEV
OPS
How the A3 is populated
Cost of Delay?
Impact to users?What benefits who?
What does feature do?
Sustainability impact? fine print /misc?
27.
28. What? So what? What now?
Demo DIV – Each squad has 5 min to demo their DIV*
*DIV – Deployable Iterative Value
36. @dominicad
Number of deployments
is easy to game?
Not so easy when
the qualification of a
deployment is that it must be
related to a DIV*, on the
roadmap.
DIV – Deployable Iterative Value
43. @dominicad
Demo DIV feedback from Biz teams
* DIV - deployed iterative value
“I just want to learn about the things I can sell.
“I don’t want to listen to the technical stuff.”
44. @dominicad
Forum for discussing A3’s
A3 reviews
A3 Wall
• all invited
• context provided
• user perspective
• why’s addressed
• goals explained
• concerns heard
• opinions aired
• feedback welcome
47. @dominicad
What makes a great team?
Google two year study results:
Who is on a team matters less than
how team members interact.
The willingness to talk about errors is
by far the most important factor for a team
Amy Edmonson TED talk:
https://www.youtube.com/watch?v=LhoLuui9gX8
48. Alignment requires absolute clarity
@dominicad
Customers pleased?
Work transparent?
Team structure/measures?
Communication effective?
55. tech stack
@dominicad
.net webservers and SQL DB Servers
Docker hosts node services
Redis for caching and volatile storage
Rabbit MQ for messaging hosted off linux
Puppet for managing infrastructure configuration automation
Tableau for Analytics
56. yes - relational data model limits, but
@dominicad
does the way the
code consumes
the data
factor in?
strangler pattern
in play to tackle
architecture