PMP:

11.09.2024

2 Certificate examination:

PMP - Project management Professionals –Experienced persons

CAPM- Certified associate in project management Just graduated

Practice not to memorize

Process is a sequence

Conflict Arises Due to personal Interest, Thinks Authoritative,

Blame storming instead of Brain storming (shall always find out the cause and make proper analysis
during handling conflicts)

People, Process and Business Environment have to be excelled

Tailoring the needs (tailor the tasks and enablers)

Tailoring the needs

50% from Predictive and 50% from Agile projects in Exams

ASAPPredictive / waterfall (Full existing plan)Standard approach SOP Chemical industry

Agile/Adaptive - IT Industry Flexible Creative improve the process

Iteration: The repetition of a process for improving (Trial and Error), testing again and again

Increment: Next step/process placing battery in Bonet, or putting potatoes boiled taken out and
added flavours and put it to boil again

Iteration + Increments  Agile

180-5 demo questions-Total 175 questions in 230 minutes

10 minutes break can be used for revision- Don’t press the next button after 60 questions

75% marks passing

In a year 3 times… but everytime fee payment

60 PDU (professional development unit)s are mandatory.

CCR – Continuous certification requirement

Label to the experience and branding is required

13th Sep’24

Exam booksPMPBO guide

Rita Mulcahy's PMP® Exam Prep, 10th and Eleventh Edition  7500/-

Headfirst PMP book

Eliminate answer methodology Stick to Principles

Gem store/Gem market – Store for all certified supplies from where one can procure products.

A sequence of tasks that must be completed to attain a certain outcome

Department Goal and organization Goals should be same
Project managers are like small business owners
Artifacts : Computer generated reports, progress reports, status reports, MOM’s etc

Note: Project has a fixed duration program does not.

16.09.2024
PMI project management information

In some cases, we have the ACOES Agile center of Excellence services also called VDO – Agile

CMS – Content Management System

Strict Template Project is Predictive and Waterfall

Any small changes in Template design with use Agile , and it is called Hybrid mode

Lessons learnt – Gives insight about based on how problems and risks were faced, decisions made,
who helped, how , results after this, how did the project complete in the previous project.

Supporting PMO gives procedures, protocols, templates and lessons learnt. It has very less control
over the project.

Controlling PMO gives training, induction etc. It has control over the project. All clearances for the
projects have to be done from this PMO

Directive PMO is responsible for the result of the project. Members like high level stakeholders are
present in this PMO.

Supportive PMO+ Controlling PMO+ Directive PMO = Predictive project

Usually controlling & Directive PMO’s are functioning. Controlling PMO does Supportive PMO’s work
Weak matrix structure – project manager lesser authority & control

Balanced matrix structure – project manager has considerable authority & control

Strong matrix structure – project manager has strong authority & control

One more organization structure is flat organization structure where CEO will take reporting from all
the staff
18.09.2024

Business Environment/ Business influences

Enterprise Environmental Factors (EEF’S):

1. Internal EEF Factors: Controllable

Organization culture and structure - Toxic culture, helpful culture, Culture of mentorship , values
and structure, organizations attitude towards risk decision making approaches, project governance,
communication style etc.

Organizational policies, procedures and Guidelines- Every organization will establish their own
policies, procedures and guidelines, it dictates how projects are planned, executed, controlled,
monitored. Project manager & methodologies, standards, documentation etc

Physical and environmental conditions- Geographical location, Climate, Infrastructure, ecological

impact, natural disasters. Can affect resource allocation. Eg Covid 19

2. External EEF factors: Uncontrollable

Market conditions/Trends – Economic conditions, market trends, pressures etc are going to affect
the project trends, schedule, budget, risk management etc

Social and cultural influences and issues – Ethics, code of conduct & perceptions. You have to tailor
your project or product as per customers according to these factors.

Government Rules Regulations – like Political situations, govt policies, , licenses, compliance with
law, permits etc. Eg GST, previously VAT, IGST for interstate goods transportations. Academic
research, Financial conditions of region of operations, Exchange rates etc.

Organization Process Assets (OPA):

Organizational Rules and Guidelines or Processes and Procedures – these are present throughout
the tenure of the project. Policies, procedures, guidelines, templates, standards are covered under
this section. A project charter is prepared on this basis. Every organization has its own templates.
Project charter contains name of the project, ideas of project, domain, start date, end date and
project tenure, project objective, scope, stakeholder list, output ,reporting, Policy for using social
media etc.

Knowledge base or corporate knowledge base – Lessons learnt, Historical references

