Agile and Scrum from a product manager's seat

Agile is often described as a methodology. It is closer to a mindset: deliver in small increments, learn from real feedback, change the plan when the evidence says so. Scrum is the most widely used framework for practising that mindset, and it works only when someone owns the product decisions inside it. The name comes from a 1986 Harvard Business Review article in which Hirotaka Takeuchi and Ikujiro Nonaka likened the best product teams to a rugby scrum, moving the ball forward together.

The product manager as Product Owner

• Owns the product backlog and decides its order, so the team always pulls the most valuable work next and the backlog never turns into a parking lot.
• Brings the why to sprint planning, answers questions early, and keeps new work out of a sprint once it has started.
• Puts working software in front of stakeholders at every sprint review.
• Turns what the retrospective surfaces into lasting changes to the process.

Cadence is a product decision

At arabam.com we put the web and mobile roadmap on a two-week sprint cadence, and time to market fell by about 40%. Most of that came from shorter feedback loops, and from the habit of finishing work before starting more.

Where it goes wrong

Without product ownership, the rituals produce busy teams and unchanged results. Scrum is a frame and nothing more. Someone has to put the product thinking into it, deliberately.