What do we do during planning?

1) Understanding requirements.

2) Finalise scope

* All estimation and planning are done after requirements are understood and scope is finalised.

Estimation of resources, cost, duration

If we miss out any requirements?

It will lead to rework, delays, cost overruns, and quality problems.

3) When the scope is finalised, it called scope baseline.

Change Control Procedure.

Most of the difficulties, problems, and challenges that we face during execution is due to poor planning.

Planning means creating scope baseline, schedule baseline, cost baselines. Planning means identifying all those
factors which may lead to failure.

Planning also means developing actions plans to avoid or minimise those factors which will lead to failure.

Why organizations do projects?

Because there is a need.

From how many areas Need for a project may emerge?

Organizational need or Business Need:

1) Need for Growth of the company

2) Need for increasing Market share

3) Need for increasing ROI

Question: You have recently been assigned as project manager of a large Telecom Project. You want to know
which project management methodology is relevant to the project. Which document would you consult?

Answer: Business Case

Business case defines which approach is suitable for the project.

•Traditional Waterfall Approach, or Agile Approach, or Hybrid Approach. Remember this point!

Construction project = Traditional Waterfall approach

Software development project - Agile approach

Design and launch of new mobile = Hybrid approach

Question: What are project management business documents and why do we need them?

Answer: Business case and benefits management plan together are termed as Project Management
Business Documents. We need them for selecting a project and authorizing through the project
charter.

Traditional Waterfall Approach or Predictive Life Cycle

1) Requirements are well defined, agreed and approved. Detailed project plan is made. Execution follows
the plan.
2) Changes are discouraged and allowed after approval through the change control procedure.
3) Project manager assigns work to the team members.
4) Project manager directs and controls the team.
5) Development is often done sequentially, and delivery is made at the end of the project. There are no
incremental deliveries.
6) Example: Construction Projects

Agile Approach or Adaptive Life cycle

1) In agile, a project divided into short periods of development (say 2 to 4 weeks) which are called Sprints
or Iterations.
2) Requirements are defined Sprint-by-Sprint, not for the entire project.
3) Changes are welcome.
4) There is no control procedure or change control board in agile.
5) Project manager is only a Servant Leader with no management authority over the team.
6) In agile, the team is self-organizing and self-managing.
7) The team members decide who will do what among themselves.
8) Project manager does not assign any work.
9) There are incremental deliveries to provide early business advantage to the customer.
10) Example: Software Development Projects

Project Charter
Question: You have been assigned as a new project manager for a Multi-site Construction project where some
work has already been done by the earlier project manager.

You want to know overall project risk. Which document would help you with this information?

Answer: Project Charter

1 ques on Stakeholder Map: Power/Interest Grid

It will help us decide how attention we should pay to each stakeholders.

Question: What is scope creep?

Answer: Uncontrolled expansion in scope is called scope creep.

Scope creep leads to rework, delays, cost overrun, quality problems. We should identify factors that lead to
scope creep and try to eliminate these factors.

At the top level of WBS, we have phases or major deliverables.

At the bottom level of WBS, we have Work Packages. Work Packages are assigned to the team members.

3-4 questions on team charter

Team charter is an agreement among the team members on how they work together as a good team.

Team charter contains:

1) Team values - respect each other, compliment each other, respect diversity and culture.
2) Operating guidelines - Communication guidelines,
Decision-making guidelines,
Conflict resolution guidelines, and ,
Meeting management guidelines.

3) Acceptable and unacceptable behaviour

More extensive involvement of stakeholder means provide demo of work completed, take
feedback, and ask if there are changes in the requirements.
This will help timely incorporation of change before it is too late.
This will also ensure satisfaction of stakeholders.
This will increase chances of success.

15-05-2022
AGILE
A software development project of one year will be divided into 26 Sprints (52/2).
Requirements are defined Sprint-by-Sprint.
Requirements are not defined for the entire project.
Agile uses Rolling Wave Planning.
 Rolling wave planning – Rolling Wave Planning means more detailing of the work we are going
to perform in NEAR future than the work we are going to perform far in future.
In agile, requirements evolve over a period of time. Therefore, changes are welcome based on
the feedback of the customer and the business value of the changes.
In agile, requirements are recorded in document called Product Backlog.
All agile methodologies are based on 4 Values of Agile Manifesto and 12 Agile Principles.
1- Individuals and interactions over processes and tools.
2- Working software over comprehensive documentation.
3- Customer collaboration over contract negotiation.
4- Responding to change over following a plan.

1 question on exam : Working software is the primary measure of progress.

Agile project are High-uncertainty and High-variability projects.

In agile methodology, we have Agile Roles, Agile Ceremonies, and Agile Artifacts.

Agile Roles:

•Product Owner

•Development Team

•SrumMaster

Agile Ceremonies:

•Sprint Planning

•Daily Standup or Daily Scrum

 •Sprint Review

•Sprint Retrospective

Agile Artifacts:

 Product Backlog
 Sprint Backlog
 Definition of Done “DoD”
 Burndown chart, Kanban or Task Board
 Product increment
Lot of questions on Agile roles

Total 180 questions in exam

