Lessons learned in Project Management

Lessons learned in Project Management

Lessons learned (it may be +ve or -ve) in project management are the knowledge gained during a project that can be used to improve future performance.

Lessons learned are documented with solutions to provide future project teams with information that can increase effectiveness and efficiency.

Every project manager should be well aware of the impact lessons learned can have on the current and future projects.

However, despite knowing the value of lessons learned, not everyone makes full use of them.

The lessons learnt documented using below process flow:

1) Identify:

Identify comments and recommendations for use in future project.

This is usually done through a project survey that is sent out to all team members. Various questions connected to a project help the participants share their lessons learned.

2) Document:

Document and share the findings

3) Analyze:

Analyze the finding and find the solution

4) Store:

Store in a repository

5) Retrieve:

Retrieve for use in current projects

Suggested categories for lessons learned include:

Project management
Technology
Communication
Business processes
Requirements
Design and build
Testing
Implementation

The fields used in the Lesions learnt document:

Lesson learned
Subject
Project Name
Business Line
Technology
Experience type
Situation
Comments
Recommendations
Date

Comments

Voice of the Customer (VoC) vs Voice of the Business (VoB)

Tthe differences and strategic importance of Voice of Business (VoB) and Voice of Customer (VoC) in Lean Six Sigma: Voice of Business vs Voice of Customer: Aligning Strategy with Value In the world of Lean Six Sigma , success hinges on understanding and balancing two critical perspectives: the Voice of the Customer (VoC) and the Voice of the Business (VoB) . While both are essential for driving sustainable growth and operational excellence, they represent distinct priorities that must be harmonized for optimal results. 🔊 Voice of the Customer (VoC) Definition : VoC refers to the needs, expectations, preferences, and feedback of the customer—whether internal or external. Focus Areas : Product/service quality Delivery timelines Customer experience Responsiveness and support Methods of Capturing VoC : Surveys and interviews Focus groups Customer complaints and feedback Net Promoter Score (NPS) Goal : To ensure that processes and outputs are aligned with what the customer truly ...

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics, Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims: Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)

High-Tech Yuga

Search This Blog