Meeting Management/Planning. Today Go over basics of meeting management Introduce key elements of creating a plan.

Slides:



Advertisements
Similar presentations
Facilitated by Joanne Fraser RiverSystems
Advertisements

Team Communication What does it take?. Overview  Why it is important & necessary  Creating Team Communication  Characteristics of Open Communication.
Deliverable #8: Detailed Design - Overview due: Wednesday, 7 March All Deliverable materials are to be posted into Team Concert. Your to.
Effective Meetings.
Stephanie M. Glyptis April 5, 2014 Let’s Meet: The Essentials of Great Meetings.
09/27/2014 Artis Boyd, PMP 1. BUSINESS AND FUNCTIONAL REQUIREMENTS “PROCESS IMPROVEMENT” 09/27/2014 Artis Boyd, PMP.
Performance Assessment Process: The Employee’s Perspective May 2014.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Welcome to RAI, the future of collaborative Project Risk Management Overview of Project Risk and Issue Management RAI for the Project Manager RAI for the.
Project Perfect Pty Ltd Project Administrator Overview of Software.
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
Projmgmt-1/33 DePaul University Project Management I - Risk Management Instructor: David A. Lash.
SE is not like other projects. l The project is intangible. l There is no standardized solution process. l New projects may have little or no relationship.
CSCI 639 Topics in Software Engineering Assignment #4 Fall 2006.
Lean Six Sigma: Process Improvement Tools and Techniques Donna C. Summers © 2011 Pearson Higher Education, Upper Saddle River, NJ All Rights Reserved.
IS&T Project Management: Project Management 101 June, 2006.
Implementation of Project Governance at the Center Level
Meeting Skills.
Release & Deployment ITIL Version 3
Leaders Manage Meetings
Advanced Project Management Project Plan Templates
Project Manager’s Survival Guide PMI Westchester - Quality SIG Presentation June 11, 2013 By: Annmarie Gordon, PMP.
COLLABORATION MODULE #3 Planning Good Meetings An online module developed by Pivot Learning Partners for the West Contra Costa Unified School District.
S/W Project Management
Project Planning with IT Y/601/7321
COMPGZ07 Project Management Presentations Graham Collins, UCL
Teamwork and Problem Solving
COMP 208/214/215/216 Lecture 2 Teams and Meetings.
Software Testing Lifecycle Practice
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Software Project Management Introduction to Project Management.
Project Management Chapter 3. Objectives Become familiar with estimation. Be able to create a project workplan. Understand why project teams use timeboxing.
BSBPMG503A Manage Project Time Manage Project Time Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG503A.
Project Management : Techniques and Tools (60-499) Fall 2014 / Winter 2015.
1 This workshop is part of our commitment to periodically provide you with updated information about BPA’s contracting and project management processes.
Honor Respect Devotion to Duty Please be seated…. Only one person from a Division at the same table.
BSBPMG402A Apply Time Management Techniques Apply Time Management Techniques Unit Guide C ertificate IV in Project Management Qualification Code.
How to Run an Effective Meeting Goal – Get desired results – Use the time of all participants efficiently When face-to-face communication is required Sharing.
Welcome to Session 4 – Project Management Process Overview (continued) Instructor:Phyllis Sweeney Instructor: Phyllis Sweeney Project Management Certificate.
Service Transition & Planning Service Validation & Testing
1 Chapter 5 Project management. 2 Project management : Is Organizing, planning and scheduling software projects.
Assessment Callie Cothern and Heather Vaughn. A Change in the view of assistive technology assessment: From a one shot, separate event to an ongoing,
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Project Management Part 6 Project Control. Part 6 - Project Control2 Topic Outline: Project Control Project control steps Measuring and monitoring system.
Project Charters Module 3
BSBPMG402A Apply Time Management Techniques Apply Time Management Techniques Unit Guide C ertificate IV in Project Management Qualification Code.
INTRO TO USABILITY Lecture 12. What is Usability?  Usability addresses the relationship between tools and their users. In order for a tool to be effective,
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Modeling Tough Scheduling Problems with Software Alex S. Brown Mitsui Sumitomo Marine Management (USA), Inc.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Apply Quality Management Techniques Project Quality Processes Certificate IV in Project Management Qualification Code BSB41507 Unit Code BSBPMG404A.
BSBPMG404A Apply Quality Management Techniques Apply Quality Management Techniques Project Quality Processes C ertificate IV in Project Management
Chair & Minute Taking Training Isabel Costello, Student Voice Coordinator (Course Reps & Quality)
PLANNING YOUR APPROACH: THE MANAGEMENT COMPONENT OF CPS.
Operational and Postimplementation
Problem-Solving Meeting Foundations
CREATING GREAT STANDS: A STEP-BY-STEP GUIDE TO CREATING A TEAM’S MOST VALUABLE TOOL DFA Coaches DoLE Team.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
T Project Review Wellit I1 Iteration
Making Health and Safety Meetings Work If you had to identify, in one word, the reason why the human race has not achieved, and never will achieve, its.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
Running Effective Meetings. So what makes a meeting effective? They achieve the meeting's objective. They take up a minimum amount of time. They leave.
BSBPMG503A Manage Project Time Manage Project Time Project Time Processes Part 2 Diploma of Project Management Qualification Code BSB51507 Unit Code.
School-Wide Positive Behavior Coaches Meeting Year 1 Day Donna.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Conducting Effective Meetings
Sweet Adelines International
Dr. Rob Hasker SE 3800 Note 9 Reviews.
Presentation transcript:

Meeting Management/Planning

Today Go over basics of meeting management Introduce key elements of creating a plan

Why Have Meetings? What are the reasons for having meetings?

Issues What common issues are experienced? – Wastes time Expensive (duration * # of attendees) – Ill focused Not clear what the purpose is Not clear what the desired outcome is – Goes off track Is sidetracked by discussions that don’t support objectives – No follow up Not clear what happens after the meeting People lose track of decisions/issues from meeting

Results of Poor Meeting Management Personal issues can arise Team can become demoralized Schedule delays

Effective Meetings First why are you meeting? Meetings need to be planned Ensure appropriate participation Make sure the meeting stays focused Record decisions, issues, and actions Make sure all understand the results Have some effective mechanism for following up on the results of the meeting

Why Are You Meeting? What is the purpose of the meeting? Do you really need a meeting? All meetings should have a clear objective (should be clear to all attendees) e.g. – Status – Planning – Review (e.g. postmortem) – Working meeting of some type Should have specific (reasonable) objectives

Planning a Meeting The meeting should be structured and conducted to support the goal To do this you should “plan” the meeting Everyone should know and understand the “plan” People should have a chance to comment on the plan prior to the meeting Pre work should be explicitly identified And should be done prior to the meeting Key participation should be confirmed – Doesn’t make sense to meet if you don’t have the people needed to accomplish goals

Keep Meeting Focused The meeting should stay on topic and be efficient You should have some means for making sure the discussion doesn’t go off track – E.g. if you have a status meeting it is often easy to start talking about solutions for identified issues Helpful to have someone responsible for making sure you stay on topic – Could also have someone keep track of the time May need to time box discussions

What Did We Talk About? It’s great if you do some great thinking but … – If no one remembers what was decided what good is it? Need to have some way to capture the results of the meeting – Typical output are: Action items Issues/Risks Decisions It is helpful if there is someone who is responsible for capturing these outputs

Did We Accomplish Our Goal? It may be useful to review outputs of the meeting at the end – Helps to ensure all understand the decisions consistently It can also be helpful to reflect on the effectiveness of the meeting – Many ways to do this – Can help ensure that the meeting process supports objectives

So Now What? What happens after the meeting? Is it clear? How are the decisions/risks/actions communicated? How are the results tracked? Helps to have (at a minimum) minutes published

Realization Varies How you incorporate meetings into your process will vary widely Should have some means for making sure the meeting is effective Will require that you have integrated processes – This is true across the board

Planning What is a plan? Why do you need one … or do you need one? What does a plan consist of?

Past (Common) Issues It isn’t clear what is being planned – The plan doesn’t reflect the needs of the project – Often we’ll see “semester” plans Plan isn’t created because teams don’t know everything yet Multiple plans – We often see “Macro” plans and “iteration” plans Plans are static – Teams create a plan early and don’t update – Initial plan isn’t accurate or detailed Plan isn’t adequately communicated – The plan is only used by the project manager Tasks are commonly understood Relationships among tasks aren’t clear or commonly understood

Creating the Plan What is the plan for? What are the tasks for each deliverable? How are the tasks related? How much effort is required for tasks? What will be done when? How will the plan be recorded and tracked? How and when will the plan be updated?

What Is the Plan For? What are the results of the activity being planned? – What are the goals of the project? What are the deliverables? – Be sure to consider all deliverables – Remember you have three main “recipients” the client, the Academic program, and yourselves As knowledge of these deliverables are refined the plan will likely need to be refined The resulting plan should support the goals

Tasks? What Tasks? You (as a team) will need to do some finite set of activities to realize the deliverables What are these activities? – They may come from risks and process as well as deliverables You will not be able to identify all of them upfront – They may also be high level initially It (somehow) needs to be clear what these tasks are – At least when they are going to be estimated, assigned, and performed How much effort is needed to complete the task? – Needed for scheduling – Needed for work allocation

Tasks are Related Tasks are related – Tasks often depend on each other in some way Tasks may constrain each other – Decisions made with one task may constrain the available options for another task You must therefore understand these relationships – Impacts how you are going to stage the work – Impacts the interactions among people working on related tasks – Impacts how re-planning happens

Scheduling Tasks You need to create a schedule for the tasks Your lifecycle process will impact this You need to consider: – Available resources – Fixed deliverable dates (e.g. MPP) – Task dependencies – Vacations, holidays, other non-working time

Recording and Tracking In order for the plan to be effective it needs to be communicated – An excel spreadsheet on the PM computer probably isn’t the best approach You need to have some mechanism for recording, communicating and tracking the plan – Some combination of tool and process

Plans Are Dynamic Things change Your initial plan will be inaccurate/inadequate When will you update the plan? – At what point might you have enough information to refine previous assumptions? How do you know if your plan is working? Do you have some means for updating your planning process?

Resources Mentors In house experts – Mel Rosso-llopart – Eduardo Miranda Courses – Managing Software Development – Estimation course – Team Software Process And of course – Online and print resources