Note : OPAs always originate from inside the organization, while EEFs
always originate from the environment outside the project.
1. Introduction:
Starting phase. Short phase. It is usually the product launch ie to sell the product. Focus on
launch is very important. Organization has to invest a lot of money. ROI is very less as lot of
expenses on selling the product. Advertisement, dealers to be approached.
We require help from different departments (production, logistics, marketing, dealers). In
this phase engagement activities focus is on successful launch and sales are the goal. There
will be many projects happening from different departments. Eg: Marketing – Digital
marketing, Print media marketing etc.
2. Growth:
People are understanding the product and its uses. Organization has to keep spending their
money to upgrade sales. ROI is comparatively handful. People are getting awareness of the
product. Word of mouth is spreading.
There will projects to fix the faults in product (bug fixing). Investment on advertisements will
be happening. A continuous support activity for the sales will happen in this stage. Eg
Starting of WhatsApp where we never had too many upgrades. ( Competitors arrive slowly)
3. Maturity:
Product is matured. Longest phase ever. Organization needs to do little investment. People
are completely aware of the product. They are using it regularly. People refer our product.
In this phase we see ups and downs. Efforts to be made to make the product consistent in
the market. This is the phase to get maximum ROI. In this stage there are projects happening
to upgrade the product. There is increase and decrease in sales. Eg: Voice notes and money
payment options upgradation in WhatsApp (addition of new options)
4. Decline:
People does not want to spend on the backdated product. A market competitor with an
upgradation is introduced with new upgrade, features and facilities then this product loses
its interest and value. This product would not be preferred. This phase is decline. At this
stage the organization stops investments but introduce incentives, schemes, offers and will
continue to finish the sales. Flush sale will be introduced. Eg e-commerce organization who
give facility to purchases to clear the dead stocks. In this phase projects are happening to
clear the products. Organization stops investing on marketing and employment in that
segment.

20.09.2024
Principles of Project Management

Steward Management

Leader takes the overall responsibilities, achieves the goal along with his team,
Steward is taking care of things and taking care of responsibilities.
Stewardship is taking care of project activities with care, behave honestly, ethically,
depicting ourselves, our roles, our team, our goals, our authority accurately in a trust worthy
way, Compliance with rules and external to the organization.

Internal Responsibilities of steward:

1. Operating in alignment – Organization objectives, strategy, Vision, Mission, to sustain
and make journey towards its goal. Alignment along everything is very important. This is
the responsibility is of steward. Team engagement commitment and creation of
respectful environment is a responsibility of a steward. Steward should be active
2. Maintaining resources like finances and materials to be handles by steward. Usability of
resources and maintenance to be taken care.
3. Appropriate use of power, authority and accountability.

External Responsibilities of the Steward:

1. Resource Management : Resource may be Human resource or Physical resource. Eg of

Physical resource is supply chain, machines, equipment etc. Sustainability of
environment is Steward responsibility.
2. Maintaining relation with external Stakeholders like clients, contractors, vendors, SME’s,
Customers, Contractual employees who are source of the project. Steward should
maintain good relationship with all these people.

Personality demonstrates person’s value.

Sustainable environment and condition of people across the planet should get reflected.
High performing project consists of professionals who diligently oversees matters like
responsibility and care.

Team
We should create a collaborative team environment and it has agreements, structures and
processes.
Team agreements – working norms which are established by the project team. Can be
Verbal norms to be followed. As a project manager we have to establish the team
agreement. Should be created before the project is started.
There should be a formal commitment.

Processes are also important other than team creation

Kanban (Kan- sign, ban -board) – Visual management system, comes from Agile
methodology. It is a frame work. This has a list of process and bullet points. You can manage
department work, team work, individual work, nonperformance and also what is not being
performed. This limits the wastage of resources.
This is generated by Toyota
This type of process enhances the project. This gives the team members to have authority
and accountability. We can have a high performing team.
High performing team always has team agreements, organizational structure, processes etc

Stakeholder
Stakeholders are the individual who are getting affected by the project, program or portfolio.
They have a great effect directly or indirectly. Stake holder engagement affects the value
delivery of the project.

Value Indicator

Course of the project should always be on constant evaluation and need to have an
alignment of project with business objective. We should always understand the success
indicator. This drives the project towards the goal. Value of project might differ from
individual perspective. Financial, social benefit/ customer. Accordingly, Project team
meets/exceeds the value. Project justification and business needs are important elements.
Business need has to be understood. Business Need tells us about initiation of work. Without
understanding the business need we cannot perform and it leads to defective product or
rework.
Project justification is connected with business needs. It explains the investment in the
business.
Business strategy is where you are and where you want to be. The methods and action plans
, approaches taken to move from one point to other in the business. This creates value to
the business. Business strategy is needed to achieve its value. Without strategy in a business
is like a tourist without a map.

