DMG 2016

Solve your problems or get new ideas with basic brainstorming

Get Started. It's Free
or sign up with your email address
Rocket clouds
DMG 2016 by Mind Map: DMG 2016

1. Delivery Assurance

1.1. Q1

1.1.1. Define Supervisor & Program Manager roles

1.1.1.1. Elaborate who is Supervisor? Which part of EPAM set supervisors?

1.1.1.1.1. Is DSv above or under Program Manager?

1.1.1.1.2. Automate calculation risks of assignment

1.1.1.2. Review / elaborate role in PAL

1.1.1.3. Sample of activities / tasks (cases in KB)

1.1.1.4. How not to kill the responsibility from DM?

1.1.2. Define Delivery Supervisor vs. Program Manager assignment process

1.1.2.1. Define Rules of Assignment

1.1.2.1.1. check org units and structures: BU vs. SP vs. Multi-SP setup vs. GDO (aka Core Tech)

1.1.2.2. Document

1.1.2.3. Publish/advertise

1.1.2.4. Integrate into project initiation workflow (UPSA PIRs etc.)

1.1.2.4.1. Improve UPSA PIR fields with more details of project setup - better control on what we deliver and how

1.1.3. Ensure the defined process really followed

1.1.3.1. Assignments

1.1.3.1.1. set some "rules" / KPI for assigment

1.1.3.1.2. Measure how many DMs/DSvs meet defined criteria

1.1.3.2. Delivery Status Check Quality

1.1.3.2.1. % of Green

1.1.3.2.2. Periods of status check

1.1.3.3. Process Quality

1.1.3.3.1. Last access Rate

1.1.3.3.2. % projects vs. best process

1.2. ??? Continue Delivery Assurance based on the Network being built

1.3. Continue hands-on involvement into Delivery Assurance

1.3.1. how to increase DMG/DA capacity???

1.4. HOW TO ENSURE NEW LOCATIONS ARE FOLLOWING RIGHT PROCESSES?

1.4.1. Interview key DMs

1.4.2. Relocation (IM)

1.4.3. Onboarding Guide / Programm

1.4.3.1. Trips

1.5. Simplify DAF

1.5.1. Review materials for clarity

1.5.2. Synchronize Health monitor + DAF + Tools

2. "Staff" DM Network

2.1. Q1

2.1.1. Define a baseline matrix with gaps

2.1.1.1. restructure excel

2.1.1.1.1. 19/02/2016

2.1.1.1.2. lines

2.1.1.1.3. pivot

2.1.2. FILL DM NETWORK CANDIATES

2.1.2.1. https://kb.epam.com/display/EPMDMO/DM+Network

2.1.2.2. https://kb.epam.com/display/EPMDMO/Core+Assurance+DM+Network

2.1.2.3. https://jira.epam.com/jira/secure/RapidBoard.jspa?rapidView=38848

2.1.2.4. e3s

2.1.2.4.1. PM + tech background + team leaders role

2.1.2.4.2. skills

2.1.2.4.3. education

2.1.2.4.4. facet for ASMT

2.1.3. Delivery Assurance Event

2.1.3.1. Role of DSv

2.1.3.2. Sharing of Health.epam.com

2.1.3.2.1. Access Rate increase

2.1.3.3. Cases

2.1.4. ASSIGN DM -> NETWORK ROLE

2.1.4.1. Sell Role to BU

2.1.4.2. Sell Role to SP/ GDO

2.1.4.3. Define

2.2. Q2

2.2.1. Visit major locations

2.2.1.1. Share DMs and Assurance ideas, find promoters in top exec level

2.2.1.2. Identify candidates for open positions via local GEO heads

2.2.1.3. Interview / assess candidates

2.2.1.4. ??? assign to placeholders in the matrix

2.2.2. Delivery Assurance Event

2.2.2.1. Role of DSv

2.2.2.2. Sharing of Health.epam.com

2.2.2.2.1. Access Rate increase

2.2.2.3. Cases

2.3. Q3

2.3.1. Delivery Assurance Event

2.3.1.1. Role of DSv

2.3.1.2. Sharing of Health.epam.com

