SlideShare a Scribd company logo
1 of 2
Agenda / Schedule
Copyright John E. Derrick
2010 (512) 413-5010
Week 1
Meetings will be conducted across the employee ranks to create a detailed understanding of
the business model, technology offerings, the team and begin to form a quantitative analysis
of the opportunities and risks.
Day 1 – Goal: Introductions and Assurances
 Meet with the executive team as a group and briefly as individuals to answer any fast
questions, provide assurance to the team, and request detail information for their
particular function for later in the week.
 Meet the employees as a group to introduce and provide assurances and begin to
meet with key employees to get insight into the operational company, not just the
management team, answer questions, and provide assurance.
Day 2 – Goal: Marketing and Sales
 VP/Sales and VP/Biz Dev provide marketing information, plan, and supporting
information
 Detail customer funnel and definitions of stages
 Detail use cases and customer value propositions
 Competitive analysis and differentiation
 Customer product requests and the process used to validate, prioritize, and current
status of requests and features
Day 3 – Goal: Product Offering and Roadmap
 Detailed description of the defined product – what is included, what is coming on
planned releases, and what has been rejected or excluded from the product
 Description of value attributed to portions of the technology
 Installation and maintenance requirements
 Approximate schedules for products in the roadmap
Day 4 – Goal: Technology / Development Status Walkthrough
 Hardware or system design content
 Software design content
 Development process – how is it defined, developed, validated, and documented
 Performance / Architectural modeling methodology
 Detailed review of current status against upcoming releases, risk areas, and mitigation
plans
 Stress testing procedures and resources – is there enough time and systems available
to test product internally or is there too much reliance on customers
Day 5 – Goal: Staffing, Finance, and Budget
 Current organization and adjustments in the plan
 Review of finance operations and planning process
 Review of the budget and forecast
Agenda / Schedule
Copyright John E. Derrick
2010 (512) 413-5010
Week 2
An initial assessment of the risks and problem areas will be validated with the team and
reviewed with the board. These will include proposed plans to reduce risks and compensate
for the deficiencies – typically it can include adjusting responsibilities, clearly specifying and
assigning actions to be performed, resolving deferred issues, and correcting staffing issues.
Changes would be planned in a way to improve, not negatively impact, upcoming release
schedule and quality.
It is also vital that regular status and communication is established between the different
leaders and provide an opportunity to alert each other and resolve any challenges that need to
be addressed. This needs to be started by the second week, but any existing structure /
methods need to be observed the first week to determine if any change is warranted.
Day 6 & 7 – Goal: Communicate next steps
 Based on the meetings and information gathered the previous week, some conclusions
will be accessible – these would be shared with the board, executive team, and
applicable staff
 Most of the next steps will have ownership and actions required by the staff with the
immediate access and background so progress should be timely
 The team will drive the required changes to the company and operational plan. To
enable this, the existing team (with modification if required) will expand and
implement the clarification and direction of the key issues or decisions.
Day 8 & 9 – Goal: Review and changes or adjustments with owners
Meet with individuals and ensure that required actions / adjustments are understood
Day 10 – Goal: Communicate progress to the team
 Meet with employees and provide information on what is being done, why it was
necessary, what the goal and expectations are, and answer questions
 Depending on the scenario this would be the time to inform that the company is
looking to add certain missing skills, is making changes in leadership if required, and
any changes or expected changes in products or market focus.
Week 3-8
During this period, the direction (change) will be set in motion. The most important factors
are visible progress, focus and coordinated activity by the team, and continued open
communication.
Week 9-12
Success with the completion of relevant changes or redirection, renewed customer traction,
and team operation will have been demonstrated during this time.

More Related Content

What's hot

It Project Management
It Project ManagementIt Project Management
It Project Management
TJ Rains
 
Implementation and Deployment - Best Practices for Managing Change
Implementation and Deployment - Best Practices for Managing ChangeImplementation and Deployment - Best Practices for Managing Change
Implementation and Deployment - Best Practices for Managing Change
Peter Quintana
 
Cmgt 410 week 4 individual assignment project controls
Cmgt 410 week 4 individual assignment project controlsCmgt 410 week 4 individual assignment project controls
Cmgt 410 week 4 individual assignment project controls
7Fase1
 
Fetac level 6 certificate in project managment
Fetac level 6 certificate in project managmentFetac level 6 certificate in project managment
Fetac level 6 certificate in project managment
EdenTraining
 

What's hot (14)

It Project Management
It Project ManagementIt Project Management
It Project Management
 
Free PMP Sample Q & A
Free PMP Sample Q & AFree PMP Sample Q & A
Free PMP Sample Q & A
 
