Project Management @ Ektoo

1,864 views

Published on

Project Management @ Ektoo

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,864
On SlideShare
0
From Embeds
0
Number of Embeds
471
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Project Management @ Ektoo

  1. 1. Project Management @ Ektoo<br />Syed Shofiul Alom<br />Sr. Project Manager<br />Ektoo Limited<br />
  2. 2. 1. What is a Project?<br />“A temporary endeavor undertaken to accomplish a unique purpose”<br />“Project Management is a discipline of planning, organizing and managing resources to bring about the successful completion of any specific project goals and objectives ”<br />Beginning<br />Middle<br />End<br /><ul><li>All projects have a beginning, a middle and an end.</li></ul>Program Management: A group of related project managed in a coordinated way<br />
  3. 3. Project..<br />A target outcome<br />A defined life span<br />Cross organisational participation<br />New or unique<br />Time, Cost and performance requirements<br /><ul><li>Projects have a common set of characteristics which c which can also be defined by what they are not an also be defined by what they are not</li></ul>Explorations<br />Go on indefinitely<br />One team or one person working alone<br />Creating the same thing multiple times<br />No constraints on time, cost or performance<br />
  4. 4. The PMBOK’s 9 Knowledge areas<br />Integration<br />Management<br />Time Management<br />Cost Management<br />Scope Management<br />Quality Management<br />HR Management<br />Risk Management<br />Communication Management<br />Procurement Management<br /><ul><li>The first four knowledge areas are Core Functions
  5. 5. Other four knowledge areas are Facilitating Functions</li></li></ul><li>The Triple Constraint<br />Time<br />Quality<br />Scope<br />Cost<br />
  6. 6. Question??<br />If we have success in how we manage projects, <br />what are some of the expected benefits?<br /><ul><li>Improve Profitability
  7. 7. Saving Money (expenses)
  8. 8. More efficient use of existing resources
  9. 9. Reduced stress level
  10. 10. Better time management
  11. 11. Eliminate mistake
  12. 12. Enhanced work environment
  13. 13. Improve teamwork
  14. 14. Better estimating
  15. 15. Accountability
  16. 16. Shortened schedule
  17. 17. Late project create cascading delays
  18. 18. Better focus on goals
  19. 19. Faster reaction to market changes
  20. 20. Closer working relationship with customers
  21. 21. Allow more research to find more SOW
  22. 22. No sacrifice of scope or quality</li></li></ul><li>Challenges<br /><ul><li>Projects are often late and over budget
  23. 23. Projects do not deliver what is really needed
  24. 24. Unexpected event occur that may or may not be involved with the project
  25. 25. Project prioritization
  26. 26. Working on multiple project at the same time
  27. 27. Lose time when test failure occur
  28. 28. Unrealistic timelines, no slacks in schedule
  29. 29. Learning how to use Microsoft Project
  30. 30. Time Reporting Method
  31. 31. Hard to control outside resources</li></li></ul><li>
  32. 32. Driving Forces for Project Management<br /><ul><li>Improving profitability
  33. 33. Increases sales
  34. 34. Reducing expenses
  35. 35. Meeting customer expectations
  36. 36. Executive understanding
  37. 37. Faster New product development
  38. 38. Efficiency and Effectiveness
  39. 39. Creating high performance team</li></li></ul><li>SMART Goal<br />Goals should be SMART:<br /><ul><li> Specific
  40. 40. Measurable
  41. 41. Attainable
  42. 42. Relevant
  43. 43. Time Bound</li></li></ul><li>Project Lifecycle<br />
  44. 44. Plan<br />Monitor & Control<br />Implement<br />Process Groups<br />Initiate<br />Close<br /><ul><li>A process is a series of actions directed towards a particular result.
  45. 45. All projects typically go through these five processes</li></li></ul><li>Initiate Phase Deliverables<br /><ul><li>Objective of the project are agreed to
  46. 46. Scope and approach are established
  47. 47. Initial constraints and assumptions defined
  48. 48. Project Organization with role and responsibilities
  49. 49. High level risk assessment
  50. 50. General Business requirements
  51. 51. Project completion criteria
  52. 52. Initial work plan
  53. 53. Work breakdown structure
  54. 54. Projected milestone
  55. 55. High level cost assessment
  56. 56. Assessment of resource requirement
  57. 57. Project charter
  58. 58. Customer approval</li></li></ul><li>Tool: Project charter<br />A documents that formally authorizes a project<br /><ul><li>Project deliverables – what is the scope of the project and what is excluded from the project scope
  59. 59. Functional requirements
  60. 60. Project Sponsor- person ultimately responsible for the success of the project
  61. 61. Project Manager- Person tasked with day to day management of the project.
  62. 62. Constraints, assumptions and Risk</li></li></ul><li>2. Plan phase Deliverables<br /><ul><li>Detail requirements
  63. 63. Business Process definition
  64. 64. Detail system architecture
  65. 65. High level test cases
  66. 66. Data Analysis
  67. 67. Enhance work breakdown structure
  68. 68. Schedule and budget validated
  69. 69. Risk Plan
  70. 70. Communications Plan
  71. 71. Issue tracking
  72. 72. Quality Plan
  73. 73. Change management Plan
  74. 74. Customer approval</li></li></ul><li>WORK BREAKDOWN STRUCTURE<br />A work breakdown structure (WBS) is a tool used to define and group a project's discrete work elements (or tasks) in a way that helps organize and define the total work scope of the project<br /><ul><li>Break the project in to manageable pieces
  75. 75. Build team commitment
  76. 76. Basis for cost accounting system
  77. 77. Improve estimating, scheduling and risk management
  78. 78. Facilitate clear responsibility assignment
  79. 79. Define a baseline for performance management and control
  80. 80. Create reusable template for future projects.</li></li></ul><li>Tool: Project Scheduling<br /><ul><li>Use the work breakdown structure to identify every project deliverable and activity
  81. 81. Create a precedence network of dependencies
  82. 82. Estimate Task
  83. 83. Add Project buffer and feeding buffer
  84. 84. Assign people resources to each task
  85. 85. Analyze critical path</li></ul>The Critical Path are the sequence of events that will dictate how long it will take to finish the project<br />
  86. 86. Tool: Communication Plan<br />How is your team is going to communicate with each other and others in organization <br /><ul><li>Regular meetings
  87. 87. Written Notes
  88. 88. Change Log
  89. 89. Risk Management Log
  90. 90. Requirements documentations
  91. 91. Status report</li></li></ul><li>3. Execute/Control phase Deliverables<br /><ul><li>Execute the plan
  92. 92. Technology projects
  93. 93. Code
  94. 94. Unit test
  95. 95. System test
  96. 96. Final acceptance test
  97. 97. Hardware deployment
  98. 98. Training
  99. 99. Documentation
  100. 100. Project Management
  101. 101. Measure performance
  102. 102. Change Management
  103. 103. Risk Management
  104. 104. Issue Management
  105. 105. Quality Management
  106. 106. Communications Management</li></ul>Additional details are discovered which are not found during the plan phase <br />
  107. 107. 4. Close Phase<br />Project Closure Phase is the last phase of the Project Life Cycle. The commencement of the Project Closure Phase is determined by the completion of all Project Objectives and acceptance of the end product by the customer.<br />Project Closure includes the following tasks:<br /><ul><li>Release of the resources, both staff and non-staff, and their redistribution and reallocation to other projects, if needed.
  108. 108. Closure of any financial issues like labor, contract etc.
  109. 109. Collection and Completion of All Project Records.
  110. 110. Archiving of All Project Records.
  111. 111. Documenting the Issues faced in the Project and their resolution. This helps other projects to plan for such type of issues in the Project Initiation Phase itself.
  112. 112. Celebrate the Project Completion. Its party time folks!!!</li></li></ul><li>Thank you !!<br />

×