Project Management¶

Project Management is the planning, organization, securing, motivation and control of resources to successfully complete a project, while minimizing unproductive efforts

IDK¶

Every project should have the following

• Clear goal
• Project valuation: NPV

Project Management Models¶

Scrum¶

Keywords¶

Artifacts¶

Meetings¶

Time-boxing¶

Every thing should be assigned a particular max-duration

If time gets over, go ahead with the best solution possible rather than wasting more time trying to obtain the “perfect” solution

Clear goal & agendas¶

If you don’t know why exactly you are having a meeting, you shouldn’t be having it

Involved participants¶

If someone does not need to be there, don’t force them to attend

People¶

Ideally Product Owner and Scrum master should always be different, as each of their roles is very tiring as is.

Feature Size¶

Categorize features as S, M, L

IDK

• Discuss as an entire team whenever possible
• Each role should try to lend its perspective
• Listen & try to make sense of what others are saying
• Offer alternate solutions & point out problems
• Divide huge features into atomic features
• Everyone related to the decision should be there
• Everyone should agree on the feature size
• Don’t average out the opinions if someone says S & another person says L, don’t conclude it’s M
• Should not take too long. If you get stuck on a feature, put it aside & come back to it

Estimation¶

Get a clear view of project reality to make informed decisions to control project to hit targets. You need to identify what the team is capable of, not what you can/want to happen

---
title: Estimation
---

flowchart LR

subgraph pb[Product Backlog]
    direction LR
    f1[Feature 1]
    f2[Feature 2]
end

subgraph sb[Sprint Backlog]
    direction LR
    t1[Task 1]
    t2[Task 2]
end


pb --> Size --> Effort --> People --> Time --> sb

• Don’t estimate in “ideal work hours”
• Include breaks, distractions & meetings in the estimate

Need to know the __ of your estimates

• Uncertainty
• Accuracy
• Precision

You need to commit to a point estimate; don’t use the average of a range.

Estimation \(\ne\) Planning¶

Tracking Estimates¶

Get summary statistics of feature’s resources

Use this for better estimating in the future

Compare against feature size

Backlog to Tasklist¶

By breaking up story into tasks, you can understand all dependencies & potential overloading of individuals

Scrum Board¶

References¶

• Creating Video Games | MIT
• IIT Roorkee July 2018 | Project Management
• Agile Crash Course: Intro to Agile for Developers

Comments