Today, I would like to write about another important set of attitudes and abilities that a good product owner (PO) should possess. As mentioned in the article I previously posted, PO doesn’t need to be technical to deepen his or her view and understanding of the role. Having a wider visibility and taking ownership on […]
You are browsing archives for
In part one, I wrote about the myth of existence and need of technical product owners. We left our hypothetical PO at a party answering few questions around his or her product. As we saw, the product owner needs to own the product knowledge base. If you are a PO and you wouldn’t be able […]
Today I want to write about the product owner (PO) or product manager (PM) role and not to provide a definition or list responsibilities but address a specific myth.
I am talking about the myth of the existence and the need of a technical PO.
I read an article where someone proposes to rename the role Scrum Master, following the latest trend of renaming everything that contains the word Master. We shouldn’t remove the word Master from our vocabulary. It is not the opposite of slave. Coming from latin magĭster (derives from magis «more») and means who knows a discipline […]
There many tools and checklists to verify wether your team is doing Scrum and how good (or or bad or ugly) is implementing it. If you are a Scrum Master, self-assessing the following statements from 1 (strongly disagree) to 5 (strongly agree) can help you to make a reality check and compare results with your […]
The daily scrum is the heartbeat of a scrum team.As Scrum is a compression algorithm for organizational and engineering best practices, this meeting is not a Scrum invention but it is considered an Agile best practice independently from the adopted framework. It is also known as StandUpMeeting (1993 Jim Coplien), “daily scrum” (1997 Ken Schwaber), […]
In my previous article “Spike 101” I introduced the concept of Spike and it’s general use in Agile. In that article we saw that: Spikes are investigation activities -e.g: research, design, investigation, exploration, prototyping- to gain the knowledge to solve a problem. As Scrum doesn’t prescribe any particular type for Backlog Items, it is up […]
Scrum is often described as a very prescriptive framework despite this is not the case. Take for example the various type of backlog items that we are used to deal with in our favourite backlog visualisation tool. Some work with Epics and User Stories only, others use a mix of Stories and Tasks, others add […]
As the end of the Sprint is approaching, usually in the last few hours before demo or even after, some team member decides to rush activities. What for the whole Sprint (1-4 weeks) and surely till “yesterday” wasn’t possible to complete in 1-2 days, suddenly can be finished in few hours, or it must absolutely […]