• Save
Pm Communication Reporting
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Pm Communication Reporting

on

  • 923 views

 

Statistics

Views

Total Views
923
Views on SlideShare
923
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

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

Pm Communication Reporting Presentation Transcript

  • 1. Communication/Reporting PM
  • 2. Why is it important?
  • 3. PM Reporting/Communications Software Development PM Upper management Reports, presentations, meetings, Q&A Team Meetings, Action Items, CC, Minutes, Q&A Clients Requirements, visits, demos, Q&A, development updates, tests
  • 4. Communication/Reporting
    • Agenda
      • (IceBreakers, Attendance?, Open Section)
    • Change Control List
    • Action Items List
      • (who, when, actual completion)
    • Meeting summaries
      • (weekly, bi-weekly, monthly)
  • 5. The Agenda Bell Modest decision items Announcements Minutes Moderate decision items Most difficult item Discussion items Small, trivial item Source : Tropman, 1985 TIME SPENT
  • 6. Icebreakers
    • Ask each individual to post 4 statements about themselves to a discussion forum: one of the statements should be false while 3 should be true. Have the group member guess which of the items are lies.
    • Ask participants to define a list of 8-10 things they would like to know about other people in the group. Pair the team up with each other and conduct interviews to learn the answers to those questions.
    • Give each group member a piece of a puzzle and have them write a unique skill they bring to the group. Have the group put the puzzle together to demonstrate how everyone contributes to the overall group success.
  • 7. Effective Presentations
    • 1. Strategy for a specific audience and occasion
      • identify your general and specific purposes
      • tailor your message to your specific audience
        • understand needs, desires, knowledge level and attitude towards your topic
        • make sure your approach is audience centered
        • if the audience is hostile present both sides of the issue
      • meet the demands of the situation
    • 2. Clear structure , translating strategy into a specific content
      • catch the attention as you begin, provide them with a reason for listening
      • give them an outline of the message so they can follow along
      • transitions/signposts to signal your progress
      • conclude on a high note
  • 8. Effective Presentations (cont)
    • 3. Support ideas with examples, illustrations and other material adapted to your audience
    • 4. Create a presentation style
      • prepare your notes
      • practice using your visual aids
      • convey controlled enthusiasm for your subject
      • use delivery to enhance your message (eye contact, body movement)
    • 5. Supplement your presentation with confident, formed responses to questions.
      • prepare to handle questions
      • maintain control of the situation
  • 9. Software Reviews Developer. A reader, TL. Development team representative. Software PM or project representative. Presenter Lead auditor. Facilitator or developer. Trained facilitator, technical/QA leadership. TL / Lead engineer. Responsible manager or Senior Software PM. Group leadership Auditors, management and technical personnel. Technical leadership and software team mix. Software team mix, Software QA. Technical leadership and development team mix. Management, TL, software team mix. Group attendance Management, Software PM, development team. Team agrees on changes to be made by the developer. Review team request changes and defects removals. Review team requests management or TL to act on recommendations. Made at the meetings; online pooling/email, or as a result of recommendations. Decision-making Independently evaluate compliance with objective standards and regulations. Find errors, code readings, conformance to specifications. Find errors; verify resolution and product quality. Conformance to specifications, development issues. Tracking / milestones, issues, resources, action items. Objective Audit Walk-through Inspection Technical Review Management Review Characteristic
  • 10. Management Reviews - IEEE Std.1028
    • Roles
      • Decision Maker: Determines if the review objectives have been met.
      • Review Leader: Plans and conducts the review, issues the Management Review Report .
      • Minutes Taker: Documents errors, action items, decisions, and recommendations made during the review examination.
      • Management Staff: Participate in the review.
      • Technical Staff: Provide information for the review.
      • Customer/user Representative: Optionally invited by the reviewer leader; provides information for the review.
    • Management review report
      • Software project being reviewed
      • The review team members
      • Management review objectives
      • Software product reviewed
      • Specific inputs to the review
      • Action item status (open, closed), ownership and target date (if open) or completion date (if closed)
      • A list of errors/change control items/issues identified by the review team to be addressed
  • 11. Management Review Chart Software Product Statement of Objectives Other Inputs Management Review Report Planning Overview of Review Procedures Overview Meeting Preparations Overview of Review Procedures Review Meeting Review software product and record errors Rework/Follow-up Management Follow-up Staff Creates Management Preparation
    • Optional, requested by the review leader
    • Conducted during the beginning of the (first) review meeting
    • Specified prior to the review, via a Software Project Management Plan or other plan
    • If the purpose is not specified by the plan; the statement of objectives should be created by management
  • 12. Technical Reviews - IEEE Std.1028
    • Roles
      • Decision Maker: Determines if the review objectives have been met.
      • Review Leader: Plans and conducts the review, issues the Technical Review Report .
      • Minutes Taker: Documents errors, action items, decisions, and recommendations made during the review examination.
      • Management Staff: Participate in the review for the purpose of identifying issues that require management resolution.
      • Technical Staff: Participate in the review and evaluate the software product.
    • Technical review report
      • Software project being reviewed
      • The review team members
      • Software product reviewed
      • Specific inputs to the review
      • Review objectives and whether they were met
      • List of resloved and unresloved software, hardware, specification errors
      • List of management issues
      • Recommendations made by the review team of how to dispose of unresloved issues and errors
      • Whether the software product meets the applicable regulations, standards, guidelines, plans and procedures without deviations
  • 13. Technical Review Chart Software Product Statement of Objectives Other Inputs Technical Review Report Planning Overview of Review Procedures Overview Meeting Preparation Overview of Review Procedures Review Meeting(s) Review software product and record errors Rework/Follow-up Management Follow-up Development Team Management Preparation Overview of Review Procedures Overview of software product
  • 14. Inspection Reviews - IEEE Std.1028
    • Roles
      • Inspection Leader: Plans and conducts the review, issues the Inspection Report .
      • Recorder : Document errors, action items, decisions, and recommendations made during the review examination.
      • Reader: Leads the inspection through the software product, paraphrasing several lines, functions, paragraphs, or sections.
      • Developer: Prepares the software product for the inspection, provides information on the software product during the inspection, and reworks the software product as needed following the inspection meeting.
      • Tester/QA: Identifies and describes errors in the software product.
      • ( Note : Holders of management position over the inspection team are excluded from the inspection reviews.)
    • Error ranking
      • Major - would result in failure of the software product.
      • Minor - deviate from relevant specifications but will not cause failure of the software product or an observable departure in performance.
    • Inspection report
      • The software project being inspected.
      • The inspection team members.
      • The inspection meeting duration.
      • Software product inspected.
      • The size of the material inspected (number of programming lines).
      • Specific inputs to the inspection.
      • Inspection objectives and whether they were met.
      • The error list, containing: Defect ID, Description, Platform type, Date, Severity, Phase creation/detection, Date correction, Status.
      • Estimation of the rework effort and rework completion date.
  • 15. Inspection Review Chart Software Product Statement of Objectives Other Inputs Management Review Report Planning Overview Session Preparations Review general items Examination Review software product and record errors Management Follow-up Management Preparation Introduce meeting Establish preparedness Review error list Decision making Rework/Follow-up Software Developer More preparation required Re-inspect Accept
  • 16. Walk-Through Reports - IEEE Std.1028
    • Roles
      • Walk-Through Leader: Plans and conducts the walk-through, defines and checks the objectives of the walk-through, and issues the Walk-Through Report .
      • Recorder: Documents decisions and identified actions made during the walk-through meeting.
      • Developer: Presents the software product in the walk-through.
      • Team Member: Participates in the walk-through.
      • ( Note : Holders of management position over the walk-through team are excluded from the walk-through.)
    • Exit criteria for Walk-Through
      • The examined part of the software product has been completed.
      • Recommendations and required actions have been recorded.
      • The walk-through output (report) has been completed.
    • Walk-Through Report
      • Walk-through team members.
      • Software product being examined.
      • Statement of objectives to be accomplished and status.
      • List of recommendations for every modification/error.
      • Action item list (open, closed), ownership and target date (if open) or completion date (if closed).
      • Any recommendations made by the walk-through team.
      • Any proposals made by the walk-through team for follow-up walk-throughs.
  • 17. Walk-Through Chart Software Product Statement of Objectives Other Inputs Walk through Report Planning Examination Presentation of the software product; Rework/Follow-up Management Follow-up Software Developer Management Preparation Preparations General Discussion Overview
    • May function as a walk-through leader and/or recorder.
    • Walk-throughs are conducted by technical staff and provide information to technical staff.
  • 18. Audits Chart Software Product Purpose and Scope Other Inputs Audit Report Planning Examination Reporting Management Follow-up Audited entity Management Preparation Preparations Closing Meeting Evidence collection Opening Meeting
  • 19. Technical Review, Inspection, Walk-Through Installation Configuration Audit Audit Source Code and Source Code Documentation Evaluation Technical Review, Inspection, Walk-Through Software Design Evaluation Technical Review, Inspection, Walk-Through Software Requirements Evaluation Technical Review Concept Documentation Evaluation Management Review, Technical Review Contract Verification Technical Review System Requirements Review Management Review Management Review of V&V Audit QA Audit Technical Review, Inspection, Walk-Through User Documentation Review Management Review, Technical Review Post-mortem Review Management Review Software Configuration Management Plan Review Management Review Managerial Reviews Audit In-Process Audits Audit Physical Audit Audit Functional Audit Management Review Software V&V Plan Review Technical Review Critical Design Review Technical Review Preliminary Design Review Technical Review Software Requirements Review Corresponding IEEE Std 1028 Review Type Review name