HATS Lessons Learned June 24, 2008. Pennsylvania Department of Human Services Bureau of Information...
17
HATS Lessons HATS Lessons Learned Learned June 24, 2008 June 24, 2008
-
Upload
allyson-paul -
Category
Documents
-
view
214 -
download
0
Transcript of HATS Lessons Learned June 24, 2008. Pennsylvania Department of Human Services Bureau of Information...
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 22
AgendaAgenda
Ground RulesGround Rules GoalsGoals Lessons Learned Lessons Learned
DefinedDefined The TeamThe Team Game PlanGame Plan Action PlansAction Plans Next StepsNext Steps
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 33
Ground RulesGround Rules
Turn your cell phone to silent.Turn your cell phone to silent. No interruptions or judgments.No interruptions or judgments. If names MUST be mentioned, If names MUST be mentioned,
keep it professional.keep it professional. no personalities.no personalities.
Contribute openly to the discussion.Contribute openly to the discussion. Identify needed actions explicitly.Identify needed actions explicitly. Others you would like to add?Others you would like to add?
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 44
GoalsGoals
Learn from our experiences.Learn from our experiences. Engage in a dialogue that will give each of Engage in a dialogue that will give each of
us a view of alternative perspectives.us a view of alternative perspectives. Improve team communications.Improve team communications. Create an action plan for application on Create an action plan for application on
future initiatives.future initiatives.
June 24, 2008June 24, 2008 Pennsylvania Department of Human SercicesPennsylvania Department of Human SercicesBureau of Information SystemsBureau of Information Systems
Page Page 55
What is a Lessons What is a Lessons Learned Session?Learned Session?
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 66
Lessons Learned DefinedLessons Learned Defined
A retrospective of past events or actions.A retrospective of past events or actions. Brainstorming ideas for working more Brainstorming ideas for working more
effectively going forward. effectively going forward. Developing actions for applying lessons Developing actions for applying lessons
learned to future initiatives.learned to future initiatives. Improving team communications.Improving team communications.
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 77
The TeamThe Team
FacilitatorFacilitator Hearings & AppealsHearings & Appeals DHS Bureau of DHS Bureau of
Information Systems Information Systems (BIS) (BIS) Project Management Project Management
Office (PMO)Office (PMO) Division of Enterprise Division of Enterprise
Applications (DEA)Applications (DEA) Division of Technology Division of Technology
Engineering (DTE)Engineering (DTE)
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 88
Game PlanGame Plan
Create the TimelineCreate the Timeline Identify positive, neutral, and negative events/actions Identify positive, neutral, and negative events/actions
that occurred during the project.that occurred during the project.
Timeline WalkthroughTimeline Walkthrough What worked well? What worked well? What still puzzles us?What still puzzles us? Prioritize identified issues.Prioritize identified issues.
Action PlanningAction Planning Be reasonable, in terms of what is doable.Be reasonable, in terms of what is doable.
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 99
Create TimelineCreate Timeline
List actual events or milestones in List actual events or milestones in chronological order.chronological order.
Not yet identifying whether it was good or Not yet identifying whether it was good or bad.bad.
Typically this is a shared view of what Typically this is a shared view of what happened when, fact-based.happened when, fact-based.
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 1010
TimelineTimeline
Start DateStart Date Phases/ActivitiesPhases/Activities
StrategyStrategy InitiationInitiation PlanningPlanning Execution & ControlExecution & Control
Project ClosedProject Closed Lessons Learned – June 24, 2008Lessons Learned – June 24, 2008
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 1111
Timeline WalkthroughTimeline Walkthrough
For each event/milestone identify:For each event/milestone identify: what worked.what worked. what did not work.what did not work.
Identify areas to focus on rather than Identify areas to focus on rather than specific solutions.specific solutions.
Give examples.Give examples. Don’t assume or infer.Don’t assume or infer.
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 1212
Areas to ConsiderAreas to ConsiderProject Project
ManagementManagementTechnical Technical
ManagementManagementHuman FactorsHuman Factors OverallOverall
Project PlanningProject Planning RequirementsRequirements CommunicationCommunication Customer Customer SatisfactionSatisfaction
Resource Resource ManagementManagement
SpecificationsSpecifications Team ExperienceTeam Experience Technical Technical SuccessSuccess
Risk ManagementRisk Management Test PlanTest Plan Interaction with Interaction with Project SponsorProject Sponsor
Quality ProductQuality Product
Change ControlChange Control ConstructionConstruction Interaction with Interaction with CustomerCustomer
Product AcceptedProduct Accepted
ProcurementProcurement TestingTesting Interaction with Interaction with ManagementManagement
On TimeOn Time
Budget Budget ManagementManagement
RolloutRollout Management Management SupportSupport
Within BudgetWithin Budget
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 1313
Time-OutTime-Out
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 1414
Action PlanningAction Planning
Prioritize issues to be addressed.Prioritize issues to be addressed. Identify how each issue could be resolved Identify how each issue could be resolved
in the future.in the future. Don’t be too ambitious in any one action.Don’t be too ambitious in any one action. If necessary, decrease the scope of the If necessary, decrease the scope of the
action to something that could be action to something that could be realistically achieved.realistically achieved.
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 1515
Action PlanningAction Planning
What type of action is it?What type of action is it? Short-term fix?Short-term fix? Root cause solution?Root cause solution?
If outside of your sphere of responsibility, If outside of your sphere of responsibility, how can you influence the decision-how can you influence the decision-makers?makers?
Who is responsible for each action?Who is responsible for each action?
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 1616
Next StepsNext Steps
Retrospective output will be Retrospective output will be written and shared with the written and shared with the group.group.
Action Plan will be published Action Plan will be published within the PMO for use on within the PMO for use on future efforts with Hearings future efforts with Hearings and Appeals, as well as with and Appeals, as well as with other BIS supported other BIS supported projects.projects.
June 24, 2008June 24, 2008 Pennsylvania Department of Human ServicesPennsylvania Department of Human ServicesBureau of Information SystemsBureau of Information Systems
Page Page 1717
Thank you for coming! Thank you for coming! Your voice is very important to the Your voice is very important to the
Bureau of Information Systems. We Bureau of Information Systems. We look forwarding to working with you look forwarding to working with you
soon!soon!
Contact: Carole Hussey, 717-772-7980, or [email protected]
