KS Dev Methodology Shift
KS All Hands Meeting
Nov. 8, 2012
Agenda
• Purpose of Methodology Shift
• Timing Changes
• Implementing Timing
• Dev Calendar Timing (Changes to Sprints and Milestones)
• Resource Changes
• Team Assignments
• Reporting Lines
• Process Changes
• Questions & Answers
• Link to Google Doc to post questions
2
PURPOSE OF
METHODOLOGY SHIFT
Purpose
• Move us to a truly agile
process – unit of measure is a
sprint, and accepted work is
“done”
– More iterative approach to
development*
– Move away from milestone
perspective, no more planning
and QA weeks
– Minimize contribution to
technical debt*
4
* = issue brought up during last retrospective
Purpose
• PDTs empowered to do more design and
development. This will increase development
velocity
– Increases communication between Services / UX /
PDTs*
– Reduce hand off points*
5
* = issue brought up during last retrospective
Purpose
• …This will increase development velocity
– Better align Services / UX / PDTs*
• BAs, POs, and UX team members were already
tied to PDTs, now they officially move to the
PDT
– PM with PDT POs does all prioritization
– PM has the final say on all requirements and design
decisions
• Move Services Design resources into the PDTs
– PDTs do all services implementation work
6
* = issue brought up during last retrospective
Purpose
• Core focuses on project-level issues
– Product governance, application design review,
and PDT decision support
– Backlog definition and refinement
– UIM and Kitchen Sink
– Service design standards
– Larry and his Core Technical team continue as they
are
• Allows KS to scale as we bring on more PDTs*
7
* = issue brought up during last retrospective
TIMING CHANGES
Timing
• We are adopting the new methodology today
– Thursday Nov 8th
• This milestone (M6) has some analysis work
that was done by Core for the new
functionality, so we are easing into the new
methodology. And we will focus some of our
M6 effort on addressing our technical debt.
9
Timing
• We expect the methodology change will
impact our velocity at first
• Sprints for the rest of the year:
– M6 Sprint #1 Nov 8 – Nov 29th
– M6 Sprint #2 Nov 30 – Dec 20th
– M6 Sprint #2B Dec 21 - Jan 3 (tech debt only)
– M6 Sprint #3 Jan 4th – Jan 17th
10
Timing
• Milestones are NOT time based going forward.
Product Manager (PM) cuts milestones based
on functionality we want the Imp Institution
to provide feedback on. And releases are
done based on functionality the PM wants to
release to the public
11
Timing
• There may be additional sprints in this
milestone, BUT we need to allow:
– Core Analysis team time to plan
– Tech side needs to finish the estimation effort.
• More information will be coming in the next
few weeks on the full functionality we are
slotting for this milestone.
12
RESOURCE CHANGES
Team Structure & Responsibilities
PDT
PDT Lead
PO
Tech
Lead
Test Eng
PDT Dev
PDT Dev
PDT Dev
PDT Dev
PDT Dev
BA
BA
UX
Services
Services
PDT Dev
• All resources
needed are in the
team
• PDT has the ability
to work
independently
• PDT is still
responsible to work
with Core and
follow standards
and policies
Core
Core
Many previously core resources
have now been moved to the PDT
Core UX
William
Core Analysis
Mike
Bob
Core Services
Tom
Jennifer
Mezba
Ruth (20%)
Kevin
Core Tech
Larry
Cathy (20%)
Melissa (50%)
Haroon
Terry (50%)
Andy
15
PDTs
PDts
East Coast
Garey
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Dan E – Tech Lead
Dan S – PO / SME
Rachel – BA
Terry 50% - BA
Kristina - UX
Michael – Services
Charles - Dev
Val - Dev
Chris - Dev
Bonnie - Dev
Cody - Dev
Donald - Dev
Miki - Dev
David - Dev
Hossein - Dev
Mike – Test Eng
West Coast
Cassy
•
•
•
•
•
•
•
•
•
•
•
Glenn – Tech Lead
Steve – PO / SME
Taryn – BA
Melissa 50% – BA
Erik - UX
Sri - Services
Li – Dev
Venkat - Dev
Chong - Dev
Adam – Test Eng
Bob Hurt – UI Dev
NWU SA
Nina
•
•
•
•
•
•
•
•
SW Genis - Dev
Paul - Dev
Christoff - Dev
Peggie - Dev
Danie de Wet – Dev
Liaan – Dev
Alta - UX
Norm - Services
16
PROCESS CHANGES
CORE
A
Features Definition &
Prioritization
Epic Definition, Prioritization, &
Refinement
PDT
PDTs may pull more than one user story for a sprint
SPRINT
Backlog
User story
Definition
Validate design
SVC
UX
through
user testing
High-Level Service Design
UX
UIM components & patterns
Navigation standards
Terminology standards
Kitchen Sink components
PDT
Collaborative
Definition &
Iteration
Sketch &
Wireframe
Done!
Principles
• Iterate
• Design simplest thing that
could possibly meet user goals
• JIT definition & fidelity
Development
QA
UX
Development
Validate UIM
through
user testing
PO & Team Lead
decide it’s ready
For development
Validate user
story design
Implementing Institution (UMD)
PDT
PO
Collaborative
Design &
Development
Validate
product
usefulness &
usability
FD
Feature Definition
FD
Feature Prioritization
A
Epic Definition
PM
Epic Prioritization
• Functional Director sets product vision and direction
• Functional Director defines features
• And sets feature prioritization, with feedback from the
Functional Council, to meet that vision
• May occasionally need to update features and prioritization
19
FD
Feature Definition
FD
Feature Prioritization
A
Epic Definition
PM
Epic Prioritization
• The Core Analysis team takes the Functional Director’s
guidance and breaks features into Epics
• Core Analysis team provides definition to the Epics
• Epic statement; description; links to existing artifacts
• Epics then go into the Product Backlog
• We have only one backlog for everything – epics, technical
debt, UX changes, etc.
20
FD
Feature Definition
FD
Feature Prioritization
A
Epic Definition
PM
Epic Prioritization
• Product Manager prioritizes the Epics based on functional
value
• Prioritization of the backlog will happen on an on-going basis
21
A
Epic Refinement
SVC
UX
Initial Service Design
UIM Additions & Validation
• Core Analysis team reviews prioritized backlog and provides
“enough” detail to each Epic
• Conditions of satisfaction; pain points; considerations
• Core Analysis team shares information with Core UX and Core
Services
22
A
Epic Refinement
SVC
UX
Initial Service Design
UIM Additions & Validation
• Core Services team reviews epics from the backlog
• Contracts, models, description & assumptions, DTO
• Ensures consistency and minimizes upheaval in contracts
• Core Analysis supports business cases and configuration
improves service design and implementation
standards
23
A
Epic Refinement
SVC
UX
Initial Service Design
UIM & Kitchen Sink
• Core UX team reviews epics from the backlog and identifies
new required UIM additions, design templates, or navigation
standards
• Assess technical feasibility with UI Devs
• Validate UIM through user testing
• UI Devs implement UI components and update if needed
• As prioritized through the Product Backlog
24
PDT
PO
PDT
User Story Definition
User Story Prioritization
User Story Design
Collaborative
Definition &
Iteration
PDT
Sketch &
Wireframe
SME User
Testing
User Story Development
Collaborative
Development
design &
development
QA
• The PDT pulls Epic from backlog and breaks it up into one or
more User Stories
• User story statement, conditions of satisfaction, usage data
• May require PDT PO and / or BA to do additional research or
contact Core Analysis or Implementing Institution for additional
business context
25
PDT
PO
PDT
User Story Definition
User Story Prioritization
User Story Design
Collaborative
Definition &
Iteration
PDT
Sketch &
Wireframe
SME User
Testing
User Story Development
Collaborative
Development
design &
development
QA
• Once User Stories are broken down and defined, the PDT PO
will assign priority based on functional value
26
PDT
PO
PDT
User Story Definition
User Story Prioritization
User Story Design
Collaborative
Definition &
Iteration
PDT
Sketch &
Wireframe
SME User
Testing
User Story Development
Collaborative
Development
design &
development
QA
• PDT will iterate on application design, including UI, service
design, and reference configuration
• A new design artifact will need to evolve, driven by PDTs.
• PDT consults with Core when need support, or when app design
standards can’t be followed or aren’t well defined
• PO and PDT Lead determine when artifacts are ready for
development
27
PDT
PO
PDT
User Story Definition
User Story Prioritization
User Story Design
Collaborative
Definition &
Iteration
PDT
Sketch &
Wireframe
SME User
Testing
User Story Development
Collaborative
Development
design &
development
QA
• PDT implements service contracts, develops UI, and loads
reference data
• PDT ensures “definition of done” is met
• Includes functional, UI, services, testing, and
documentation themes
• PDT ensures test coverage is acceptable and all tests passed
• PDT consults with Core when need support, or when app design
standards can’t be followed or aren’t well defined
28
User Story Design & Development
Sprint 1
Sprint 2
Sprint 3
User Story 1
User Story 2
User Story 3
For illustrative purposes only. PDTs will likely work on multiple user stories in a sprint.
Multiple phases (e.g. define and design) also could happen in a single sprint.
PM
II
FD
DM
User Story Acceptance
Product Evaluation
Release Planning
Dev Standards Evaluation
• Product Manager signs off on User Stories after acceptance by
PDT PO
• Or sends the user story back to PDT through the Backlog for
additional iteration
• Core Services and UX leads assist in verifying delivered work
meets product standards
• PM identifies/validates gaps, bugs, and enhancements and
prioritizes them in the backlog
30
PM
II
FD
DM
User Story Acceptance
Product Evaluation
Release Planning
Dev Standards Evaluation
• Product Manager calls a milestone release based on
functionality
• Implementing Institution tests implementability, configurability
and customization (and other –abilities)
• Implementing Institution evaluates functionality and usability
to answer “Can I use this to do my job?”
• PDT responds to questions about their work
• PM reviews feedback, accepts project-level work, and
prioritizes in the backlog
31
PM
II
FD
DM
User Story Acceptance
Product Evaluation
Release Planning
Dev Standards Evaluation
• Functional Director plans release strategy, messaging,
packaging, and ongoing product support
32
PM
II
FD
DM
User Story Acceptance
Product Evaluation
Release Planning
Dev Standards Evaluation
• Dev Manager looks for efficiency gains and improvements to
the development process on an ongoing basis
• Ensures consistent methodology across teams
33
For more information
https://wiki.kuali.org/display/STUDENT/
Development+Methodology
34
Questions?
35