Free PMP Sample Q & A
Free PMP Sample Q & AFree PMP Sample Q & A
Free PMP Sample Q & A
 
Free PMP Sample Q & A
Free PMP Sample Q & AFree PMP Sample Q & A
Free PMP Sample Q & A
 
Operational definition of of Monitoring and Evaluation Terms
Operational definition of of Monitoring and Evaluation TermsOperational definition of of Monitoring and Evaluation Terms
Operational definition of of Monitoring and Evaluation Terms
 
HOW TO CARRY OUT MONITORING AND EVALUATION OF PROJECTS
HOW TO CARRY OUT MONITORING AND EVALUATION OF PROJECTSHOW TO CARRY OUT MONITORING AND EVALUATION OF PROJECTS
HOW TO CARRY OUT MONITORING AND EVALUATION OF PROJECTS
 
Free PMP Sample Q & A
Free PMP Sample Q & AFree PMP Sample Q & A
Free PMP Sample Q & A
 
Implementation and Deployment - Best Practices for Managing Change
Implementation and Deployment - Best Practices for Managing ChangeImplementation and Deployment - Best Practices for Managing Change
Implementation and Deployment - Best Practices for Managing Change
 
Free PMP Sample Q & A
Free PMP Sample Q & AFree PMP Sample Q & A
Free PMP Sample Q & A
 
Project plan overview
Project plan overviewProject plan overview
Project plan overview
 
Pfizer experience
Pfizer experiencePfizer experience
Pfizer experience
 
Pfizer experience
Pfizer experiencePfizer experience
Pfizer experience
 
Cmgt 410 week 4 individual assignment project controls
Cmgt 410 week 4 individual assignment project controlsCmgt 410 week 4 individual assignment project controls
Cmgt 410 week 4 individual assignment project controls
 
Fetac level 6 certificate in project managment
Fetac level 6 certificate in project managmentFetac level 6 certificate in project managment
Fetac level 6 certificate in project managment
 

Similar to Agenda

Project iii.collaborative.group1.part i_understanding_expectations_the_who_wh...
Project iii.collaborative.group1.part i_understanding_expectations_the_who_wh...Project iii.collaborative.group1.part i_understanding_expectations_the_who_wh...
Project iii.collaborative.group1.part i_understanding_expectations_the_who_wh...
Maicol Suntasig
 
Optimize Project Intake Approval and Prioritization
Optimize Project Intake Approval and PrioritizationOptimize Project Intake Approval and Prioritization
Optimize Project Intake Approval and Prioritization
Info-Tech Research Group
 
Various National Agencies Directly Involved in the Issuance of Public Fiscal
Various National Agencies Directly Involved in the Issuance of Public FiscalVarious National Agencies Directly Involved in the Issuance of Public Fiscal
Various National Agencies Directly Involved in the Issuance of Public Fiscal
MarieTaylaran1
 
Current Job Description
Current Job DescriptionCurrent Job Description
Current Job Description
Brian Miller
 
How to get started - managing a project
How to get started - managing a projectHow to get started - managing a project
How to get started - managing a project
Maven
 

Similar to Agenda (20)

Project iii.collaborative.group1.part i_understanding_expectations_the_who_wh...
Project iii.collaborative.group1.part i_understanding_expectations_the_who_wh...Project iii.collaborative.group1.part i_understanding_expectations_the_who_wh...
Project iii.collaborative.group1.part i_understanding_expectations_the_who_wh...
 
High Level Solution Plan - Nationwide
High Level Solution Plan - NationwideHigh Level Solution Plan - Nationwide
High Level Solution Plan - Nationwide
 
Optimize Project Intake Approval and Prioritization
Optimize Project Intake Approval and PrioritizationOptimize Project Intake Approval and Prioritization
Optimize Project Intake Approval and Prioritization
 
Various National Agencies Directly Involved in the Issuance of Public Fiscal
Various National Agencies Directly Involved in the Issuance of Public FiscalVarious National Agencies Directly Involved in the Issuance of Public Fiscal
Various National Agencies Directly Involved in the Issuance of Public Fiscal
 
4 integration
4 integration4 integration
4 integration
 
The_8_Successful_Steps_for_ERP_Implementation.pptx
The_8_Successful_Steps_for_ERP_Implementation.pptxThe_8_Successful_Steps_for_ERP_Implementation.pptx
The_8_Successful_Steps_for_ERP_Implementation.pptx
 
Current Job Description
Current Job DescriptionCurrent Job Description
Current Job Description
 
1B project MS V2
1B project MS V21B project MS V2
1B project MS V2
 
1st Discovery Delivery Model
1st Discovery Delivery Model1st Discovery Delivery Model
1st Discovery Delivery Model
 
Project management processes Groups
Project management processes GroupsProject management processes Groups
Project management processes Groups
 
