• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Gopu Pm 200712 Slideshare
 

Gopu Pm 200712 Slideshare

on

  • 1,235 views

New PM Slide show hope fullsy works

New PM Slide show hope fullsy works

Statistics

Views

Total Views
1,235
Views on SlideShare
1,234
Embed Views
1

Actions

Likes
2
Downloads
0
Comments
0

1 Embed 1

https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NoDerivs LicenseCC Attribution-NoDerivs License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Gopu Pm 200712 Slideshare Gopu Pm 200712 Slideshare Presentation Transcript

  •  
  •  
  •  
  •  
  •  
  •  
  • Bust practices in Project Management!
  •  
  •  
  • Many restraints in achieving the OBJECTIVE
    • Not understanding what is required !
    • Neglecting the down side
    • Not being prepared
      • Time
      • Resources
      • Finances
    • Managing people and entities in achieving the objective
    • Lack of Communication
      • Status Reporting | Objectives
    • Lack of approach in how changes are handled
  • Projects become difficult as the key fundamentals are not supported! People Management Process Un Clear or not there Delegated selectively empowered Project Manager Authority Closed to scrutiny Formal & defensive Open to scrutiny Communication Arbitrary Force fit Comprehensive & effective Controls Cash cow syndrome – excesses controlled planned Funding & Budgets Counter productive involvement As customer demands Up to date Management Process Sink or swim Reference Manual Continuous Management Support Nobody Team All Trained Training Inactive Reactive Proactive
  • We need to Model and Manage Projects
    • Why Model?
      • Basis framework for understanding fundamentals
      • Common clarity understanding and vocabulary
      • Visualize - Improve perspective
      • Simplify & therefore broad base understanding
    • A good model of Project management
      • Reflect Reality
      • General Applicability
      • Understandable >> Usable
      • Explicitly defined structure
  • We need to Model and Manage Projects
    • Optimally Achieve Objectives
      • Better understand financial, physical, and human resources
      • Learn from lessons, success, and mistakes of others
    • Reduce failure of Outcomes
    • Improve end results
      • Improved customer relations
      • Shorter development times
      • Lower costs
      • Higher quality and increased reliability
      • Improved productivity
    • Happier teams
      • Better internal coordination
      • Higher worker morale
  •  
  • Dimensions in project Management..
    • Key functions and responsibilities in managing a project
    • Stages in a project
    • Methodologies in managing projects
    Functions & Responsibilities Stages (Lifecycle) Methods
  •  
  •  
  • Current Models - + Confusing & Complex Representation Risk Analyses is serial not continuous Iterative Modeling > Early Wins
    • Spiral model (barry boehm)
      • Iterative process through phases and increasing scale
    Risk Averse Time Consuming Therefore Expensive No perceived progress until end Unsuitable to large real life projects Comprehensive Good for small quick projects Less Complex ~ Simple
    • Water Fall Model (Royce 1970)
      • Stepwise Progresss from phase to phase.
    Framework -No guidance for action 1 st Model – the basis for all other models
    • Linear model (Henri Fayol)
      • 5 elements
        • Plan | Organise | Coordinate | Control | Command
      • 14 principles
  • The Waterfall Model - Software Life Cycle
  •  
  •  
  •  
  • Basic VEE Project Model Understand requirements System Concept User Vallidations System Specification System Verification plan Design Documentation Build Documentation Verification procedures Fab & Assemble Build to Documents Assemble CI Verify CI CI – Design to sepcification Inspect Build to Documentation Validate System to User Decompose & Define Recompose & Develop
  • Visualizing Project Practice!
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •