1. Project?
1.1. Unique Deliverable
1.2. Defined Timeframe
1.3. Budget
2. Project manager
2.1. Job
2.1.1. **Get the job done within the timeline**
2.1.2. Planning & Organizing
2.1.3. Budgeting
2.1.4. Managing Task
2.1.5. Controling the cost & other factors
2.2. Skills Required
2.2.1. Strategic planner
2.2.2. Strong organization
2.2.3. Delegation
2.2.4. Prioritization
2.2.5. Action-Oriented / **Enable** decision making
2.2.6. Communication Conflict resolution & Escalation Manage team/people
2.2.6.1. Understanding Team's motivation
2.2.6.2. Communicating what the success will look like, will motivate them For ex: Telling the team how the bridge will look like and how many ppl will use it and how it will save 10000's of hours for commuters will motivate them when you have just started to build
2.2.6.3. Influencing *without* **authority**
2.2.7. Flexibility & Handling ambiguity
2.2.7.1. External Constraints
2.2.7.2. Plan - Risk & Challenges
2.2.7.3. Add "Float/Slack" in schedule
2.3. Impact
2.3.1. Customer/Stakeholder centric
2.3.2. Bulding a great team
2.3.3. Fostering relationship & communications
2.3.4. Innovate - Breaking barriers
2.3.5. Managing project
3. Project Lifecycle
3.1. Initiation of the project 1 (Stakeholder/Client)
3.1.1. Intro with stakeholders/clients
3.1.2. Understanding the mission and vision of the company and the project
3.1.3. Understand the goal and unique deliverables
3.1.4. Timline and Budget if any
3.1.5. Metrics for success
3.1.6. Bonus: What is the need of this project/How will this impact their company
3.1.7. Document everything
3.2. Initiation of the project 2 (Internal team)
3.2.1. Do we have the resource, technology, capacity, venue, talent required?
3.2.2. Is the timeline and budget doable?
3.2.3. Create project proposal and get approval
3.3. Planning
3.3.1. Assemble the team Define the roles and responsiblities
3.3.2. Breakdown the goals and deliverables into **milestones** and furhter into tasks
3.3.3. Create item wise budget
3.3.4. Set *schedules* for tasks and milestones
3.3.5. Set communication channels & modes, establish escalation paths
3.3.6. **Account for risk & challenges**
3.3.7. Create a plan B
3.4. Execution & completion of the task
3.4.1. Assign and prioritize the tasks
3.4.2. Monitor the progress, set daily, weekly or more frequent huddles
3.4.3. Remove obstacles / Enable decision making by putting > 2 right people on a call
3.4.4. Consider any **changes** to budget/plan/schedule/resourece
3.4.5. Motivate the team & keep the team aware of progress
3.4.6. Improve the process if any weakness found
3.4.7. Keep an eye on quality
3.4.8. Call out any risks/delays. Keep the communication open to stakeholders
3.5. Closing the project
3.5.1. Ensure all tasks are completed, Submit the documentations, Handover to support or other team (if req)
3.5.2. Get a confirmation from stakeholders that project is accepatable & the goals are met
3.5.3. Retrospect & check the success metrics. What worked and what did not work
3.5.4. Communicate the project completion to the world and *celebrate *
4. Interview Prep
4.1. Finding the skiils
4.2. STAR methodolgy for answering questions
5. Methodology
5.1. Linear
5.1.1. Waterfall
5.1.1.1. When to use
5.1.1.1.1. End goals are fixed and cannot change
5.1.1.1.2. Stakeholders knows exactly what they want
5.1.1.1.3. You know exactly how to do it and know everything
5.1.1.1.4. New task can start only when the previous task is completed
5.1.1.1.5. Changes are very expensive or not possible
5.1.1.1.6. Phases are clearly defined
5.2. Iterative
5.2.1. Agile
5.2.1.1. When to use
5.2.1.1.1. End goal is an idea, rather than concrete plan
5.2.1.1.2. You don't have clear pathway to the goal / You don't know everything
5.2.1.1.3. Plan can change based on initial feedback from customer/stakeholder
5.2.1.1.4. Stakeholders need want to get involved in each stage
5.2.1.1.5. When change is definite / Flexible
5.2.1.1.6. Get something done quicker by doing task in non-orderly way
5.2.1.1.7. Team's are responsible for their own work
5.2.1.2. How it works
5.2.1.2.1. Task from different lifecycle can be done togehter
5.2.1.2.2. Uses scrum - **sprints** and small milestones to complete work
5.3. Process Improvement
5.3.1. Lean Six Sigma
5.3.1.1. When to use
5.3.1.1.1. Make things which already exist - **better**
5.3.1.1.2. Improve quality
5.3.1.1.3. Improve process / Efficiency
5.3.1.1.4. Reduce wastage/Save money
5.3.1.2. How it works
5.3.1.2.1. D : Define the goal, problem, issue
5.3.1.2.2. M : Measure - understanding the current process and where to find the problem is and what to measure
5.3.1.2.3. A : Analyze using the data received and processes understood
5.3.1.2.4. I : Improve based on the analyzation by putting up processes
5.3.1.2.5. C : Control the process which you have set-up, and put guard rails so it does go haywire like before
6. Tools
6.1. Planning and scheduling software (templates, workflows, calendars)
6.2. Colloboration tools (Mails, slack)
6.3. Documentation (doc, files, path)
6.4. QA tools (evaluation, productivity tracker, reports)
7. Organization
7.1. Structure
7.1.1. Classic/Top Down
7.1.1.1. Resource allocation
7.1.1.2. Limited Authority
7.1.2. Matrix
7.1.2.1. More authority
7.1.2.2. Faster Delivery
7.1.2.3. Resource Sharing
7.1.2.4. Role Ambiguity
7.1.2.5. Negotiation Skills Required
7.1.3. PMO
7.1.3.1. Align projects with companies vision
7.1.3.2. Select projects
7.1.3.3. Connect multiple projects
7.1.3.4. Set best practices
7.1.3.5. Resource allocation
7.1.3.6. Documentation, tools
7.2. Culture
7.2.1. Companies identity/personality
7.2.2. Value
7.2.3. Mission
8. MIscellaneous
8.1. Change Management
8.1.1. Process of delivering **completed** project and getting it **adopted** by people People here can be companies employees, end users, top management, sales/marketing team
8.1.2. 5 steps before normalcy by humans
8.1.2.1. Resistance
8.1.2.2. Letting-go
8.1.2.3. Acceptance
8.1.2.4. Insight
8.1.2.5. Practice
8.1.3. 3 Important questions
8.1.3.1. Who get's affected
8.1.3.2. How do they get affected
8.1.3.3. How to help
8.1.4. How to plan for change? Even with planned change there will be disturbance, but the chaos will be better than non-planned change
8.1.4.1. Communicate the plan to change
8.1.4.2. Tell them the bigger picture
8.1.4.3. Motivate them by telling how this will make their life better. Evernthough it will be difficult in the beginning
8.1.4.4. Show them the plan, ask for feedback
8.1.4.5. Make the release step-by-step Do not release everything at once
9. Prioritize requirement
9.1. MoSCoW
9.1.1. **Must have** Critical/Priority requirements. Must have for success of the project Ex: Message sending functionality in the messaging app
9.1.2. **Should have** Imprortant feature that add value Ex: Group chat
9.1.3. **Could have** Nice to have Ex: Emoji reaction for messages
9.1.4. **Won't have** Out of scope for now Ex: Audio call.
9.2. Value vs Complexity matrix
9.2.1. High value, low complexity
9.2.2. High value, high complexity
9.2.3. Low value, low complexity
9.2.4. Low value, high complexity
9.3. **Kano model** Requirements based on **cusotmer satisfaction**
9.3.1. **Basic needs** These are the requirements which customers thinks are minimum. - Failing to meet these leads to dissatisfaction. - Meeting them *doesn’t* increase satisfaction.
9.3.2. **Performance needs** - Customer satisfaction increases. - The more better, the more happy customers
9.3.3. **Excitement needs** - Unexpected feature that delight customers
9.3.4. **Indifferent needs** - Don’t have any significant impact on customer satisfaction.
9.3.5. **Reverse needs** - Feature that reduces customer satisfaction and needs to be removed
10. Job **Search**
10.1. Resume
10.2. Job search
11. Project LifeCylce
11.1. Initiation
11.1.1. Goals
11.1.1.1. SMART
11.1.1.1.1. Specific
11.1.1.1.2. Measurable
11.1.1.1.3. Attainable
11.1.1.1.4. Relevant
11.1.1.1.5. Time-bound
11.1.1.1.6. Example
11.1.1.2. OKR
11.1.1.2.1. Objective
11.1.1.2.2. Key Result
11.1.2. Scope
11.1.2.1. How to know the scope?
11.1.2.1.1. Talk to the stakeholders and ask them what they have in mind
11.1.2.1.2. Do research based on the goals
11.1.2.2. Questions to ask to define the scope
11.1.2.2.1. **How do you want to achieve the goal?** For increasing revenue there are 100 ways, how and what do you want to do? Example: As a company selling plants, you can borrow money gamble and increase the revenue. Or you can create a new plant line, create a website, market and sell it.
11.1.2.2.2. What does stakeholder have in mind?
11.1.2.2.3. Who approves the final result?
11.1.2.2.4. Who will be using the service?
11.1.2.2.5. Who should we deliver the project to?
11.1.2.2.6. What is the project expected to achieve?
11.1.2.2.7. Example: For Pet Pal project let's say to achieve the goal, the customer had to purchase the plants from online or print catlog. Scope will be - Research the market to understand the needs for creating a new product - Find a merchant that will deliver this new product - Create a website suitable for tablet with shopping cart, online payment, search functionality. - The size and thickness of the paper will be A4 and 250gsm and the color of the print will be B/W
11.1.2.3. In-scope
11.1.2.3.1. What is **included** in the project which contribute to the project goal
11.1.2.4. Out-of-scope
11.1.2.4.1. What is **excluded** in the project which contribute to the project goal
11.1.2.4.2. Example: Pet Pal which is suppose to deliver small plants, suddenly if the sales team tell you to start delivering big plants then it is out-of-scope
11.1.2.5. Scope Creep
11.1.2.5.1. Changes, growth or un-controlled factors that changes the scope after the project has begin
11.1.2.6. Managing the scope
11.1.2.6.1. Scope and goal go hand-in-hand, If you change the scope goal will change Similarly, if you change the goal scope will change
11.1.2.6.2. Solution to scope creep
11.1.2.6.3. How to trade-off
11.1.2.7. Remember any change to the scope, internal or external should be informed to the stakeholder and the team
11.1.3. Deliverables
11.1.3.1. Products/Services you need to deliver for completing the project Tanglible/Intangnible outcome
11.1.3.2. Example: For plan pal, Submitting the newly designed website Deliering 1000 plants to 100 customers Completing marketing campaign These are all deliverables
11.1.4. Success Criteria
11.1.4.1. Intro
11.1.4.1.1. **Launch** Delivering the final product to the users and stakeholders ----------------------------------------------
11.1.4.1.2. **Landing** Measuring the success of the project using criteria established in the beginning ----------------------------------------------
11.1.4.1.3. **Adoption** How customers are using the product or services without any issues ----------------------------------------------
11.1.4.1.4. **Engagement** How ofter customer interact over a time ----------------------------------------------
11.1.4.2. What?
11.1.4.2.1. Tells us whether or not a project is successfull
11.1.4.2.2. Standard by which the project is judged
11.1.4.3. How to determine?
11.1.4.3.1. Measurable component of the goal M from SMART and KR from the OKR
11.1.4.3.2. Quality of the product/service
11.1.4.3.3. Does it fulfill the need of the customer
11.1.4.4. Important things to consider
11.1.4.4.1. Once the success criteria is defined, get it signed off from the stakeholder
11.1.4.4.2. After the project is completed, use the document to validate if everything has been completed
11.1.4.5. How to measure?
11.1.4.5.1. Google follows a 0.0 - 1.0 approach for setting OKRs. Typically, they set ambitious goals with the aim of achieving 0.7-0.8 of the target, considering this range to be a good outcome. If they reach 1.0, it suggests the goal was too easy. Sample scorecard - https://tinyurl.com/yeynbz5s
11.1.5. Project Roles & Stakeholder Analysis
11.1.5.1. Project Roles
11.1.5.1.1. Project Sponsor
11.1.5.1.2. Team Members
11.1.5.1.3. Customer
11.1.5.1.4. Users
11.1.5.1.5. Stakeholders
11.1.5.1.6. Project Manager
11.1.5.2. Stakeholders Analysis
11.1.5.2.1. Why?
11.1.5.2.2. Preparation
11.1.5.2.3. Analysis
11.1.6. Resource
11.1.6.1. People
11.1.6.1.1. Team
11.1.6.1.2. Roles & Responsibilities
11.1.6.2. Budget
11.1.6.3. Materials
11.1.7. Cost benefit analysis / ROI
11.1.8. Documentation
11.1.8.1. Project Proposal
11.1.8.1.1. Documentation used to persuade the project sponsor to initiate the project
11.1.8.1.2. This is done by senior team and before the project is assinged to the PM
11.1.8.1.3. Mode could be formal document, an email or a presentation
11.1.8.2. Project Charter
11.1.8.2.1. Formal document outlining everything fromExecutive summary, goal, scope, why we are doing it (business case) deliverable, wteam, budget, cost benefit anaylysis and success criteria.
11.1.8.2.2. Example
11.1.8.2.3. Example Plan pal