About 60 ques on agile roles
which includes about 40 ques on Servant Leadership

In agile, requirements are recorded in document called Product Backlog.

In the Product Backlog, requirements are organized according to the priority.

Requirements are written in the format of User Stories.

Product Owner is responsible for creating the product backlog, prioritizing the product
backlog items.

Question : Q: Who can decide priority of Product Backlog Items (PBIs)?

Answer : Product Owner (not Scrum Mater, not development team).

Q: Who will do Sprint Review?

Answer : Only the product Owner has the authority to review the work completed during the
sprint and provide acceptance.
In agile, project manager may be called Scrum Master or Agile Coach.

Agile Thumb Rules

2. If it is necessary to change a team member, then do not do it during the sprint. You can do
it between sprints.
Q: In agile, who does estimation?
A: Development Team
Note: Product Owner or Scrum Master are not allowed to do it. Only team will do estimation.

Q: Wo will do velocity prediction?

Scrum Master facilitates all agile ceremonies.

In Sprint Planning Meeting, the Product Owner explains before the team what requirements
are to be completed in the sprint.
After that, the development team will to do estimation on the basis of their experience and
the complexity of work.
And then, make commitment to the Product Owner. This commitment becomes Sprint Goal.
Example: Suppose product wants 4 requirements to be completed in the sprint. Product
owners explain these 4 requirements to the team.
The team members will do estimation whether they will be able to complete them in the
sprint.
If they find yes, then they commit to product that they will complete these 4 requirements in
the sprint.
In case, team finds after estimation, that they can complete only 3 requirements in the sprint,
not 4.
Then team will make commitment for completing 3 which will become sprint goal.

Agile Thumb Rule:

Product can say what is required to be done. The team will decide how much possible to be
done in a sprint. Product owner cannot impose.

Agile Thumb Rule:

Sprint Backlog is created by the team, and it is updated by the team as the work progresses.
Nobody else is allowed to touch it.

In agile, estimation is done in story points.

Sprint Backlog
1. Sprint Backlog is created the team ONLY.
2. In the Sprint Backlog, the team will enter those requirements / or product backlog
items/ or user stories which have been committed by the team for completing in the
sprint.
3. Team will define tasks required for completing each user story.

Sprint Dashboard or Task Dashboard or Kanban Board is used to show status and progress.

Kanban board

 To Do
 Work-in-Progress (WIP)
 Done

Burndown Chart

4. When Actual line of burndown (red) is horizontal instead of burning down.

Time is passing but no work is happening.

5. When Actual line of burndown (red) moves up instead of burning down.

New scope has been added.

SCALING AGILE or Scaling Scrum

We can do large projects in agile mode by having multiple teams.

When we scalup Agile or Scrum by having multiple teams, we need to conduct Scrum of
Scrums meeting to coordinate and manage the work of these multiple teams.

Fibonacci sequence
Fibonacci sequence is made after observation in nature, on how the sizes grow in nature, such
as how the sizes of branches become bigger.

In agile, team is self-organizing and self-managing.

Team is empowered to:

1) Do estimation,

2) Decide who will do what,

3) Decide how the work will be done,

4) Take technical decisions

So, the requires decision-making tools.

In agile, PMO plays an advisory role only. PMO can not monitor and control status and
progress of agile projects. PMO can not direct agile team.

PMO can only share guidelines.

DoR (Definition of Ready)

1) Product is responsible for ensuring that user stories, before presenting to the team for
development, are clear and complete, so that team can work on them. This means these user
stories should meet Definition of Ready.

2) If the use stories are ambiguous, the team can not work on them, and product owner is at
fault.

Sequence of Test-driven Development: Write test, Write code, Refactor

In agile there are two to do scheduling and manage work: In Iteration-based scheduling.

In agile there are two ways to do scheduling and manage work:

1) Iteration-based scheduling

In Iteration-based scheduling, the project is divided into sprints or iterations. These are time
boxed to 2 to weeks to 4 weeks.

Product backlog items are estimated by the team.

Product backlog is managed by the product owner. Sprint backlog is managed by the team.

There are 4 Scrum or Agile ceremonies: a) Sprint Planning, Daily Standup, Sprint Review, and
Sprint Retrospective.

Sprint = Iteration

Here, scrum master owns the process and ensure that scrum process is followed. Scrum
methodology is iteration-based.

2) Flow-based scheduling

In Flow-based scheduling, Kanban is used.

All the tasks that ARE to be done are placed under TO DO column.

Team pulls the work into next column which is called WORK-IN PRPGRESS (WIP), based the
rate at which team comperes the work (throughput).

Here, team owns the process not scrum master. Kanban is Flow-based.
Cycle time= Time taken to complete the work

Scope creep means that we have finalised the scope and after there is uncontrolled expansion
in scope.

In agile, scope is not finalised, because requirements are not defined at the start of the
project.

So, the term scope creep does not apply to agile. Agile welcomes changes.

Bottom-up estimation means estimating the cost or resources for each work package of the
WBS and then summing up to know cost estimate or resource estimate for each phase and
the entire project.

Since WBS is not made in agile, the Bottom-up estimation is not possible.