Systems Thinking
System includes some interdependent and interacting domains of activity which has a
holistic view and consists of factors inside and outside the project.
Systems are constantly changing and require consistent attention to the internal and
external conditions.
Eg: Any small change in a resource has a great impact on the project. Some people might get
affected like contractors, suppliers, contract providers, regulators etc. We can see changes in
project cost, schedules, budget and it impacts the project.
Project team is inclusive of many people with diverse skill set, they often get engaged as a
project team, just because of project system for common objective.
Sympathy & Empathy
Empathy – we get close to the person and feel what the person feels.
Empathy with business areas, critical thinking, assumptions and challenges to those thinking,
dealing with uncertainty and project risk management in the early stages of project, making
clear communication with the stakeholders, ability to adjust to the changing needs of the
customer. If these are done in our project management definitely, we are going through
systems thinking. We are thinking in a systematic manner.

Skills on systems thinking:

1. Empathy with Business area – Upgrading a product needs to be listened and felt to
people and critical thinking is needed. We need feedback and externa review or advice.
2. Diagram below is empathy map. What people say, think, does and feel about the
product
3. This gives an idea about need of the people. This leads to brainstorming and building the
product.
4. Empathy is for all human beings (stakeholders) related to the project

Empathy Maps are great tools not only for getting to know users but also for sharing this
knowledge.

Leadership
Leader shholud have a combination of all types of leadership.

1. Autocratic/Authoritative Leadership:

Leader solve the issues by observation and thinking about the requirement of all people and
benefits.
No opinion is taken from the group.
Leader is the person who dictates all the work, methods and process to follow.
Decisions are more quick without accounting too many people into it.
This leadership is in existence where there is lot of risk in the project, time available is too
short and also to save people life, focusing on life and price.
Focus is mainly on use and utilization of resources.
Characteristics – very little / no input from the group member
There is no use of your brain
Eg : covid 19, Nuclear project, chemical project

2. Democratic Leadership:

There is a controlled approach towards the team. There is an equality in the team.

Team members participate I decision making.

No nepotism.

No conflict

Participants are encouraged, they express their opinion

Final decision is by the leaders

Group members are engaged and motivated

Concern of all team members who are participating or not participating is taken. Decision of
all those present.

Eg : Election (common people are decision makers)

3. Participative Leadership:

People are allowed to participate (Similar to democratic. There is a thin line of difference) in
the process.

Leader gives decision, based on the insights and inputs by the participants.

Insights of only those who participate are taken.

Eg : Parent teachers meeting (only parents are the participants)

4. Laisere Faire Leadership:

Leader supports the team with resources , tools and requirements.

Leader won’t/ give little guidance the team.

Ultimate task to be performed by the team.

Participants to sort out their problems

This is good for rewards and recognition

Participants have complete freedom in decision making

5. Directive Leadership:

Similar to autocratic leadership

Telling followers what needs to be done and giving appropriate guidance along the way.

Giving schedules of specific works to be done, at specific times.

Rewards will be given. Ambiguity will be decreased.

When task is unstructured and team & members are not experienced then direct. Leadership

Brain can be used.

Eg : Defense

6. Supportive Leadership :

Leader makes work pleasant for employees by showing concern by being friendly and
approachable.

Concern for team’s welfare and creating friendly work environment.

Increasing self-esteem, making the job more interesting.

This is required during stressful, highly competitive environment and boring situations
High performing team shows a universal pattern of continuous improvement. Leader applies
various skills and techniques and combination for focusing on Project teams, agreed goals,
seeking consensus, motivating the vision, overcoming the obstacles etc.

23.09.2024

Tailoring

Tailoring is customizing and personalizing things. Tailoring in project management is

choosing right approaches based on organizational context, team culture, project maturity
and delivery.

Tailoring has a goal of maximizing the values by managing constraints and by improving the
performance.

Tailoring is iterative in nature. Tailoring is required till we get perfection. Project teams
understands these tailor-based methods and usability. It is a constant process and continues
throughout the tenure of the project. It is influenced by constant feedback.

Eg: While handling a big sized project a small or mid-sized project has to be handled. We will
have to do only required documentation not like how we do for big projects. Only must
complete things are carried out. We will be compressing the documentation. It will be like a
funnel.

Tailoring approach along with appropriate processes, methods and artifacts can help entire
project team for taking decision about cost related, value contribution and project outcome.

A tailored project gives too many benefits. It leads to reduction in wastage of resources. It
leads to better resource management. It leads to efficiency in productivity

Most appropriate methods of products the desired outcomes

 It helps in creating a lesson learnt document

Quality

Quality should be built into processes and results, as stakeholders expect to get an end
result which is fit for their purpose and meet their needs.

Project team use a Metrix to measure the quality based on the criterion for requirement.

Requirement is expected from all. Requirement is conditions/capabilities that are necessary

to be present in the project or product service.

Quality is applicable to the project activities and approaches. Quality is always focusing on
the requirement.

