Week 2 Notes

Leadership = Accountability, responsibility, Look and act like a leader, Body language is important 

Management = working with people

Core Concept 1: 

Scope - Describes what the end product will be 

Schedule - Is the time frame that You will have to complete your project 

Budget (Cost) - The money that you can spend on your project

Manage expectations with the investors as altering any of these things will impact the quality of the final product. 

Quality = Time + Cost

Core Concept 2:

In scope are things that will be discussed, and are things we will do 

Out of scope ideas will also be discussed so their is a understanding between the investors and you. 

Scope management -  is the process whereby the outputs, outcomes and benefits are identified, defined and controlled (PMBOK, 7th Edition)

As a product manager you have to manage expectations and the things that you are gonna get in the future to clients, stakeholders and anyone else involved in the project. 

Calibrate the temperature of excitement between the client and your group, work with them and communicate regularly. 

Bad news (Obfuscation) - Never hide this from stakeholders or the client as it could do terrible damage to the quality of the product. (Plus no one will trust you in the future.)

Core concept 3:

Learn how to say "no"

Starting a project:

Kick Off - The first meeting that utilises problem solving, in this you will discuss the "why" and the "what" and the feasibility and viability 

Feasibility- doable / possible

viable - £? / is it profitable, do we have the financial budget for it

Baseline/ reline - telling everyone the exact details of the product and how they are going to help

Communication is key - check in with people until your certain they are doing the right thing/ daily checks/ also build a relationship with them so it doesn't seem like a standoff

Approaches:

BDUF - Big design up front

The waterfall project/ cascade project: - Each phase of this project is clearly lined out and allows for each step to be completed before the next phase is started.

However - If the "why" has changed halfway through the project it may be hard to make this fit with the product.

-You could stop, 

- Pivot the aim and goal,

- or manage backtracking 

This technique doesn't work well if the product is an app or website as they are ever changing and would need customer inclusion

This technique also has very little customer communication

 

Agile projects:

EDUF - Enough Design up front 

- The ability to move quickly and easily 

- Relating to or denoting a method of product management, used especially for software development. 

- It welcomes change as you build the final product in short burst which are shown back to the client regularly 

https://agilemanifesto.org/iso/en/principles.html 

"The agile Manifesto that explains what key principles are used in this technique"

Each methods are suited to particular types of projects

Both methods use the same iron triangle principles. 

Task/ Birthday cake:

• What type of cake will you bake?

-Victoria sponge 2 layer 

• How long will this take to deliver? 

-1 day 

• How much will it cost in total? 

-£22 for ingredients 

-£35 for equipment 

-£15/hr for kitchen 

-£10 for delivery box