Talk of the town!

It was the talk of the town! We were involved in a product development and everyone in my team was talking about following Agile practices. Lots of ideas were flowing… ‘Rapid development’, ‘Scrum’, ‘Sprints’, ‘Regular feedback from client’, ‘Iterative deliveries’ and many more.

The product was delivered in releases as planned and of course in time. Partial Scrum was followed as the Agile practice. Don’t be furious!!! you scrum masters…

I agree there is nothing like ‘Partial Scrum’. It’s either Scrum or not. So what’s the heck is Scrum?

A view from 30,000 foot...

Scrum is an agile way to manage projects. Usually scrum is practiced in software development. It is a people-centric framework based on the values of honesty, openness, courage, respect, focus, trust, empowerment, and collaboration.

Scrum team consists of three roles:

• Product owner: The most empowered central point of product leadership.
• Scrum Master: Acts as a coach, providing process leadership, helping the Scrum team and the rest of the organization develop their own organization-specific Scrum approach.

• Development team: A cross function, diverse people who are responsible for designing, building, and testing the desired product.

We will discuss these roles in length later.

Why Scrum?

• Risk Mitigation due to faster feedback cycles.
• Reduced time-to-market hence improved ROI
• Improved stakeholders satisfaction
• Confidence to succeed in a complex product development

I’m sure one question must be bouncing in your mind, which kind of domain we should start with Scrum.

In next chapter we will find out among the below domains which are best suited with Scrum.

1. Complex domain
2. Complicated domain
3. Chaotic domain
4. Simple domain
5. Domain in Disorder
6. Interrupt-Driven Work