Topic – Beyond Post Mortems and Lessons Learned
December 10, 2015
PM Connect Agenda – 12/10/2015
Topic Presenter Time
Welcome Note Adrienne Taylor-Barnes 10:00 am
PM Connect Survey Overview Sandy Kruczkowski 10:05 am
EPMO Project Health check update Scott Aziz 10:10 am
Speaker Presentations
• Lessons Learned: Tops from the Trenches
• Project Spotlight: Agile Retrospective
• David Chirokas
• Tosin Davis
10:15 am
Q & A All 11:00 am
Wrap up Shruthi Rangathyagarajan ~11:25 am
3
PM Connect Survey Overview
A few highlights from our Sept. 17, 2015 PM Connect Survey
• What did you like:• Well organized, good energy• Enjoy the networking with new members• Interactive
• What could be improved:• More time for Q&A• Longer time for coverage of topics…• Use the opportunity to announce changes in process that will
affect everyone
.
4
PM Connect Survey Overview
• Best practices for agile projects• Cross collaboration across agencies• How to work with difficult stakeholders • Other PMO government showcases• Procurement• Rescuing projects in trouble• Testing Process• The Importance of having a solid change management plan• Training opportunities and professional development• Use agile techniques within Waterfall projects to gain speed • Ways projects have dealt effectively with roadblocks
Other Topic suggestions
5
Speakers Introductions
Scott Aziz• Role - Quality Assurance Lead at EPMO• At Commonwealth since July 2015• Current Project – Health Check process & Quality Assurance best practices for Capital Projects
David Chirokas• Role - Technical Project Manager, IT PMO (MassDOT)• At Commonwealth since 2009• Current Project - Highway and Infrastructure projects
Tosin Davis• Role - IT Assistant PMO Director (EEA)• At Commonwealth since 2007• Current Project - Statewide Point of Sale Outdoor Recreation Transaction System for Massachusetts Environmental Police and the Competitive Electric Supply System for the Department of Public Utilities
6
EPMO Health Check Update
EPMO Health Check Process – 1st Quarter
• Independent assessment based on objective measures• Inform & Document Status• Insight into project health; Opportunities, Challenges
• 2 triggers: Quarterly planned; On-Demand
• 2 levels: EPMO, 3rd party
• How: Artifact reviews, Surveys, In-person meetings, Reviews
• Scoring model; Dashboard
• ANF Plan – September 30th complete level 1.
The health check includes assessment of:Scope, Cost, Time, Quality, Resources, Communication, Risks, Contingency Planning, Benefits, Training, Implementation, Governance, Roles and Responsibilities, Requirements, and General Lifecycle Activities.
EPMO Health Check Process – 2nd Quarter
• ANF portfolio complete; MASSIT started; EHS started• 1st round EHS to be complete early Jan• 2nd round to start for ANF End Dec/Early Jan
• 42 recommendations for ANF portfolio• Themes:
• Sprint reviews to be more inclusive • Risk management process improvements• Stronger QA processes
• Build certification tests• Automation
• Survey Feedback• Very positive; Collaborative approach• Some questions that reveal gaps are not easy conversations, but
necessary
The health check includes assessment of:Scope, Cost, Time, Quality, Resources, Communication, Risks, Contingency Planning, Benefits, Training, Implementation, Governance, Roles and Responsibilities, Requirements, and General Lifecycle Activities.
9
Lessons Learned Presentation By David Chirokas
10
Agile Retrospective By Tosin Davis
Consumer Division Complaint Management SystemSuccess in Failure
Tosin Davis, PMP, CSMEEA IT PMO
ObjectiveDeliver a database system to replace the existing Consumer Division Complaint Database that
facilitates effective management of complaint cases.
Fail Fast Philosophy
• Service Quality Order
• Discontinued support for MS Access Databases
• Shared Services Pilot
Project PlanThe best laid schemes of mice and men …
Conditions for Success • 3 dedicated Subject Matter Experts
• 50% Allocation • Tech Savvy• Highly Motivated
• Engaged Product Owner
• Preexisting system replacement
• Cloud based, vendor implemented system• Rapid Feedback / Rapid Redeployment• More responsive and adaptive to requests
Project Execution… oft go awry. ~ Robert Burns 1785
Conditions for failure• Critical SME on Paternity Leave
• Unconfirmed Business Requirements
• Historic Weather Event• Spike in call volume
Applying Lessons Learned ThroughoutInspect … Adapt …
Weekly Retro / PlanningSprint Stop Continue Start
1) … … … … … … … … … … … … … …
2) … … … … … … … … …
3) … … … … … … … …
4) … … … … … … … … … …
TakeawaysFailure or Success?
Results• 3 Month Duration
• ~$12k spent out of $200k budget
• Bad news delivered quickly and often
• Fast transition to alternate plan
Q & A?
18
Wrap up & Next steps
• Next PM Connect meeting (Tentative) Late Spring, 2016
• PDU/SEU Reporting
• Upcoming Survey
Mailbox [email protected]