About Lean, Agile, Scrum, Kanban, Waterfall

Eky Pradhana
2 min readOct 5, 2021

--

Wow, what a title!

In product development world bla bla bla bla there he is.. shut up! just to the point please.

With a good title comes great opening sentence. Whatever, let’s start!

Lean (in Product Development)

Lean is a philosophy in product development that revolve around cutting off the unnecessary works or efforts until we’re absolutely sure we need to do it for our users or customers.

One good example lately I’ve found is when my friend’s trying to build a new business. He tried to bridge the sellers in local (traditional) market with the customer, because he saw that during pandemic, many people don’t go to the traditional market so the sellers lose their profit.

What he did was, he just made an instagram account, uploaded the flyers consist of the service he offered, phone/whatsapp number, small text about the story behind why he did it, and start selling his service. He didn’t build a fancy mobile apps to acquire the customers to start this idea, although I know he is a great software developer as well. Pretty sure he will do it when the market is validated. This is the lean approach. So lean is really just about building something in an intelligent way where we’re not using the resources until we know we actually have to. And this way we safe a ton of money and time.

instagram : @tumbasno.id

Get the point, right? at least I do :) . Let’s jump to the next thing.

Agile

You can find some other definitions about what is agile out there, but this is as per my understanding. So what is agile? Agile is just a way of applying the lean mindset to software development. This is sort of project management framework for software development.

Agile is an iterative method to develop software where we do it batch by batch. We split the whole big requirement and group it into small batches, then do them in order to not wasting resources. So for example, let’s say we have about 15 features we need to build for our apps that we’re sure users will use it. If we do it in agile way, in the first phase probably we will only research and develop the first until five features that we think are most important. Then we release them and waiting for user feedbacks before we go to the next phase to do the remaining features.

I also apply the agile method in writing this post. So I will split this story become some parts (maybe 2, or more?) because I want to release this post faster and hear the feedback.

No, that’s because I’m tired to arrange the words actually. It is 1:27 AM and I miss my bed.

Keep sharing small things ;)

--

--

Eky Pradhana

Writing as an act of giving back and paying it forward. Let's sparking change, and fostering a culture of compassion!