2.3.1.2.1. Access Rate increase

2.3.1.3. Cases

2.4. EOY

2.4.1. ??? Assess the HEALTH of the Network at the end of 2016

2.4.2. Recap Delivery Assurance Event

2.4.2.1. Role of DSv

2.4.2.2. Sharing of Health.epam.com

2.4.2.2.1. Access Rate increase

2.4.2.3. Cases

2.4.3. Target 2016 – 200 DMs in core assurance net (attached) + on major accounts

3. Motivation/Reward policy

3.1. for DM and DSv roles

3.1.1. Define criteria of successful project / failure / outstanding achievements

3.1.1.1. document and advertise

3.1.2. ??? Work out funding source for DMs reward

3.1.3. Promote/approve the scheme with top mgmt

3.1.4. Verify a scheme is followed in the end of 2016

3.2. Confirm wage ranges

4. CDP

4.1. DM University (M2+)

4.2. DM School 2.0 (M1+)

4.2.1. Attend as traininers

4.2.2. Review modules

4.2.3. Enhance cases

4.2.4. Q2

4.2.4.1. Assurance Programm MOOC

4.2.4.1.1. RAG

4.2.4.1.2. How to track

4.2.4.1.3. How Often

4.3. GROW 2.0 for DM

4.3.1. Review, refine, fill gaps in preset'2015

4.3.2. Collect feedbacks

4.3.2.1. Audience = ?

4.3.3. Measure use / last access rate

4.3.4. Write DM hints or QPF (Jozsef K-B)

4.3.5. Education activities for gaps in DM matrix (Gyorgy B)

4.4. Mentoring

5. Delivery PLATFORM

5.1. Vision & Demo for Board

5.1.1. reviewed with P.Veller

5.1.1.1. create actual plan

5.1.1.1.1. engX

5.1.1.1.2. DMG

5.2. Roles definition

5.2.1. Revitalize role definition for all Key Staff in project props

5.3. Process

5.3.1. what do we mean here?

5.3.2. SDLC 2.0

5.3.2.1. Kanban (4 sessions recorded)

5.4. Tools

5.4.1. Delivery Health Monitor (DHM)

5.4.1.1. Make public quaterly announcements of new features

5.4.1.2. Q1'16 roadmap = see whiteboard

5.4.1.2.1. Mar: now Cases, Status Invalidation are supported

5.4.1.3. Q2'16 roadmap = ?

5.4.1.4. Q3'16 roadmap = ?

5.4.1.5. Q4'16 roadmap = ?

5.4.2. Jira dashboard

5.4.2.1. integrate/merge with IN framework

5.4.2.2. introduce a Portfolio/acct level view

5.4.2.3. further integration with DHM

5.4.3. Gantt chart Plug-in for JIRA

5.4.3.1. Dima Sakavets1

5.4.4. Portfolio/Roadmap Plugin

5.4.4.1. Travix

5.4.4.2. Team working on proposal

5.4.4.2.1. ETA: 1st Apr

5.4.5. JIRA7

5.4.5.1. on staging (1-2MM)

6. SWAT team

6.1. Create a bench of DMs, train for handling RED cases

6.1.1. demand?

6.1.2. locations?

6.1.3. subordination to whom?

6.1.4. available budgets / salary limits?

6.2. Initiate weekly review of RED production projects within DMG

6.3. Propose SWAT capacity for RED projects to appropriate BU heads

6.4. Improve SWAT sustainability => "Time to live" > 1y

6.4.1. ???

7. DONE

7.1. DM Network

7.1.1. Q1

7.1.1.1. AGS Integration

7.1.1.1.1. Initial Integration Activities

7.1.1.1.2. Solution from IN

7.2. Delivery Assurance

7.2.1. Q1

7.2.1.1. Cleanup/review all DM & DSv. assignments for Projects WHERE create date =<3 month from now AND FixFee OR > $500,000k “size”(>10000mh)

7.2.1.1.1. 12/Feb/2016

7.2.1.1.2. check by FTE/resplan

7.2.1.1.3. Algorithm was put in place @Rachynski

7.2.1.1.4. run algorithm