Dimensions of quality are performance, sustainability, resilience, conformity, reliability etc

Objective of Quality is to understand the objectives of the stakeholders are met. It is to

minimize the waste of resources and maximizes the profit without any defects in
deliverables and quick deliveries.

Positive outcomes of quality are less rework, save cost & time, improve efficiency, less
customer complaints, continual improvement and better product.

Complexity
Projects are not complex but organizations are complex

Continually evaluate and navigate project complexity to successfully navigate the project life
cycle.

Uncertainty is lack of necessary information to make a decision. Ambiguity is lack of clarity.

Source of complexity - Human behavior like personal agenda, language barrier, time zone,
variance in culture.

System behavior - Too much technology is a threat or leads to negative results and
unpredicted problem.

Volatility is rapid and unpredictable change.

Complexity is due to diversity of stakeholders, regulatory agencies, international financial

institutions, multiple vendors, subcontractors, local communities etc.

Risk
Risk is an uncertain event or consequence. Risk is not always negative. It gives an
opportunity. Risk can be negative or positive ie threat or opportunity. Both risks have to be
analyzed in a constant manner.

Positive risks have to be maximized and negative risks have to be minimized. This process is
called optimized risk responses.

Adaptability and Resiliency

Project performs in the way we plan during initiation. There are internal and external
influencers. Eg: Regulations may influence to change the scope, Pandemic changed the way
we conduct virtual meetings.
Learning plan creation is important before the initiation of project for team like technical
knowledge, listening to the stakeholders is important to decide on best solutions.

Change

Change is a development approach. Change has to be done keeping too many aspects in
mind. Change can be internal/external. Stakeholders sometime decide on changes.

Development Approaches
1. Water fall model/Plan driven/fully plan driven approach

5.Testing can be done after entire project is completed

Phase – Initiating (feasibility testing, understand business case, talking to the

organizational people, prepare project charter) – Planning (on integration, schedule,
scope, quality, communication, risk)- Execution (start working as per the plan) –
Monitoring and control (adjustments) – Closing
Frozen requirements – scope is fixed/locked (IT projects scope can change)
Eg: Restriction on building floors
Specific deliverables – Output is locked to single or specific product/service
Testing can be done only after the completion of product.
Eg: A car can be tested inly after the vehicle is made.

Burj kalifa is an example for waterfall method

Advantages:
Phase gates are Check lists which we follow. This can lead us to be double sure we are going
as per the planning.

25.09.2024
Agile is flexible. Entire project is in small pieces. Before completion of the project customer
can be given something out of the project to use. When things don’t go well, diversions and
systems changes are needed, changes are required (scope) agile methodology is used.

It is different from waterfall

1.Practices like gathering feedbacks, validation of assumption, making adjustment etc

2.Driven by people. Users are the people who give feedback. You cannot completely go by
feedback which can lead to scope change. You should always work within the scope and
satisfy the requirements, quality and value.

3. Continuous feedback is there throughout the tenure of the project.

3. Refining the requirement is important to avoid repetitions and other aspects.

4. In agile we have cross functional teams like matrix organization structure. One person will
not do only one thing. Eg: developer working as a tester and does other tasks as well.

Employees are not categorized on single skill set. They have to work with the organization in
collaboration.

It is environment of transparency, guidance, learning and understanding.

1. It is flexible as we can do changes in scope of the project. We may carry out changes
because of unforeseen circumstances. We should not only work in agile platforms but
also our mindset and hierarchy also should be based on agile. Changes and adjustment
are always present.
2. All people work very closely. This leads to transparency in communication and
collaboration.
3. MVP – A minimum viable product can be availed in agile at the earliest ie even before
the completion of the project. Delivering the product in early manner. Agile gives rise to
continuous updates of our system. Constant feedback and software upgrades are
possible in agile.
4. Suitable for uncertain project . Eg: Development of vaccines. Initially we don’t know the
results, but we keep on improving.
1. You can always train the team as we have individuals from cross functional teams with a
skill set of two or more jobs.

Project charter : Includes Total budgets, milestone. Project charter formalizes the
project. It is a dynamic document, where changes can be made with approval.

Agile values
Agile manifesto values people over process and tools. As people adapt to needs. If its tool
driven adjustments become scare. So, people are valued more.

Value is focusing on iteration for product development.

In tool driven testing process takes a lot of time and hence the late delivery. Agile is people
dependent, through iteration and adjustment we can achieve early delivery.

Negotiation is a time when the customer and delivery manager work out details of delivery.

Customer negotiates on the details of product before any work commences. Customer is not
involved in process. Customer involvement will be there throughout the tenure of project.
May be in periodic demos, daily part of the team to meet the business needs of the product.

If a walking product is put into the customers hands early then the feedback on
improvement can be gained.

