Managing IT Projects

777 views
720 views

Published on

The basic in managing IT projects and tips on how a Region project manager will handle Worldwide initiated projects

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

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

No notes for slide

Managing IT Projects

  1. 1. Managing IT Projects by Rhys Leong
  2. 2. Agenda <ul><li>What is SDLC? </li></ul><ul><li>Different stages of IT project management </li></ul><ul><ul><li>Project planning </li></ul></ul><ul><ul><li>System Analysis and Requirement </li></ul></ul><ul><ul><li>System Design </li></ul></ul><ul><ul><li>System Implementation </li></ul></ul><ul><ul><li>Testing </li></ul></ul><ul><ul><li>Move to Production </li></ul></ul>
  3. 3. What is SDLC?
  4. 4. Software Development Life Cycle <ul><li>Software Development Life Cycle (SDLC) is a model of a detailed plan on how a software is created, developed, implemented and finally retired. </li></ul><ul><li>Software process </li></ul><ul><ul><li>A set of activities and associated results which produce a software product </li></ul></ul><ul><li>Software process model </li></ul><ul><ul><li>A simplified description of a software process which is presented from a particular perspective </li></ul></ul>
  5. 5. Software process models <ul><li>Different software process models are different approaches to develop a software </li></ul><ul><ul><li>Waterfall model </li></ul></ul><ul><ul><li>Evolutionary development </li></ul></ul><ul><ul><li>Formal systems development </li></ul></ul><ul><ul><li>Reuse-based development </li></ul></ul>
  6. 6. Success implementation of SDLC <ul><li>Factors that contribute to a successful implementation of SDLC: </li></ul><ul><ul><li>Management/stakeholders support </li></ul></ul><ul><ul><li>Availability of both technical and business expertise </li></ul></ul><ul><ul><li>Focal point designation </li></ul></ul><ul><ul><li>Well defined procedures </li></ul></ul><ul><ul><li>Proper documentation </li></ul></ul>
  7. 7. Stages of SDLC <ul><li>Discover business requirement </li></ul><ul><li>Define scope of solution </li></ul><ul><li>Design solution </li></ul><ul><li>Develop and test solution </li></ul><ul><li>Deploy the system </li></ul>
  8. 8. Different stages of IT project management Project Planning
  9. 9. Project Planning <ul><li>Project planning is a stage where development team, project managers and business units will be working together to: </li></ul><ul><ul><li>Identify business requirements </li></ul></ul><ul><ul><li>Estimate investment and reward </li></ul></ul><ul><ul><li>Analyse feasibility </li></ul></ul>
  10. 10. Project charter <ul><li>A project charter or project definition is a statement of the scope, objectives and participants in a project </li></ul><ul><li>A project charter will document: </li></ul><ul><ul><li>Reasons for undertaking the project </li></ul></ul><ul><ul><li>Objectives and constraints of the project </li></ul></ul><ul><ul><li>Directions concerning the solution </li></ul></ul><ul><ul><li>Identities of the main stakeholders </li></ul></ul><ul><li>The main uses of a project charter: </li></ul><ul><ul><li>To authorize the project </li></ul></ul><ul><ul><li>Serves as the primary sales document for the project </li></ul></ul><ul><ul><li>As a focus point throughout the project </li></ul></ul>
  11. 11. Project Planning <ul><li>Objectives and constraints </li></ul><ul><ul><li>Scope, budget, time etc. </li></ul></ul><ul><li>Project organisation </li></ul><ul><ul><li>People involved and their roles </li></ul></ul><ul><li>Risk analysis </li></ul><ul><ul><li>Possible risks and how to manage them </li></ul></ul><ul><li>Resource requirement </li></ul><ul><ul><li>Hardware and software </li></ul></ul><ul><li>Work breakdown </li></ul><ul><ul><li>Milestones and deliverables </li></ul></ul><ul><li>Project schedule </li></ul><ul><ul><li>Dependencies between tasks, allocation of time and people to tasks </li></ul></ul><ul><li>Monitoring and reporting </li></ul><ul><ul><li>Project monitoring mechanisms </li></ul></ul>
  12. 12. Risk management <ul><li>Risk identification </li></ul><ul><ul><li>List of potential risks </li></ul></ul><ul><li>Risk analysis </li></ul><ul><ul><li>Prioritised risk list </li></ul></ul><ul><li>Risk planning </li></ul><ul><ul><li>Risk avoidance and contingency plans </li></ul></ul><ul><li>Risk monitoring </li></ul><ul><ul><li>Risk assessment </li></ul></ul>
  13. 13. Case study: When a Region handles a Worldwide project <ul><li>Region project planning </li></ul><ul><ul><li>Review scope, budget, time etc. and ensure region is able to align. E.g., is the timeline favorable to Region? </li></ul></ul><ul><li>Project organisation </li></ul><ul><ul><li>Determine people in the Region who are involved and their roles. E.g., are they in the core or extended team? </li></ul></ul><ul><li>Risk analysis </li></ul><ul><ul><li>Define possible Region-specific risks and add to Worldwide list. E.g., will project affect a particular downstream system in Region? </li></ul></ul><ul><li>Resource requirement </li></ul><ul><ul><li>Determine availability of hardware and software in Region. E.g., for a project that requires IE8 for testing, what if Region is still using IE6? </li></ul></ul><ul><li>Work breakdown </li></ul><ul><ul><li>Ensure all milestones and deliverables are acceptable by Region. E.g., Region business units sign-off might be required during particular milestones </li></ul></ul><ul><li>Project schedule </li></ul><ul><ul><li>Ensure Region dependencies are considered, and could align to allocation of time and people to tasks. E.g., is the UAT scheduled amidst vacation period in the Region? </li></ul></ul><ul><li>Monitoring and reporting </li></ul><ul><ul><li>Region specific dashboards and reports that filter out unrelated items must be used in Region reporting </li></ul></ul>
  14. 14. Different stages of IT project management System Analysis and Requirement
  15. 15. System Analysis and Requirement <ul><li>System analysis would lead in determining the requirements needed. These requirements should be implemented otherwise the system may not meet business needs. This stage will somehow determine how the system should function. </li></ul><ul><li>All requirements must be listed and classified to ensure that the system will have all the expected properties and could exceed business expectations of the system. </li></ul>
  16. 16. Requirements definition <ul><li>Functional requirements </li></ul><ul><ul><li>Describes the functionality that a system is expected to provide. </li></ul></ul><ul><ul><li>The expected behavior of the system. </li></ul></ul><ul><li>Non-functional requirements </li></ul><ul><ul><li>Emergent system properties, e.g. response time. </li></ul></ul><ul><ul><li>Constraints on the functions, e.g. legislative requirements. </li></ul></ul><ul><li>Domain requirements </li></ul><ul><ul><li>Derived from the application domain of the system </li></ul></ul>
  17. 17. Case study: When a Region handles a Worldwide project <ul><li>Are Region specific requirements taken into consideration? </li></ul><ul><li>Is Region agreeable to priority of requirements? </li></ul><ul><li>How will requirements impact other Region systems? </li></ul>
  18. 18. Different stages of IT project management System Design
  19. 19. System design <ul><li>Developers will work on design of the solution so that the resultant system will meet business requirements </li></ul><ul><ul><li>Interface design </li></ul></ul><ul><ul><li>Database design </li></ul></ul><ul><ul><li>Program design </li></ul></ul>
  20. 20. Different stages of IT project management System Implementation
  21. 21. System Implementation <ul><li>Developers will carry out actual work and evaluate. During this time, developers become users as they try out the system to determine if it is reaching expected performance and output. </li></ul><ul><li>Bugs and errors in the system will surface at this stage. Even if the bugs and errors are already present in the system prior to the project, they will have to be fixed if they affect the project requirements. </li></ul><ul><li>As the system is being developed, developers must document on what they have done in this stage. </li></ul>
  22. 22. Different stages of IT project management Testing
  23. 23. Testing <ul><li>Verification and validation (V&V) is the checking and analysis processes that ensure that the system conforms to its specification and meets business needs. </li></ul>
  24. 24. Testing process <ul><li>Unit testing </li></ul><ul><li>Module testing </li></ul><ul><li>Sub-system testing </li></ul><ul><li>System testing </li></ul><ul><li>Acceptance testing </li></ul>
  25. 25. Testing process <ul><li>Design test cases </li></ul><ul><ul><li>Inputs to the test, expected output from the system and a statement of what is being tested </li></ul></ul><ul><li>Prepare test data </li></ul><ul><ul><li>Inputs which have been devised to test the system </li></ul></ul><ul><li>Run program with test data </li></ul><ul><li>Compare test results to expected outputs </li></ul><ul><ul><li>Generate test reports </li></ul></ul>
  26. 26. Case study: When a Region handles a Worldwide project <ul><li>Determine resource from Region participating in User Acceptance Test (UAT) </li></ul><ul><li>Keep Region testing team in sync with Worldwide testing team </li></ul>
  27. 27. Different stages of IT project management Move to Production
  28. 28. Move to Production <ul><li>After the system is Moved To Production (MTP): </li></ul><ul><ul><li>Business verifies that all business requirements are met </li></ul></ul><ul><ul><li>User acceptance of the system during warranty period, test that the new and existing functionalities are working </li></ul></ul><ul><ul><li>Development team on standby for unexpected bugs and errors found during warranty period </li></ul></ul>
  29. 29. Before the project is closed… <ul><li>Ensure proper documentation of the system </li></ul><ul><li>Present the finalised system to stakeholders </li></ul><ul><li>Provide training to users </li></ul><ul><li>Do a post-mortem review of the project </li></ul>
  30. 30. Case study: When a Region handles a Worldwide project <ul><li>Create Region specific documentation of the system if necessary </li></ul><ul><li>Update changes to operation process in Region if necessary </li></ul><ul><li>Present the finalised system to Region stakeholders </li></ul><ul><li>Provide training to Region users </li></ul>
  31. 31. About me Rhys Leong [email_address] Twitter @cloudywind http:// www.linkedin.com/in/rhysleong

×