The After Action Review (AAR) is a post-shift team discussion that incorporates technical and human factors lessons learned from an event or day's activities. It aims to determine the roots of performance successes and failures to develop strategies for improvement. The AAR assists in establishing a common crew perception of events, provides practice in communication and conflict resolution, and reinforces group norms. An effective AAR addresses both good and poor performance, is conducted privately after the event while still fresh, and focuses discussion on the most important lessons learned rather than unnecessary details.
The document discusses decision making in projects and how to make better decisions. It introduces Crew Resource Management (CRM) and Team Resource Integration Management (TRIM) as techniques. TRIM involves talking with the team, respecting each other, initiating action, and monitoring results. The document provides a checklist for project teams to use when making decisions, considering what needs to be decided, options, and involvement of the project manager and team.
This document discusses lessons learned from managing an IT project that had to serve both Agency and Center needs. The project aimed to consolidate multiple Active Directory forests into a single forest across 18 NASA Centers. [1] Meeting both sets of needs can seem impossible, as Centers find Agency initiatives difficult to implement and Agencies prioritize external requirements. [2] The project manager found success by having open communication, compromising to find common ground, and problem-solving issues actively as they arose. [3] With an emphasis on understanding all perspectives and frequent discussions, the project ultimately met requirements for both Agencies and Centers.
The manager of a global IT support team faced several challenges: [1] ensuring business continuity across time zones, [2] maintaining a shared knowledge base to resolve issues quickly, and [3] building team cohesion across geographic distances. To address these, the manager standardized communication tools and processes, increased opportunities for in-person interaction, and balanced remote and on-site work. This improved information sharing and strengthened relationships within the virtual team.
The document discusses a Technical Excellence Program (STEP) run by the National Aeronautics and Space Administration's (NASA) Safety and Mission Assurance (SMA) organization. STEP aims to improve project success through technical excellence by developing curriculum for SMA personnel. The agenda outlines a presentation on STEP including its development, rollout, and future plans to expand it to other training needs. It also includes an overview of the System Safety discipline and how it interacts with programs/projects to reduce risk.
The document provides information about an audio webinar on decision making during disasters and emergencies, including:
- The audio dial-in number, access code, and note that slides are available on the Everbridge blog.
- It discusses how human factors errors can negatively impact decision making during crises due to diminished cognitive capacities under stress.
- The webinar will cover research on decision making challenges during disasters and how to anticipate and mitigate barriers to quality decisions.
This document provides an overview of the Levin-Ward Competency Model for program management. It defines complexity and discusses key concepts related to complexity such as nonlinear dynamics and self-organization. It then outlines the basic structure of the competency model, including its purpose to identify important competencies. It describes the six performance competencies and eight personal competencies that make up the model. Examples are given of elements, performance criteria, and types of evidence for both performance and personal competencies. The document concludes by discussing how the model can be used to assess competency at the organizational, program manager, and prospective program manager levels and provides a five step process for implementing the model.
This document discusses piloting innovative idea capture and management tools at NASA Langley Research Center. It outlines lessons learned from piloting these tools, including that participation is critical to success but was limited, and credibility of the process is also important. A specific pilot involved launching topics on the Langley Creativity and Innovation Fund and Center Innovation Fund to solicit ideas from October to November 2010 and then assessing results through January 2011. The goal was to learn from initial pilots to improve innovation processes and tools.
Through strategic planning workshops, Dr. Tramel helped the NASA Metal Engineering Division develop a strategic plan from the bottom up. She engaged technicians, engineers, and managers to identify their organization's vision, mission, values, goals, and action steps. By applying servant leadership principles and an inclusive process, the workshops addressed the needs of employees experiencing uncertainty from changes at NASA. The bottom-up approach built ownership of the strategic plan.
The document discusses decision making in projects and how to make better decisions. It introduces Crew Resource Management (CRM) and Team Resource Integration Management (TRIM) as techniques. TRIM involves talking with the team, respecting each other, initiating action, and monitoring results. The document provides a checklist for project teams to use when making decisions, considering what needs to be decided, options, and involvement of the project manager and team.
This document discusses lessons learned from managing an IT project that had to serve both Agency and Center needs. The project aimed to consolidate multiple Active Directory forests into a single forest across 18 NASA Centers. [1] Meeting both sets of needs can seem impossible, as Centers find Agency initiatives difficult to implement and Agencies prioritize external requirements. [2] The project manager found success by having open communication, compromising to find common ground, and problem-solving issues actively as they arose. [3] With an emphasis on understanding all perspectives and frequent discussions, the project ultimately met requirements for both Agencies and Centers.
The manager of a global IT support team faced several challenges: [1] ensuring business continuity across time zones, [2] maintaining a shared knowledge base to resolve issues quickly, and [3] building team cohesion across geographic distances. To address these, the manager standardized communication tools and processes, increased opportunities for in-person interaction, and balanced remote and on-site work. This improved information sharing and strengthened relationships within the virtual team.
The document discusses a Technical Excellence Program (STEP) run by the National Aeronautics and Space Administration's (NASA) Safety and Mission Assurance (SMA) organization. STEP aims to improve project success through technical excellence by developing curriculum for SMA personnel. The agenda outlines a presentation on STEP including its development, rollout, and future plans to expand it to other training needs. It also includes an overview of the System Safety discipline and how it interacts with programs/projects to reduce risk.
The document provides information about an audio webinar on decision making during disasters and emergencies, including:
- The audio dial-in number, access code, and note that slides are available on the Everbridge blog.
- It discusses how human factors errors can negatively impact decision making during crises due to diminished cognitive capacities under stress.
- The webinar will cover research on decision making challenges during disasters and how to anticipate and mitigate barriers to quality decisions.
This document provides an overview of the Levin-Ward Competency Model for program management. It defines complexity and discusses key concepts related to complexity such as nonlinear dynamics and self-organization. It then outlines the basic structure of the competency model, including its purpose to identify important competencies. It describes the six performance competencies and eight personal competencies that make up the model. Examples are given of elements, performance criteria, and types of evidence for both performance and personal competencies. The document concludes by discussing how the model can be used to assess competency at the organizational, program manager, and prospective program manager levels and provides a five step process for implementing the model.
This document discusses piloting innovative idea capture and management tools at NASA Langley Research Center. It outlines lessons learned from piloting these tools, including that participation is critical to success but was limited, and credibility of the process is also important. A specific pilot involved launching topics on the Langley Creativity and Innovation Fund and Center Innovation Fund to solicit ideas from October to November 2010 and then assessing results through January 2011. The goal was to learn from initial pilots to improve innovation processes and tools.
Through strategic planning workshops, Dr. Tramel helped the NASA Metal Engineering Division develop a strategic plan from the bottom up. She engaged technicians, engineers, and managers to identify their organization's vision, mission, values, goals, and action steps. By applying servant leadership principles and an inclusive process, the workshops addressed the needs of employees experiencing uncertainty from changes at NASA. The bottom-up approach built ownership of the strategic plan.
Enterey Life Sciences Consulting PDA So. Cal PAI Presentation3rjohnston2268
Prep and execution for a PAI inspection, we typically organize our preparation activity into four main areas:
Plan, Prepare, Execution, and Response & Maintenance.
This document provides an overview of critical thinking, situation awareness, and decision making. It discusses threat and error management and how critical thinking, situation awareness, and decision making are essential processes in TEM. The document covers topics like gathering data, understanding information, planning ahead, assessing risks, and making choices to control thinking and improve safety. It emphasizes controlling biases, seeking multiple perspectives, and continuously learning to enhance expertise.
Monitoring at scale - Intuitive dashboard designLorenzo Alberton
At a certain scale, millions of events happen every second, and all of them are important to evaluate the health of the system. If not handled correctly, such a volume of information can overwhelm both the infrastructure that needs to support them, and people who have to make a sense out of thousands of signals and make decisions upon them, fast. By understanding how our rational mind works, how people process information, we can present data so it's more evident and intuitive. This talk will explain how to collect useful metrics, and to create the perfect monitoring dashboard to organise and display them, letting our intuition operate automatically and quickly, and saving attention and mental effort to activities that demand it.
This document discusses crisis management solutions for project management. It begins with definitions of crisis management and conflict resolution, noting that the latter involves finding root causes of gaps that create conflicts. Common root causes are flaws in planning, priorities, resource management, financial control, emphasis on technical over management aspects, personalities, cultures, communication and understanding of management systems. Solutions proposed include improving planning, defining priorities, comprehensive resource scheduling, financial training, management training, workshops to facilitate relationships, and communication planning. Mitigating measures include understanding personalities, encouraging open communication, preparing for cultural differences, and culture awareness training.
Chet Thomas is the planning manager at Norris Company, a printing plant. He is experiencing problems with stress and poor time management. His days are chaotic with many urgent but unimportant tasks taking priority over important strategic work. This is negatively impacting his work and personal life. Some potential solutions discussed are prioritizing tasks, delegating more responsibilities, and finding a better work-life balance.
Do you and your colleagues have to deliver a project? Would you find it useful to use a researched approach to identify potential issues and help avoid them?
One which involves the whole project team in an interesting and participative way? “Prevaluation” does that. This actual client case study reveals all ~ Read on….
1. The document provides 10 strategies for better time management: know how you spend your time, set priorities, use planning tools, get organized, schedule your time appropriately, delegate tasks to others, stop procrastinating, manage external time wasters, avoid multitasking, and stay healthy.
2. Effective time management requires distinguishing between important and urgent tasks, prioritizing tasks, and using tools like to-do lists, calendars, and electronic planners to plan and organize time.
3. Delegating tasks, managing interruptions, avoiding unnecessary multitasking, and scheduling relaxation can help maximize productivity and prevent stress from poor time management.
This document summarizes a training module on advanced management tools and processes. It discusses managing time through prioritization, setting goals and measuring performance. It provides tools for strategic thinking including SWOT analysis and setting key performance indicators. The overall aim is to equip managers with skills for effective leadership, goal alignment, problem solving and developing their team.
The document discusses approaches to improving knowledge worker productivity. It argues that the dominant approach of designing organizational structures and then fitting roles and people into them may not be effective for knowledge workers. An alternative approach is proposed that focuses first on the person, their passions and skills, and then tailors roles and organizational structures to better fit individuals. This person-centered approach includes using passion inventories, flexible job descriptions, and lateral career moves to better align people with work they find meaningful. The goal is to recruit the right people and place them in positions and an organization structured in a way that allows them to perform at their best.
The document defines accounting rate of return (ARR) as the ratio of estimated accounting profit to average investment. ARR is calculated by taking the average accounting profit and dividing it by the average investment. Projects should be accepted if their ARR is greater than or equal to the required accounting rate of return, and between mutually exclusive projects the one with the highest ARR should be accepted. An example calculation is shown to illustrate determining ARR for a project with initial investment, annual cash inflows, depreciation, and scrap value.
This document defines accounting rate of return (ARR) as the ratio of estimated accounting profit to average investment of a project. It ignores the time value of money. ARR is calculated by dividing average accounting profit by initial investment. Average accounting profit is the mean of annual profits over the project life. Initial investment may be replaced by average investment due to declining book value over time. Projects are accepted if their ARR is not less than the required rate of return. Examples show calculating ARR for projects with given cash flows. ARR is an easy method but ignores the time value of money and can be calculated inconsistently using accounting versus cash flows.
NPV is superior to IRR for evaluating investment projects. NPV considers the time value of money and all cash flows, providing a direct measure of whether a project increases shareholder wealth. It is more accurate when cash flows fluctuate or the discount rate changes. While IRR indicates return rate, it does not measure wealth effects and can be misleading when cash flows vary or multiple internal rates of return exist. NPV is therefore a better measure for capital budgeting decisions.
Net present Value, Internal Rate Of Return, Profitability Index, Payback, dis...Akhil Sabu
This document discusses various capital budgeting techniques used to evaluate investment projects, including:
1. Discounted cash flow methods like net present value (NPV), internal rate of return (IRR), and profitability index (PI).
2. Non-discounted cash flow methods like payback period, discounted payback period, and accounting rate of return (ARR).
It provides formulas, examples, and decision rules for calculating each method and comparing investment opportunities.
This document provides an introduction to key concepts in corporate finance including what corporate finance is, its relationship to financial accounting and management accounting, the concepts of risk and return and time value of money. It discusses corporate structure including sole proprietorships, partnerships and corporations. It describes the finance function and role of the financial manager in raising, allocating and returning funds. It also covers separation of ownership and management and issues of agency theory and corporate governance.
This document discusses integrating risk and knowledge management practices at NASA's Exploration Systems Mission Directorate (ESMD). It outlines five practices ESMD has adopted: 1) establishing "Pause and Learn" processes to reflect on lessons; 2) generating and using "Knowledge-Based Risks" to convey lessons; 3) establishing "Communities of Practice" to share knowledge; 4) providing knowledge sharing forums; and 5) promoting experience-based training. The goal is for ESMD to effectively learn from the past and generate shared knowledge to help achieve the complex technical challenges of returning to the Moon and Mars.
Studies show that many projects either fail outright or fail to meet most of their objectives. There are a myriad of possible reasons why this might be the case. Very often, organizations go looking for a culprit and sometimes blame the project manager or even the very concept of project management itself. Sometimes they decide to “fix” the problem by getting all the project managers certified. Or they decide to standardize on a certain tool. And while certification and standardization are laudable things, they do not necessarily address the central problem or problems. This presentation will discuss the top ten reasons why projects fail and briefly discuss solutions to each problem. We will see how such areas as estimates, scope and “the accidental project manager” contribute to the problem.
This document is from a leadership development program workbook on coaching and feedback. It includes:
1) An introduction on the importance of coaching, even for elite athletes, and how coaching can help organizations and individuals innovated and drive performance.
2) An exercise for participants to discuss the value of coaching, compare it to mentoring and training, and identify what stops people from coaching.
3) A section defining coaching as an process to maximize potential and performance by facilitating self-directed learning.
4) Guidance on giving effective feedback using the EIC framework of describing an Example, the Impact, and recommending a Change.
This is an effective process where using the answers to 'what went wrong and why', the reasons for failure are groupded thematically, and prioritised.Once the reasons are prioritised, Identify mitigating actions. Based on the mitigation plam assign responsibilities and set timelines.
Using this approach helps in finding the risks early and put the mitigation plan to action from the start instead of doing failure based RCA as we encounter failures. What makes this technique even more attractive is the fact that it can be used mutliple times across the project phases to reprioritise the plan and change the course of action as deemed nexessary.
The document discusses the processes involved in project resource management according to the Project Management Body of Knowledge (PMBOK). It describes the inputs, tools and techniques, and outputs of each process: plan resource management, estimate activity resources, acquire resources, develop team, manage team, and control resources. The overall goal is to ensure the project has the right resources at the right time by identifying resource needs, obtaining and assigning resources to the project team, developing the team, managing team performance, and controlling the work being performed.
This document provides an overview of agile development principles and practices like Scrum. It discusses agile values such as prioritizing individuals, interactions, working software, and customer collaboration over processes, tools, documentation, and contract negotiation. Key Scrum roles like the Product Owner, Scrum Master, and Development Team are defined. Scrum ceremonies like Sprint Planning, Daily Scrums, Sprint Reviews, Retrospectives, and Backlog Refinement meetings are also outlined.
Enterey Life Sciences Consulting PDA So. Cal PAI Presentation3rjohnston2268
Prep and execution for a PAI inspection, we typically organize our preparation activity into four main areas:
Plan, Prepare, Execution, and Response & Maintenance.
This document provides an overview of critical thinking, situation awareness, and decision making. It discusses threat and error management and how critical thinking, situation awareness, and decision making are essential processes in TEM. The document covers topics like gathering data, understanding information, planning ahead, assessing risks, and making choices to control thinking and improve safety. It emphasizes controlling biases, seeking multiple perspectives, and continuously learning to enhance expertise.
Monitoring at scale - Intuitive dashboard designLorenzo Alberton
At a certain scale, millions of events happen every second, and all of them are important to evaluate the health of the system. If not handled correctly, such a volume of information can overwhelm both the infrastructure that needs to support them, and people who have to make a sense out of thousands of signals and make decisions upon them, fast. By understanding how our rational mind works, how people process information, we can present data so it's more evident and intuitive. This talk will explain how to collect useful metrics, and to create the perfect monitoring dashboard to organise and display them, letting our intuition operate automatically and quickly, and saving attention and mental effort to activities that demand it.
This document discusses crisis management solutions for project management. It begins with definitions of crisis management and conflict resolution, noting that the latter involves finding root causes of gaps that create conflicts. Common root causes are flaws in planning, priorities, resource management, financial control, emphasis on technical over management aspects, personalities, cultures, communication and understanding of management systems. Solutions proposed include improving planning, defining priorities, comprehensive resource scheduling, financial training, management training, workshops to facilitate relationships, and communication planning. Mitigating measures include understanding personalities, encouraging open communication, preparing for cultural differences, and culture awareness training.
Chet Thomas is the planning manager at Norris Company, a printing plant. He is experiencing problems with stress and poor time management. His days are chaotic with many urgent but unimportant tasks taking priority over important strategic work. This is negatively impacting his work and personal life. Some potential solutions discussed are prioritizing tasks, delegating more responsibilities, and finding a better work-life balance.
Do you and your colleagues have to deliver a project? Would you find it useful to use a researched approach to identify potential issues and help avoid them?
One which involves the whole project team in an interesting and participative way? “Prevaluation” does that. This actual client case study reveals all ~ Read on….
1. The document provides 10 strategies for better time management: know how you spend your time, set priorities, use planning tools, get organized, schedule your time appropriately, delegate tasks to others, stop procrastinating, manage external time wasters, avoid multitasking, and stay healthy.
2. Effective time management requires distinguishing between important and urgent tasks, prioritizing tasks, and using tools like to-do lists, calendars, and electronic planners to plan and organize time.
3. Delegating tasks, managing interruptions, avoiding unnecessary multitasking, and scheduling relaxation can help maximize productivity and prevent stress from poor time management.
This document summarizes a training module on advanced management tools and processes. It discusses managing time through prioritization, setting goals and measuring performance. It provides tools for strategic thinking including SWOT analysis and setting key performance indicators. The overall aim is to equip managers with skills for effective leadership, goal alignment, problem solving and developing their team.
The document discusses approaches to improving knowledge worker productivity. It argues that the dominant approach of designing organizational structures and then fitting roles and people into them may not be effective for knowledge workers. An alternative approach is proposed that focuses first on the person, their passions and skills, and then tailors roles and organizational structures to better fit individuals. This person-centered approach includes using passion inventories, flexible job descriptions, and lateral career moves to better align people with work they find meaningful. The goal is to recruit the right people and place them in positions and an organization structured in a way that allows them to perform at their best.
The document defines accounting rate of return (ARR) as the ratio of estimated accounting profit to average investment. ARR is calculated by taking the average accounting profit and dividing it by the average investment. Projects should be accepted if their ARR is greater than or equal to the required accounting rate of return, and between mutually exclusive projects the one with the highest ARR should be accepted. An example calculation is shown to illustrate determining ARR for a project with initial investment, annual cash inflows, depreciation, and scrap value.
This document defines accounting rate of return (ARR) as the ratio of estimated accounting profit to average investment of a project. It ignores the time value of money. ARR is calculated by dividing average accounting profit by initial investment. Average accounting profit is the mean of annual profits over the project life. Initial investment may be replaced by average investment due to declining book value over time. Projects are accepted if their ARR is not less than the required rate of return. Examples show calculating ARR for projects with given cash flows. ARR is an easy method but ignores the time value of money and can be calculated inconsistently using accounting versus cash flows.
NPV is superior to IRR for evaluating investment projects. NPV considers the time value of money and all cash flows, providing a direct measure of whether a project increases shareholder wealth. It is more accurate when cash flows fluctuate or the discount rate changes. While IRR indicates return rate, it does not measure wealth effects and can be misleading when cash flows vary or multiple internal rates of return exist. NPV is therefore a better measure for capital budgeting decisions.
Net present Value, Internal Rate Of Return, Profitability Index, Payback, dis...Akhil Sabu
This document discusses various capital budgeting techniques used to evaluate investment projects, including:
1. Discounted cash flow methods like net present value (NPV), internal rate of return (IRR), and profitability index (PI).
2. Non-discounted cash flow methods like payback period, discounted payback period, and accounting rate of return (ARR).
It provides formulas, examples, and decision rules for calculating each method and comparing investment opportunities.
This document provides an introduction to key concepts in corporate finance including what corporate finance is, its relationship to financial accounting and management accounting, the concepts of risk and return and time value of money. It discusses corporate structure including sole proprietorships, partnerships and corporations. It describes the finance function and role of the financial manager in raising, allocating and returning funds. It also covers separation of ownership and management and issues of agency theory and corporate governance.
This document discusses integrating risk and knowledge management practices at NASA's Exploration Systems Mission Directorate (ESMD). It outlines five practices ESMD has adopted: 1) establishing "Pause and Learn" processes to reflect on lessons; 2) generating and using "Knowledge-Based Risks" to convey lessons; 3) establishing "Communities of Practice" to share knowledge; 4) providing knowledge sharing forums; and 5) promoting experience-based training. The goal is for ESMD to effectively learn from the past and generate shared knowledge to help achieve the complex technical challenges of returning to the Moon and Mars.
Studies show that many projects either fail outright or fail to meet most of their objectives. There are a myriad of possible reasons why this might be the case. Very often, organizations go looking for a culprit and sometimes blame the project manager or even the very concept of project management itself. Sometimes they decide to “fix” the problem by getting all the project managers certified. Or they decide to standardize on a certain tool. And while certification and standardization are laudable things, they do not necessarily address the central problem or problems. This presentation will discuss the top ten reasons why projects fail and briefly discuss solutions to each problem. We will see how such areas as estimates, scope and “the accidental project manager” contribute to the problem.
This document is from a leadership development program workbook on coaching and feedback. It includes:
1) An introduction on the importance of coaching, even for elite athletes, and how coaching can help organizations and individuals innovated and drive performance.
2) An exercise for participants to discuss the value of coaching, compare it to mentoring and training, and identify what stops people from coaching.
3) A section defining coaching as an process to maximize potential and performance by facilitating self-directed learning.
4) Guidance on giving effective feedback using the EIC framework of describing an Example, the Impact, and recommending a Change.
This is an effective process where using the answers to 'what went wrong and why', the reasons for failure are groupded thematically, and prioritised.Once the reasons are prioritised, Identify mitigating actions. Based on the mitigation plam assign responsibilities and set timelines.
Using this approach helps in finding the risks early and put the mitigation plan to action from the start instead of doing failure based RCA as we encounter failures. What makes this technique even more attractive is the fact that it can be used mutliple times across the project phases to reprioritise the plan and change the course of action as deemed nexessary.
The document discusses the processes involved in project resource management according to the Project Management Body of Knowledge (PMBOK). It describes the inputs, tools and techniques, and outputs of each process: plan resource management, estimate activity resources, acquire resources, develop team, manage team, and control resources. The overall goal is to ensure the project has the right resources at the right time by identifying resource needs, obtaining and assigning resources to the project team, developing the team, managing team performance, and controlling the work being performed.
This document provides an overview of agile development principles and practices like Scrum. It discusses agile values such as prioritizing individuals, interactions, working software, and customer collaboration over processes, tools, documentation, and contract negotiation. Key Scrum roles like the Product Owner, Scrum Master, and Development Team are defined. Scrum ceremonies like Sprint Planning, Daily Scrums, Sprint Reviews, Retrospectives, and Backlog Refinement meetings are also outlined.
Using Evaluation to Improve Our Work A Resource Guide .docxjessiehampson
Using Evaluation to Improve Our Work: A Resource Guide
i
GUIDE TO THE AFTER
ACTION REVIEW
Version 1.1
October 2010
A simple, but powerful method for rapid
post-project assessment
The After Action Review is useful for reflecting upon a
project during and after its completion.
Sharing the results from your AAR can help future teams
learn your successful strategies and avoid pitfalls you have
worked to overcome
Susanne Salem-Schatz, ScD, VA Center for Implementation
Practice and Research Support
Diana Ordin, MD, MPH, VA Office of Quality and Performance
Brian Mittman, PhD, VA Center for Implementation Practice
and Research Support
Using Evaluation to Improve Our Work: A Resource Guide
0
Table of Contents
Overview .................................................................................................................................................................................. 1
User’s Guide to the After Action Review ............................................................................................................................ 2
Planning an After Action Review ......................................................................................................................................... 2
Conducting an After Action Review ..................................................................................................................................... 4
Sharing the AAR Results ........................................................................................................................................................ 7
After Action Review Report Template ................................................................................................................................. 8
After Action Review Bibliography ...................................................................................................................................... 10
Using Evaluation to Improve Our Work: A Resource Guide
1
AFTER ACTION REVIEW
OVERVIEW
Organizational learning requires that teams continuously assess their performance to identify and
learn from successes and failures. The After Action Review (AAR) is a simple but powerful tool to help
you do this. Conducting an AAR at the end of a project, program or event can help you and your team
learn from your efforts. Furthermore, sharing the results from your AAR can help future teams learn
your successful strategies and avoid pitfalls you have worked to overcome.
A b o u t t h e A f t e r A c t i o n R e v i e w
First used by the Army on combat missions, the AAR is a structured approach for reflecting on the work
of a group and identifying strengths, weaknesses, and areas for improvement. It is routinely used by
project teams in the VA’s Emergency Management program and by corporations such as GE, British
Petroleum and Motorola. An AAR ...
This document provides an overview of the Marine Corps Institute course on tactical decision making for staff noncommissioned officers. It outlines the scope and objectives of the course, lists references used in developing the course, and provides a table of contents for the course chapters which will cover topics like decision making processes, situational decisions for warfighting, and developing decision makers. The estimated time to complete the self-paced course is 12 hours and 30 minutes.
The document discusses the importance of regularly reflecting on processes and making adjustments to improve effectiveness. It emphasizes that retrospectives help teams learn, take ownership, and communicate better by sharing different experiences. The document provides tips for facilitating retrospectives, such as preparing the space and materials, choosing engaging exercises, and focusing on outcomes rather than problems.
Can Agile Work With a Waterfall Process?John Carter
This presentation was give to a Agile Community of Practice in a very large health care organization to help the Agile Team Leaders define and implement their Agile Transformation in their Waterfall environment. We show that combining Agile and Waterfall yields the best of both worlds for flexibility, time to deployment, and innovation.
This document discusses project human resource management. It covers developing a human resource plan, acquiring the project team, developing the project team, and managing the project team. Key points include identifying roles and responsibilities in the human resource plan, negotiating for and acquiring project resources, using training, team building activities, and addressing conflicts to develop the project team, and providing feedback and managing changes to the team. Motivation theories like Maslow's hierarchy of needs and McGregor's X and Y theory are also referenced. The overall summary is that this document outlines the main processes for organizing, managing, and leading the project team over the project life cycle.
This document discusses agility in leadership and management. It covers agility in psychology and software development as context for agility in leadership. Key aspects of agile leadership discussed include focusing on individuals and interactions over processes, collaborating with customers, responding to change, and valuing working software over documentation. The document also discusses the history of the Agile Manifesto and its principles of balancing documentation with active work. Various leadership theories and practices to empower teams are presented, including delegation poker exercises and focusing on intrinsic desires and motivation.
The Microsoft Solutions Framework is a flexible and adaptable framework for successfully delivering IT solutions faster and with fewer resources while achieving higher quality results. It focuses on open communication, shared vision, empowering teams, clear accountability, delivering business value, agility to change, and learning from experiences. The framework includes process models, foundation principles, and recommendations for addressing common project challenges such as disconnected stakeholders, unclear roles and requirements, and lack of business understanding.
The document outlines 11 key leadership skills that can be learned and applied to leading an Exploring post or other group. These skills include understanding group needs, knowing resources, communicating, planning, controlling group performance, evaluating, counseling, representing the group, sharing leadership, setting an example, and effective teaching. Mastering these skills can help any leader improve their ability to guide a group and get the most out of its members.
The document outlines 11 key leadership skills that can be learned and applied to leading an Exploring post or other group. These skills include understanding group needs, knowing resources, communicating, planning, controlling group performance, evaluating, counseling, representing the group, sharing leadership, setting an example, and effective teaching. Mastering these skills can help any leader improve their ability to guide a group and get the most out of its members.
The document outlines 11 leadership skills that can be learned and applied by Exploring post leaders and officers. These skills include understanding group needs and characteristics, knowing resources, communicating, planning, controlling group performance, evaluating, counseling, representing the group, sharing leadership, and effective teaching. Mastering these skills can help a leader gain experience and improve their leadership abilities in Exploring and other contexts.
SAFe PI Planning - How to conduct it in a distributed environment.
The following key topics are covered here:
* PI Planning Overview
* Inputs and Outputs
* Standard Agenda
* Why distributed PI Planning is needed
* Planning Locations
* Distributed PI Planning Agenda
* Facilities
* Working Agreements
* Tooling
* Facilitation
* Event Preparation
* Summary
* Q&A
Improve the effectiveness of behavior based selection by incorporating competency modeling into selection and also training, performance management and succession planning
This document recognizes Rear Admiral Donald E. Gaddis for the 2014 Secretary of the Navy Acquisition Excellence Award for his leadership as Program Executive Officer for Tactical Aircraft from 2010 to 2015. It contains RADM Gaddis' reflections on acquisition leadership, program management best practices, and lessons learned over his career managing programs like the F/A-18 Hornet and Super Hornet. The document provides advice to acquisition leaders on topics like leadership, teaming and relationships, people management, and the pillars of a successful program.
De twee grootste industriële rampen, 25 jaar later: Pemex in Mexico City en Union Carbide Bhopal (1984). onderzoek, feiten en zijn lessen geleerd? Overige besproken incidenten met BLEVES: LPG-bollen Feyzin (Fr.) 1966, DSM geleen 2003, BP Texas City 2005 en NAM Warffum 2005. ook bleves gastankwagens Los Alfaques 1978 en LPG-tankwagen Nijmegen 1978, belve LPG-tankwagen Ankara 2003, spoor bleve LPG-wagons Viareggio 2009
door Chris Pietersen, onderzoeker en lid adviesraad gevaarlijke stoffen
Op zoek naar vakmanschap en waarom kennisoverdrach neit werkt. Uitermate inspirerend verhaal over hoé je gedreven mensen slimme oplossingen laat bedenken voor urgente problemen.