Early & continuous delivery reduces the risk of building features. It avoids long upfront
cycles of planning in which all things are documented in details before the development
begins. It decreases the potential risk.

Software development are changeable as customers preferences may change like changes
in market, competitors’ activity, new technologies etc. These can be accommodated in the
project. This can happen in the beginning and at the end of the product.

Agile only focuses on what is done not on what is not done.

Close collaboration gives rise to better communication and efficiency. Teams are motivated,
talented and empowered. It gives a sense of ownership.

In person conversation leads to better understanding and clearing differences.

Working software, a functional product but not extensive meetings and documentation can
be used and tested and gives feedback for the team to give better results.

Creating a working environment for team to work continuously on development of

sustainable product.

Effective coding to develop a better product (technical tool)

Agile manifesto is simplicity. This does not mean a short cut or incomplete delivery. It avoids
too much complexity. Agile focuses on smart work (right work not lot of work, does not do
extra work.

Harmonious work between the team

Last principle is very important

Customers feeling is important now a days. Empathy map is a tool that put customer
research in a quantifiable format to have a better understanding of issues.

Center Smylie is user persona. Work performed is based on persona. Feedback collection for
empathy is feedback forms and interviews. They should have close ended and open-ended
answers.

27.09.2024

Root cause analysis

Fish bone Diagram/ Ishikawa Diagram/Cause and effect Diagram

5Y

It is a visual tool to figure out the cause for problem analysis. This diagram is for Root cause
analysis and problem solving. It was popularized by Japanese quality control expert Quaru
Ishikawa.

It helps to identify the root cause. It breaks down the problems into some categories. Also
going to add some points on each fin under categories and subcategories. It gives detailed
understanding of the cause. Apart from this it helps us promote the team work. It
encourages collaboration and brainstorming. It visualizes complex problems and gives the
details in graphical representation.

It shows action plan and they have been taken care of.
1. Define the problem : State every thing precisely. Avoid 2 statements.
a. Instead of writing poor product quality, write it as high product defect rate by
percentage
It helps to focus on analysis part. This specificity gives an understanding that the
product is defective. Issue might not be in build quality, might be there is a system
defect, service quality and the entire product is not defective & defect is only 32%.
We can focus on the process through which it is getting defective.
b. Problem needs to be quantifiable and specific. This helps in setting up the success
criterion for the solution and allows measurement of progress achieved so far.
A defect rate of 10% gives a clarity and we can avoid working on other 90%. Impact
of the problem has to be analyzed properly.
2. Identify the key categories:
Key categories like People(training, attitude, skills/Behavior, human factors ),
Process(Systems, SOP’s, workflows), Environment, Operation and Quality, Equipment
 (machines, tools, technology), materials ( suppliers, quality)/measurement are same for
all domains. This has to be decided by the domain type and what we are searching.
Before performing the RCA brainstorm as much as possible. Try to organize the causes
categories/segments.

3. Brainstorming:
After completion of the categories, we have to understand and include other thing in
these categories. Apply a cross functional team which is composed of various people
who will contribute different perspective and knowledge. This will ensure
comprehensive list of possible causes and avoid grouping. Crate an open and safe
environment, where everyone will feel free to respond fairly. Open and honest
communication happens. We should have a participative leadership.

4. Analyze the diagram:

Observe the diagram as a whole. Other things creating negative impact on the work flow
have to be located. Identify the pattern. It is a team work . When team
work/brainstorming is done by to get corelated issues. This can push us towards more
profound problems. Try to prioritize the causes, note it down and prepare the action
plan based on the causes.
Environment Equipment People
New Employees

Congested place Old telephones Lack of training

Noisy, cannot listen No upgrade Under staffing

Management Style Decline in Customer Satisfaction

Complaint management Defective hiring policy Timelines

Planning SOPS No escalations

Technology lack of issue resolving parameters

Systems Policies Process

30.09.2024

Kanban

It is a visual system of work management which emphasizes on continuous flow and limitation of
work in progress.

Core Principles of Kanban

Visualization of work flow - Creates the visual representation of the work which includes the
different strategies, different stages it goes to. It can be in the form of a board/chart/diagram & can
be easily accessible by the team members. This helps to identify the bottle necks and inefficiencies,
flow of work, improves the communication among the team members. Prioritizes the work and
avoids rework. Avoids duplication.
Limiting WIP (work in progress) - Setting a limit on number of tasks in a project. By this we can
reduce multitasking, contestation, improve processes, work flow, focus on efficiency, productivity is
increased, reduce the waste and errors.

Manage flow – Helps so that work moves smoothly, continuously without interruption & blockage.
It helps to identify bottle necks. Improves workflow through each stage, reduces lead time and cycle
time increases productivity.

Make policies explicit – It defines and documents the rules and guidelines which governs the work
flow It includes definition of done ( Set of criteria that the product increment must meet to be
considered complete and ready for release. In agile it is when the work is complete and shiftable).
Explicit policies helps teams can improve communication. Improves transparency and accountability.
Reduce errors and confusion.

Implement feedback loops – Creates a mechanism when we are in need to get feedback.
Planning and documentation are there. ( Waterfall/predictive system : Throughout the project none
of the clients/ customers are involved so there is no scope change)

In agile continuous feedback is there as users are engaged. It can identify the areas of improvement,
data driven decisions, quality customer satisfaction.

Continuous evolutionary – Embracing a culture of continuous learning & improvement. Recognizing

experimentation and risk taking. Failure is an opportunity for learning and growth. By continuous
evolutionary improvement teams can stay adaptable and responsive for changing circumstances. It
improves customer satisfaction. Team stays engaged and motivated. Can stay competitive and
innovative.

Improvement – Continuous improvement is an ongoing process. We can make changes which can
add up to our time. Improvement is necessary for success. We can improve the team effort.

Kanban Board:
It is a graphical representation of steps involved in completing a task or project.

Kanban Cards

It is common way to visualize the work flow is to use the columns shown above. It represents the
different stages of work. We can change the level of the column depending on the level of
requirement and domain. Like work waiting to get started, work in progress, done and ready for
review/testing.

Team members can see, understand and get the track of the project.

Kanban card is for visualization and manage the work. Helps in prioritizing. (Dev Ops)

Better collaboration and communication

Identify the bottle necks

Detect the issues and take appropriate action whenever required.

Improved work flow

It gives structured and disciplined approach. Steps involved in delivering the values is
understandable by the team. Optimizes the processes and streamline the work.

Focuses on completing the tasks. Encourages frequent feedback loops.

Ensures high quality of work is delivered in constant manner

Highly adaptable and flexible. This makes thing easier for customization & implementation within
the team and organization. It helps in management of performance and reduces the rework.

Everyone can visualize the structure.

Scrum:
A framework based on agile. Light weight as it gives minimalistic set of roles, events, artififacts that
might be tailored into concrete practices for some specific projects within an organisation.
(Predictive is ver rigid in documentation, engagement of too many people and roles).

It defines specific roles events and artifacts for managing and controlling different types of projects
and products.

It is a cyclic process of repetition ie ieterative. Each cycle is short in length and time. Each cycle is
called as sprint. Increment is small steps to make and improve the product. At the end of every
sprint the team delivers a product increment which is potentially suaitable for product functionality
which allows for early & frequent feedback of stakeholder/customers

Scrum defines 3 roles.

Product owner, scrum master and development team

Events : daily scrum, sprint Planning, sprint review, sprint retrospective

Product backlog, sprint backlog and increment are the main documents in scrum.

Increased productivity can be achieved through scrum by intellegent teams to deliver on high
priority items and limiting the work in progress. Endless on going activities are kept focused on
delivering value by introducing a sense of of urgency with a time boxed short sprint.

Due to its incrremental and ieterative nature scrum supports early and continuous delivery of
potential releasable increments. At the end of small sprints small pieces of valuable functionality we
can see which team can deliver.

It is an emperical process. It is transparent and open to inspection for improved adaptation.

Scrum roles

Product Owner

Product Owner

Is the key role in scrum.

1.Responsible for owing and managing the product backlog ( they are the required features and
functionality which should be present in the product/deliverable). They are voice of customer and
responsible for ensuring the team is doing the right thing in the right way and in the right time.

Defining and prioritizing the product backlog. Shall I include all the user stories that need to be
developed. Manage the backlog based on business value, risk, complexity and other factors to
ensure that the most important items are addressed at the first.
User stories: These are the informal descriptions of the features & functionalities from the
perspective of end-users. There is a specific format through which we need to perform .

As a [ User Role], I want to [ do something], so that [ it can achieve a goal] – this way we can come at
a user story.

2. Ensuring quality: Product meets the required quality standards of the end-user. So, the product
owner closely work with the developer to ensure the product meets the expected criteria.

3. Availability and communication: the product owner should be available to answer questions and
provide guidance to the development team, throughout the development process. They must
communicate with the stakeholder effectively to ensure everyone has a clear understanding of the
projects progress and rules. Managing Stakeholder responsibility is one of the responsibilities of the
product owner. Should ensure the stakeholders what can be delivered within a given time frame and
within the budget.

4.Providing Feedback: Product feedback to the development team on the usability, functionality and
performance. Work closely with the team to ensure any defect or issues are resolved quickly and
efficiently. Product owner collaborates with cross functional teams to ensure the project lines and
meets with the overall business strategy and meets the customer needs. Leading by example –
Product owner sets the tool for team’s culture and behaviors, providing transparency, collaboration
and continuous improvement. They must have excellent communication skills, strong decision-
making ability, deep understanding of the product and its market.

Scrum Master Role

Is a role in the scrum framework which ensure the team is following the scrum process in achieving
its goal?

Scrum master is liable to see to it all team members are working as per the scrum rules and
guidelines, team members are having understanding on scrum and applying scrum in a proper
manner.

Role is to facilitate meeting, remove impediments and help the team stay focused on its role. These
people ensure that the team adheres to scrum principles & practices like transparency, inspection
and adaptation. Have to serve the development team by helping it follow the scrum frame work and
achieve its goal which includes facilitating sprint planning & daily standup meetings. Shall help the
team remove any type of obstacles for impediments that may be preventing them from completing
their work.

Development Team:

Developers are the backbone of the system. They take product backlogs and transform them into
deliverable. Developer is member of the development team and responsible for the delivery of the
increment. A development team is usually composed of a professional having multiple types of skills
like development, testing, designing, content writing, analysis etc.

Product it achieved through team work by the developers in a self-organizing manner. They deliver
the product by showcasing their tools, skills and expertise. Developers are empowered to make all
decisions concerning by doing the best work towards desired outcome.

Delivering the project, increments, collaborating and organizing, participating in scrum events,
ensuring quality and continuous improvement etc.

Ceremonies:
Sprint Planning:

It is critical event in scrum. Team comes together to plan and committ to a set of work for the
upcoming sprint.

It defines the goal and scope of the sprint which create a plan for delivering a value faster
collaboration and allignment.
Epic

Themes is feature as well

User Story lines, story points – one story line is one sprint

Construction of building

a. Preconstruction
b. Construction
c. Post construction

Sprint planning is a meeting where we discuss with the team members how we are going to perform
the sprint. Product owner plays a crucial role. They provide clarity on the product vision, the goals
and priorities. They are responsible for maintaining the meeting and prioritizing the product backlog.

Scrum master facilitates the sprint planning session. They see to it that the event is productive, they
are focused and time boxed. They encourage the collaboration and remove the impediments which
hinder the team’s ability to plan effectively.
Development team actively participate in the planning. They provide estimates, identify the tasks,
start committing on the sprint goal.

Activities : Product owner shares the product plan; product owner and development team review
the product backlog item and ensure they are well defined and clear they are ready for estimation
and selection. They jointly select the items required for the sprint.

Sprint Review

Reviewing what has been done in the sprint.

It is a valuable ceremony which promotes transparency, collaboration and customer engagement.

It provides an opportunity for the entire scrum team to showcase the work, receive feedback and
adapt the product to meet the customer need and market demand.

We try to understand what went right and what went wrong.

Focus on what didn’t go well.

Scrum master facilities the session. Ensures it occurs at the end of each sprint. . They encourage the
collaboration and remove the impediments, guide the team and guide the team to give encouraging
feedback.

Product owner plays a central role in the sprint review. Present the backlog during the sprint, explain
the progress made and provide the context for the demonstrated work. Also gathers feedback and
prioritizes updates the product backlogs based on the insight gained.

Development team they show case their completed work, they provide technical insights, they
answer the questions on the product increment. Gains feedback directly from stakeholders.
Sprint retospective:

We focus on what we did through out the tenure of the work and what we need to plan what we are
going to perform. Ie looking back to the past.

Provides the oppurtunity for the entiere scrum team to reflect the past sprint.

Identify the improvement area, to make positive changes.

Scrum master facilitates the session. Ensures it occurs at end of every sprint. When we are
completing one sprint which remains from 1-4 weeks when we are ending the sprint this has to
happen between all participants. They encourage the collaboration and remove the impediments,
guide the team and guide the team focus on the improvement.

Product owner actively participates in the review. They provide insights into the product
development processes and product progresses.

Development team share their experiences, suggestions for the improvement.

Daily Scrum Meetings

Stand up meeting. Time boxed held during the sprint. Power tool for collaboration, understanding
the transparency & continuous improvement within the scrum team. Regular inspecting the progress
we can identify the problems and impediments and adapt the plans and team can stay focused
aligned and responsive towards the change throughout the sprint.

Scrum master facilitates the sessions. Ensures that this adheres to the scrum framework. They help
the team through the process and collaboration and help remove the impediments. Also
encourages the meeting stay focused, timeboxed and productive.

Product owner is not required actively. Can participate and observe can provide any clarification.

Development team progress and challenges are the focus. They are the primary participants. They
display their progress, discuss their challenges, encourage one another, briefly describe what they
are working on and what they have done since previous daily scrum, what is intended to do before
the next scrum. Describe impediments they are aware of.

It consists of 15 minutes. Focused for team on the updates of development against sprint goal.
Coordinate with each other and make necessary dependencies.

Scrum Artifacts

Product Back log

Product backlog is one of the critical tool in scrum which gives the development team clear visibility ,
transparency and common understanding of what should be achieved. It is a hugely ordered list of
all the wanted features of all enhancements, bug fixing or any other items that are needed to build
up the prerequisits of product. This consists of single source of requirement from which the
development will pick and implement from the customers. These are used in user stories & are
short, straight forward & has description of the feature/funtionality as per the users
perspective.Template is as follows:

Product backlog grooming

In 2013, the phase grooming was replaced with Backlog refinement as per scrum guide. It is a
recurring activity in scrum where the product owner and development collaborate to review and
refine & prioritize the items in the product backlog. Goal is to ensure that the backlog is well
prepared, organized and ready for implementation of future sprints.

We may observe same type of requirement is given by stakeholders. We cannot give it to

developers, it wastes our time . We decide, filter (groom) on what has to be there in product
backlog.

Sprint Backlog
Sprint backlog is a list of activities which need to be completed during the sprint. It is created by the
development team and includes all the work items that the team commit to complete during the
sprint. It is created during the sprint planning ceremony & we may use this to guide the team
throughout the sprint.

User stories, tasks (each user story is broken down into smaller actionable tasks which refines the
work required to complete the story), task assignments, main goals, estimated efforts etc are in this
frame work.

Burndown chart

It is a visual tool to track the progress towards the goal. It shows the remaining work that we should
complete over the time.
03.10.2024

Assessment

04.10.2023

Predictive Approach

Upfront planning, strict and linear process. Document oriented.

Feasibility testing. Plan for schedule , quality, risk etc

Phase Gate
One phase to one phase there will be a phase gate. On approvals project can be carried out in
phases to avoid faults /discrepancies.

Process groups – Initiating, planning, executing, monitoring & control and delivery
Knowledge areas – These help us to understand & perform the job. Risk is a part of the project We
need some people to help us with this. These people would have completed their sigma certification
and experience in quality maintenance. Quality and risk are the two main areas. Basically, it is in 10
domains.
Processes: If we multiply the process groups with knowledge areas, we will get 50 processes. But we
have 49 processes. In order to complete one waterfall project we need to go through these 49
process.
Processes is similar to a standard procedure that we are going to prepare a cup of tea. Take the
requirement, based on the target audience we can select the criteria of raw materials, plan utensils
and tools, with experience and plan perform the job and we can serve tea.

Stake holders are the people, individual, the organization, who are going to affect or perceive to be
getting effected by the outcome of the project.
Integration is reconciliation with others. Identify the stakeholders. Develop a project management
plan.
Planning is the main part because our execution depends on it.
 ITTO – Input, tools, techniques, output
PMIS : Project management information system. EF’s and OPA’s shall be considered through out all
the phases in the project. When we use inputs, techniques and tools we generating a special unique
outputs.
Acceptance is depending on the requirements given and what is there present in the project.

Expert judgement is given by SME (subject matter experts). Project manager has to develop the
project charter with other stakeholders and clients. Data gathering is taking information by
interviews with focused group (same domain), brain storming. Interpersonal skills are required by
the project manager to resolve conflicts.

Facilitating the meeting to maintain time to give everyone an opportunity to speak, agenda
preparation, MOM and sharing the same with others. This leads to an output of project charter and
assumption log.

Project charter
Project charter is a standard template by the organization.

Project management plan is a detailed version of project charter.

Stake holder mapping should be done beforeth start of the project work. After identification we
need to analyse the stake holder

2D model

Power/interest grid (power /influence grid)

HP & LI – Have high authority and can make the changes inside the organization. Low interest might
be because too many projects running at the same time. Then CEO may not be able to follow the
project

HP & HI – Have high authority and can make the changes inside the organization. High interest is also
given to the project. CEO/CTO

LP & LI – SME’s will get to the project work for some time in the project. But they have to be
monitored

HI & LP – supplier, contractor, labor, supervisor have high interest but they have less power to make
changes.
3D model

Salien’s model

Power – influence / impact outcome.

Legitimacy _ right / justification

Urgency – importance and time sensitivity of the stakeholders claims

Dominant – High power, low legitimacy &low urgency – Functional managers -– high power and high
legitimacy but does not bother about urgency

Dormant – High power, low legitimacy & low urgency – No performance in work – steering
committee member, board of director member

Discretionary – Engaged but not in extreme levels – Assistant to VP/CEO.

Dependent – always depend on third person – testers, developers – High legitimacy, low power, low
urgency

Definitive – CEO, must be present – high power and high legitimacy low urgency

Dangerous – Community people – high power, high urgency low legitimacy

Demanding – Keeps their demands always – Local residents

07.10.2024