{"id":1422,"date":"2008-12-02T19:22:05","date_gmt":"2008-12-03T02:22:05","guid":{"rendered":"https:\/\/svapm.org\/2008\/12\/02\/accidental-project-manager-part-3\/"},"modified":"2019-08-07T14:33:07","modified_gmt":"2019-08-07T21:33:07","slug":"accidental-project-manager-part-3","status":"publish","type":"post","link":"https:\/\/svapm.org\/?p=1422","title":{"rendered":"Accidental Project Manager Part 3"},"content":{"rendered":"

Accidental Project Manager Series
\nPart 1<\/a> \/ Part 2<\/a> \/ Part 3<\/a> \/ Part 4<\/a> \/ Part 5<\/a> \/ Part 6<\/a><\/p><\/blockquote>\n

Part 2 of the Accidental Project Manger series talked about key reasons that you are attracted to project management. So now that you are a project manager, what lessons can you learn from other project managers? Read on for some tips.<\/p>\n

Why Are Lessons Learned Important?<\/strong><\/p>\n

Lessons learned is incremental, iterative learning. Learning from project experience is also breaking a cycle; a personal cycle, or helping a project team break an organizational cultural cycle.\u00a0 If an organization doesn’t: it is doomed to repeat it.\"Project<\/p>\n

Success Factor for incorporating lessons learned:<\/strong><\/p>\n

The first is the NIKE principle, just do it.\u00a0 Make time for it.\u00a0 The next is too create your personal learning’s on how to respond to the information.\u00a0 During commutes on the way home, I would think about my project wins and losses, great moments and dumb moments, next steps and action items.<\/p>\n

Acceleration Factor:<\/strong><\/p>\n

Transitioning to thinking to an organizational perspective.\u00a0 On your commute home you can also be thinking: How else can I serve this organization better?\u00a0 What additional value can I drive?<\/p>\n

Next I want to share key accidental project manager lessons learned.\u00a0 Let’s start at the beginning of the project life cycle.<\/p>\n

Lessons Learned #1: Business Case<\/strong><\/p>\n

A business case summarizes the value a project is projected to provide an organization. It is a structured proposal for business improvements.\u00a0 It functions as a decision package for organizational decision-makers.<\/p>\n

How many of you are required to have a completed business case for all projects?<\/p>\n

If there is all this business value provided:it would seem that this practice should be more prevalent. Well: .Life is full of contradictions like me saying this is a brief blog posting.<\/p>\n

Another key element to include in the business case: you also need to state the business value drivers that cause your project to have a unique value proposition.\u00a0 Value drivers are reasons for funding or continued funding and could be:<\/p>\n