Project Management How To
Project Management How ToProject Management How To
Project Management How To
 
Assignment .pdf
Assignment .pdfAssignment .pdf
Assignment .pdf
 
Lean/Agile Depth Assessment Checklist A3
Lean/Agile Depth Assessment Checklist A3Lean/Agile Depth Assessment Checklist A3
Lean/Agile Depth Assessment Checklist A3
 
How to get started - managing a project
How to get started - managing a projectHow to get started - managing a project
How to get started - managing a project
 
kanbarasu
kanbarasukanbarasu
kanbarasu
 
Tc11 ad14
Tc11 ad14Tc11 ad14
Tc11 ad14
 
Spm unit 1
Spm unit 1Spm unit 1
Spm unit 1
 
Introduction to Project Management.pptx
Introduction to Project Management.pptxIntroduction to Project Management.pptx
Introduction to Project Management.pptx
 
PARAMED COLLEGE preventing and eliminating of muda.pptx
PARAMED COLLEGE preventing and eliminating of muda.pptxPARAMED COLLEGE preventing and eliminating of muda.pptx
PARAMED COLLEGE preventing and eliminating of muda.pptx
 
Project Management
Project ManagementProject Management
Project Management
 

Agenda

  • 1. Agenda / Schedule Copyright John E. Derrick 2010 (512) 413-5010 Week 1 Meetings will be conducted across the employee ranks to create a detailed understanding of the business model, technology offerings, the team and begin to form a quantitative analysis of the opportunities and risks. Day 1 – Goal: Introductions and Assurances  Meet with the executive team as a group and briefly as individuals to answer any fast questions, provide assurance to the team, and request detail information for their particular function for later in the week.  Meet the employees as a group to introduce and provide assurances and begin to meet with key employees to get insight into the operational company, not just the management team, answer questions, and provide assurance. Day 2 – Goal: Marketing and Sales  VP/Sales and VP/Biz Dev provide marketing information, plan, and supporting information  Detail customer funnel and definitions of stages  Detail use cases and customer value propositions  Competitive analysis and differentiation  Customer product requests and the process used to validate, prioritize, and current status of requests and features Day 3 – Goal: Product Offering and Roadmap  Detailed description of the defined product – what is included, what is coming on planned releases, and what has been rejected or excluded from the product  Description of value attributed to portions of the technology  Installation and maintenance requirements  Approximate schedules for products in the roadmap Day 4 – Goal: Technology / Development Status Walkthrough  Hardware or system design content  Software design content  Development process – how is it defined, developed, validated, and documented  Performance / Architectural modeling methodology  Detailed review of current status against upcoming releases, risk areas, and mitigation plans  Stress testing procedures and resources – is there enough time and systems available to test product internally or is there too much reliance on customers Day 5 – Goal: Staffing, Finance, and Budget  Current organization and adjustments in the plan  Review of finance operations and planning process  Review of the budget and forecast
  • 2. Agenda / Schedule Copyright John E. Derrick 2010 (512) 413-5010 Week 2 An initial assessment of the risks and problem areas will be validated with the team and reviewed with the board. These will include proposed plans to reduce risks and compensate for the deficiencies – typically it can include adjusting responsibilities, clearly specifying and assigning actions to be performed, resolving deferred issues, and correcting staffing issues. Changes would be planned in a way to improve, not negatively impact, upcoming release schedule and quality. It is also vital that regular status and communication is established between the different leaders and provide an opportunity to alert each other and resolve any challenges that need to be addressed. This needs to be started by the second week, but any existing structure / methods need to be observed the first week to determine if any change is warranted. Day 6 & 7 – Goal: Communicate next steps  Based on the meetings and information gathered the previous week, some conclusions will be accessible – these would be shared with the board, executive team, and applicable staff  Most of the next steps will have ownership and actions required by the staff with the immediate access and background so progress should be timely  The team will drive the required changes to the company and operational plan. To enable this, the existing team (with modification if required) will expand and implement the clarification and direction of the key issues or decisions. Day 8 & 9 – Goal: Review and changes or adjustments with owners Meet with individuals and ensure that required actions / adjustments are understood Day 10 – Goal: Communicate progress to the team  Meet with employees and provide information on what is being done, why it was necessary, what the goal and expectations are, and answer questions  Depending on the scenario this would be the time to inform that the company is looking to add certain missing skills, is making changes in leadership if required, and any changes or expected changes in products or market focus. Week 3-8 During this period, the direction (change) will be set in motion. The most important factors are visible progress, focus and coordinated activity by the team, and continued open communication. Week 9-12 Success with the completion of relevant changes or redirection, renewed customer traction, and team operation will have been demonstrated during this time.