TRANSITIONING SOFTWARE DEVELOPMENT AND OPERATIONS...
22
/ Nikola Ivanov, Michael Pack 2016 Project Management Symposium TRANSITIONING SOFTWARE DEVELOPMENT AND OPERATIONS LABORATORY TO AGILE
Transcript of TRANSITIONING SOFTWARE DEVELOPMENT AND OPERATIONS...
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 1
//
Nikola Ivanov, Michael Pack2016 Project Management Symposium
TRANSITIONING SOFTWARE DEVELOPMENT AND OPERATIONS LABORATORY TO AGILE
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 2
//
CATT Lab
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 3
//
CATT Lab Growth
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 4
//
GROWTH CHALLENGES
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 5
//
Functional Organization
Team Responsibility
DBA Team Design, implementation, and maintenance of numerous relational databases.
Java Team Extract, transform, load (ETL) tasks required to integrate new data sources into various CATT Lab databases.
Web Team Development of front-end components showing real-time transportation data.
Analytics Team Development of visual analytics using archived data sets using the Flex application framework.
IT Team Hardware infrastructure to support development and operations. GIS Team Geographic Information Systems (GIS) related support services.
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 6
//
• Diversity of process• Ad-hoc leadership• Work-flow management• Staffing distribution• Management focus-shift• Unified direction
Challenges
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 7
//
STAFFING SOLUTIONS
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 8
//
Hierarchy and structure
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 9
//
Staff diversity
Photo by: Matylda Czarnecka
Photo by: Masa Israel Journey
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 10
//
Staff empowerment
Photo by: Harsh Patel
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 11
//
Work-Flow Solution
TAILORED AGILE PROCESS
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 12
//
Cross-functional teams and co-locationTeam 1 Team 2 Team 3 Team 4 IT Art Support QA
TeamLead
Team Lead
TeamLead
TeamLead
Team Lead
TeamLead
Team Lead
TeamLead
DBA DBA DBA DBASys
AdminsStudents Students Students
FrontEnd Devs
Front End Devs
Front End Devs
Front End Devs
Network Admins
Back End Devs
Back End Devs
Back End Devs
Back End Devs
Students
StudentDevs
StudentDevs
StudentDevs
StudentDevs
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 13
//
Two week sprintsMON TUE WED THU FRI MON TUE WED THU FRI MON TUE WED THU FRI
Team 1 Sprint Plan, Deploy,Retrospective
Team 2 Sprint Plan, Deploy, Retrospective
Team 3 Sprint Plan, Deploy, Retrospective
Team 4 Sprint Plan, Deploy, Retrospective
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 14
//
Sprint planning
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 15
//
Retrospective meetings
Photo by: Adam Binslev
Photo by: tec_estromberg
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 16
//
LESSONS LEARNED
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 17
//
Living process
Implement
EvaluateImprove
Tailored Agile Process
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 18
//
Work estimation
Photo by: Adam Binslev
• Estimation Techniques:
• Analogous
• Proxy
• Parametric
• Three Point
• Planning Poker
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 19
//
Changing priorities• Proactive communication
• Reserve technical lead capacity
• Reduce team size
Photo by: Joan M. Mas
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 20
//
Diverse sprints• Balance versatility and productivity
• Move towards product based cross-functional
teams
• Introduce team rotations
Photo by: Chris Potter
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 21
//
Performance measures• # of issues pushed to next sprint
• # of deployments
• # of issues resolved per developer per sprint
• # of issues resolved per Team Lead per sprint
• Estimate accuracy7
6
3
54
5 54
32
0 01 1
2 23
4 4 4
0
2
4
6
8
1 2 3 4 5 6 7 8 9 10Sprint #
Issues Pushed Deployments
Nikola Ivanov UMD Project Management SymposiumMay 12-13, 2016Slide 22
//
Nikola [email protected]
Questions?
