Product Development Methodologies | Product Management

Lean Product Development

Lean product developmen is a philosophy to make more effective the way of building products. Lean product development using just necessery things in the beggining. When we building a product, we use just necessary things like main things that make us product works.

Example: Food Delivery App

Normally, you would hire drivers, buy a cell phone number, and build the actual app

The Lean way of doing this is doing everything yourself in the beginning, trying to get as far as you can by using least amount of resources

Agile Product Development

So Agile framework is the way applying the Lean philosophy to software teams, products generally software development.

In the Agile framework, we group things into small batches and do them one by one, in order to not waste resources

Example: Researching the most important 2–5 features of a product instead of developing all of them.

Agile Methodologies

There are two Agile development methodologies: Scrum and Kanban.

1. Scrum Product Development

There are two Agile development methodologies: Scrum and Kanban

Scrum is the most common and it works like this:

The sprint planning meeting

• You take the most important features from the top of your product backlog and you move it to the sprint backlog
• You talk about what needs to be done in order to implement it
• You put the work into a project management software, and into tickets

The start of the developing process

• A sprint usually takes 2 weeks
• your team works on the tickets by taking them off the top of the spring backlog and moving them to “in progress” and then to “Done”
• the end of the 2 weeks, you sould have completed everyting in the sprint backlog; if not, they go into the next sptint

Standup meetings

• Daily meetings held in the mornings
• people remain standing during the meeting, in order for it to remain brief and concise
• Every team member makes a summary of their workk

Retrospective meetings

• You meet with your team at the end of each sprint
• You talk about 3 main things: the last sprint, what went well and what didn’t

2. Kanban Product Development

• A Kanban board has columns with cards that you can move from one column to another, to reflect the state of the item “to do, “ın progress” or “done”
• How many items can be in each particular state is up to you or your team to decide
• Kanban doesn’t use sprints
• there is no sprint backlog, only the product backlog itself
• the team works on their ticket, they move it do done, and they take the next task off the top of the product backlog
• Kanban doesn’t prescribe any particular meetings types
• Kanban is more relaxed, but it makes it more difficult to evaluate how much time it’s going to take to develop items

Waterfall Product Development

• The waterfall framework is the opposite of Agile
• In the waterfall framework, we take all the features of a product and develop them all at the same time
• Doing things in the waterfall way is risker
• It’s much harder to adapt to make the market feedback after you’ve already built everything