Training pm jan 11 part a

  • 390 views
Uploaded on

Presentation for Fast Forward and COnnect Trainees Saxion, 14, 28 January 2011

Presentation for Fast Forward and COnnect Trainees Saxion, 14, 28 January 2011

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
390
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • In order to define project management, we need to understand what a project is. A project is a temporary and one-time endeavor undertaken to create a unique product or service, which brings about beneficial change or added value. Projects have end dates!
  • ASK THE AUDIENCE?? Do we have any project managers in the audience?? Does anyone know what the PM Triple Constraints are? (GIVE CANDY) The PM Triple constraints are the keys to quality and success! These three are interdependent and create quite a balancing act for Project Managers. The time constraint is the amount of time available to complete a project. All projects have deadlines or end dates. This may be the most difficult constraint to manage. The cost constraint is the budgeted amount available for the project. Remember that cost also translates to resources – people, equipment, and materials. The scope constraint is what must be done to produce the project's end result – the system you need – meeting your requirements! These three constraints are often competing constraints: increased scope typically means increased time and increased cost, a tight time constraint could mean increased costs and reduced scope, a tight budget could mean increased time and reduced scope, or managing the project over a longer period of time to take advantage of various funding opportunities without a loss of continuity ! The discipline of project management is about providing the tools and techniques that enable the project team ( not just the project manager ) to organize their work to meet these constraints.
  • The textbook definition of PM is: The application of knowledge, skills, tools and techniques to project activities to meet project requirements And Organizing and managing resources so the project is completed within defined scope, quality time, and cost constraints.
  • ASK THE AUDIENCE – what skills are important? (GIVE CANDY!) (CLICK) The PM doesn’t have to be an expert in the application area but – they do need to understand the application area, the standards required, and the regulations that apply (includes functional, technical, financial, and procurement). (CLICK) Understand the project environment! What are the cultural, social and political characteristics you are doing with? (DON”T TALK ABOUT INTERPERSONAL SKILLS) There are big differences between FSP & WIC - and even more between government and private industry! (think about dealing with contractors!) Educate yourself, listen and try to understand.
  • (CLICK) (CLICK) (CLICK) (READ SLIDE) KEY POINT: The Project Manager is responsible for ensuring the work gets done – not DOING all the work!
  • (CLICK) Define requirements in detail (CLICK) Establish a speedy conflict resolution process! WRITTEN and part of the SOW or Contract (CLICK) Make contingency Plans – if things didn’t go wrong you wouldn’t need a PM ! A risk management plan is NOT a contingency plan. Risk is something you anticipate! Contingency is something you must be ready to react to! (CLICK) Plan a reasonable roll-out schedule. You are not just putting in a new system – you are also changing the way your do business and this has a huge impact. Allow time to deal with it .
  • (CLICK) Communicate objectives frequently – keep everyone on the same page! (CLICK) Recognize different perspectives KEY POINT!!!! Recognize that with the various stakeholders (program staff, IT, workers, management) come different perspectives that are all valuable to the project! Listen!! These reflect their concerns and interests. Repeat them back to make sure you understand! (CLICK) Check assumptions Remember those system goals and objectives we discussed during the alternatives analysis? These need to be reiterated to make sure assumptions stay consistent and are truly reflective of the business case.
  • (CLICK) Identify all stakeholders up front! (CLICK) Develop the project plan before starting the project (CLICK) Establish communications protocols – this should be written. Who reports to who, who carries the message to whom!
  • (CLICK) Manage expectations of all stakeholders – need to be realistic and match the actual work involved. Sometimes states think this will solve all your problems – save time, money, staff, etc. These expectations, if overblown, can cause problems. Be very honest about what the new system will or will NOT do. Don’t give false expectations. Remember change brings a fear factor with it. Assuage fears. Encourage success. (CLICK) Share success and broadcast achievements Broadcast achievements throughout the project – newsletters, e-mails, announcements at meetings – too often only hear about the problems – need to hear the good as well! Use on-line forums or even a project blog. (CLICK) Invite feedback Invite feedback from all stakeholders throughout the project! Good or bad! Be ready to manage it! KEY POINT!!! A Project Manager has to be willing and able to tell the truth to power! Remember PM’s should be empowered and this includes being the messenger to the senior managers – the project champions!
  • Management Reporting is crucial to a successful project – management buy-in and continued sponsorship is dependent upon good communications! Establish reporting requirements upfront (frequency, delivery method (meeting, written, conference call), items to be included. This is where you should establish a change control process. Remember these are management reports – be brief but provide accurate and sufficient information for managers in language they understand about the current status and any issues. Remember the higher up the food chain you go the shorter the attention span, but believe it or not management really does want to know! If they don’t, your project has another problem!
  • A good project team doesn’t mean leaving the uncooperative people out of the room – make the extra effort to co-opt them! Draw on all areas of expertise! You need the subject matter experts on your team! Involve your stakeholders – encourage synergy and collaboration! Being a team member also gives stakeholders a sense of ownership and commitment. Good teamwork makes the Project Manager look good and the project successful!

Transcript

  • 1. Training Project Management Fast Forward Connect Siep Littooij Manager International Project Desk 14, 28 January 2011
  • 2. Getting to know each other
    • Who are you, where from?
    • What degree do you have?
    • What job do you currently have (or want to have)?
    • What learning, what experience do you have with PM
    • What do you expect to learn today?
    • Siep Littooij
    • Sociologist & agriculture engineer
    • 25 years of projects in all shapes/sizes, >10 countries
    • Saxion international fund applications
    • Saxion monitoring implementation of project portfolio
  • 3. Program Reader, presentation http://www.slideshare.net/Littooij Alternatives to the waterfall 1615 14 JANUARY Closing 1700 Discussion, questions 1645 Assignment 2: -Team this project 1545 Project manager skills 1500 Assignment 1: -Do you see a project? 1430 Project management defined 1330 Start, acquaint 1300 PM Tools 5: Performance tracking 1600 28 JANUARY Closing 1700 Discussion, questions 1630 Assignment 5 -Risk Debate 1545 PM Tools 4: Risk 1530 Assignment 4 -Present the Gantt chart 1445 PM Tools 2,3 1430 Assignment 3 -Describe the logframe 1345 PM Tools 1 : LFA 1305 Start 1300
  • 4. Learning Objectives
    • Defining project management
    • The skills of the project manager
    • Tools for project management
  • 5. What is a Project?
    • A temporary and one-time endeavor undertaken to create a unique product or service, which brings about beneficial change or added value
    And it is someone’s responsibility!
  • 6. PM Triple Constraints
    • Time/Schedule
    • Cost/Budget
    • Performance/Results (Scope)
    Manage these or they will manage you!
  • 7. Delivering the results
    • Successful project management is delivering a quality product that meets the customer’s requirements within
    • Time & Scope & Budget.
  • 8. Defining Project Management
    • Organizing and managing resources so the project is completed within defined scope, quality, time and cost constraints
    • The application of knowledge, skills, tools and techniques to project activities to meet project requirements
  • 9. Project planning crucial!
    • The primary purpose of planning is to establish a set of directions in enough detail to tell the project team exactly what must be done
    • The purpose of planning is to facilitate later accomplishment
    • Planning to enable communication to all stakeholders
    Chapter 5-1
  • 10. Project life
    • Initiation/Definition/Start-up
    • Planning
    • Execution
    • Closure
    It all starts with this! This is how it feels….. Theory says this:
  • 11. Project Life Cycle & PM tools Complex Environments Controlled Environments Prince2 PM Tools PM Tools LFA LFA Prince2
  • 12. Stage control in Prince2
  • 13. Assignment: Is it a Project?
    • Split in mixed groups of 5 persons
    • Study the pictures/video
      • Identify/Verify the project design characteristics, process, team, resources, implementation, management, results, etc)
    Name 5 reasons why you see a project? Name 5 reasons why you do not see a project? http://www.youtube.com/watch?v=4u2LjkRhrc4
  • 14. Learning Objectives
    • Defining project management
    • The skills of the project manager
    • Tools for project management
  • 15. What makes a project work?
    • A good, solid professional project manager
  • 16. What you need as Project Manager
    • Program area knowledge, standards, and regulations
    • Understanding the project environment
    • General management skills (budgeting, scheduling)
    • Communication skills
    • Interpersonal skills
  • 17.
    • Ensure strong, committed management support
    • Connect the business goals to the development project
    • Establish clearly defined directions
    • Be proactive
    • Listen and please stakeholders
    Be a Leader
  • 18.
    • Define your requirements in detail
    • Establish a speedy conflict resolution and escalation process
    • Make contingency plans
    • Plan a reasonable roll-out schedule
    Anticipate, plan and keep overview
  • 19.
    • Communicate objectives frequently
    • Recognize different perspectives
    • Check assumptions frequently
    Communicate
  • 20.
    • Identify all team members up front!
    • Get commitment!
    • Define roles and responsibilities
    • Establish communications protocols
    Manage the team RACI Grid
  • 21.
    • Identify stakeholders
    • Know their Perspective?
      • Problem
      • Solution
    • Manage expectations
    • Share success and broadcast achievements
    • Invite feedback
    Manage the Stakeholders
  • 22. Report!
    • Establish reporting requirements upfront
    • Include the good, the bad, and the ugly
    • Be brief but accurate
    • Management really does want to know!
  • 23. Be effective
    • Time management
    • Roles and responsibilities
    • Effective meetings
    • Intercultural competences
  • 24.
    • How do we perceive cultural differences?
    • Minimise Exaggerate
    • No Problem Terrible…..
    • Either minimisation or exaggeration both unhelpful: it is simply a risk for which measures can be designed to ensure success
    • Why focus on cultural differences?
    Intercultural and Multi-location teams
  • 25.
    • A good project team can be the key to a successful project!
  • 26. When Projects Succeeed
    • Sound project management processes
    • Project tied to the organization’s business goals
    • Senior management commitment
    • 4. Good change management
    • 5. Detailed requirements
  • 27. When Projects Succeed
    • 6. Realistic schedule
    • Good stakeholder relationships
    • 8. Empowered project manager
    • 9. Skilled and appropriate team members with defined roles and responsibilities
    • 10. Availability of funding
  • 28. Assignment: Is it a good Projectplan?
    • Split in mixed groups of 5 persons
    • Study the projectplan
    • Name 5 reasons why this is a good projectplan
    • Describe required skills of the project leader
    • Name a team with function and roles
  • 29. Alternatives to the waterfall: Agile/SCRUM
    • Not all projects can be planned from the start
    • (Too) many unknowns and assumptions
    • (Too) many interdependencies
  • 30. Transitioning to APM? Agile Project Management Traditional Project Management Focus on customer satisfaction and interaction Focus on plans and artifacts Response to change via adaptive action Change controlled via corrective action Progressive elaboration, rolling-wave planning Monumental up-front planning Customer prioritized, time-boxed delivery Manager negotiated, scope-based delivery Commitment management via feature breakdown structure Activity management via work breakdown structure Collaboration on self-disciplined and self-organizing teams Top-down control Minimal set of context-sensitive, generative practices Prescriptive, heavyweight methods Essential, value-focused metrics Non-value added controls
  • 31. The Agile Manager’s Role
    • Leading project teams in creating and responding to change through:
      • Small batches
      • Small, integrated teams
      • Small, continuous improvements
    • Light touch leadership: the work of energizing, empowering and enabling project teams to rapidly and reliably deliver customer value:
      • By engaging customers, and
      • Continuously learning and adapting to their changing needs and environments
      • Focus on value creation
  • 32. Alternatives to the waterfall: Agile/SCRUM in action
    • Often used in
    • product development
    • software development