Thursday, March 26, 2009

Project Management from Software Development Perspective

Some days back I've attended a 2-Day conference on Project Management for Software Development though I don't have any academic background in computers but I am an enthusiast who likes to learn technology and I was amazed with the amount and potential of the material presented before us, so much to learn and grasp in those 16 hours from WBS (Work Breakdown structure) to Risk Management, from using the right SDLC (Software Development Life Cycle) to Managing Requirements, Why software projects fail etc. I'll be posting my learnings on this topic in various posts but first let me give you a glimpse of what I've learned in those 2 days...

  • Introduction
    • What is Project Management?
    • Why do we need Project Management?
    • Why Project Management in Software?
    • Common Issues faced by the Software Project Managers

  • Defining a Project
    • The business reason of the project
    • Identifying the project objectives
    • Role of Project Sponsor
    • The project kickoff meeting
    • Managing the project to build customer’s confidence

  • Selection of Right Process Model
    • Comparing various Software Development Lifecycles
    • How to identify the right model?
    • Overview of various prevalent models

  • Estimation - The Black Art
    • Why estimate?
    • What to estimate (efforts, cost, time, etc.)?
    • Various estimation techniques
    • Wideband Delphi method
    • Estimation workshop

  • Planning for Resources
    • Planning for human resources
    • Planning for skills required for project
    • Planning for equipment and other resources

  • Work Breakdown Structure (WBS)
    • How to build WBS
    • Identifying tasks and phases using a WBS
    • Sequencing tasks into a network diagram
    • Constructing Gantt charts to assess resource needs

  • Managing Risks
    • Assessing and analyzing project risk
    • Developing risk management plan
    • Risk handling techniques
    • Planning for contingency

  • Managing Quality
    • What is quality
    • How to identify quality parameters for your project
    • Optimizing quality

  • Managing stakeholders
    • Identifying stakeholders
    • Recognizing their involvements in the project
    • Managing expectations

  • Managing Changes
    • How changes are better for your project
    • How to deal with changes
    • Change management process

  • Progress Tracking and Control
    • Progress tracking parameters
    • Measuring software progress
    • Linking progress to success

  • Closing the Project
    • Administrative closure
    • Legal closure
    • Learning for mistakes
    • Influencing the continual improvement process

So, stay live !!!

No comments: