microcline + scrum   50

Why Scrum should basically just die in a fire
Overwrought article criticizing something the author is calling Scrum but seems to miss the point of agile.

0/10 , would not recommend.
scrum_criticism  scrum 
april 2016 by microcline
Who is on the Scrum Team?
Scrum team:

* A Product Owner
* A Scrum Development Team
* A Scrum Master

Scrum Development Team:

* cross functional of ~ 5-9 people who produce a potentially shippable product every sprint. Doers.
scrum  scrum_roles  product_owner_as_member_of_scrum_team 
september 2015 by microcline
Is the product owner on the Scrum team?
stick to Ken Schwaber’s terms: “Scrum Development Team” for the subset of the team that excludes the Product Owner, and “Scrum Team” for the dev team + Scrum Master + Product Owner. These are defined by _The Enterprise and Scrum_ (Schwaber 2007).
scrum  product_owner  scrum_roles  product_owner_as_member_of_scrum_team 
september 2015 by microcline
Technical stories : we don't need them
We don't need technical stories because technical work is either implied by truly doing to Done functional stories (tested, well factored) or it doesn't need doing yet.
scrum  agile  product_backlog  refactor  story_points  definition_of_done  user_stories 
september 2015 by microcline
Scrum is not Sufficient, and that's okay
Scrum as enough to allow a team to figure out what they need, not as everything the team needs.
scrum 
september 2015 by microcline
Kanban board within Scrum
"The Scrum that can be written about is not the true Scrum."
scrum  kanban  scrumban 
september 2015 by microcline
Heresy Against the Church of Agile Software Development
"I know that many Product Management bloggers believe that this problem is solved if you separate the market / customer-facing Product Manager role from the development-facing Product Owner. However, I remain unconvinced. How can the Product Owner gain the perspective to make the best product decisions without regular customer contact? "
product_management  scrum  agile  big_product_owner  product_owner 
august 2015 by microcline
Writing good user stories
What User Stories are, how to make them great, how to know if they are great, how to make them as small as possible.
user_stories  scrum  agile 
august 2015 by microcline
Diagram of Scrum product manager and Scrum master roles
Diagram showing which parts of traditional product manager and project manager roles fold into Scrum product owner and Scrum master roles (and what aspects of people telling other people what to do ideally just go away).
agile  scrum  product_owner  scrum_master  big_product_owner 
august 2015 by microcline
Summary of Agile Product Management with Scrum chapter 5 on Scrum meetings
Scrum is about having the right meetings with the right people with the right preparation and outcomes. And not having those other kinds of meetings.
scrum  sprint_planning  definition_of_done  scrum_standup  sprint_review  scrum_retrospective 
august 2015 by microcline
Summary of Agile Product Management with Scrum chapter 4 on release planning
Release planning: the team should do it. The product owner should drive it.
Mostly focused on the next release.
Which should be soon. With less scope and more quality.
And then you should plan and execute a release soon after that.
release_planning  scrum  product_owner 
august 2015 by microcline
Product owner responsibilities
Responsibilities of the product owner role:

"The product owner is the person who owns the product on behalf of the company."

Responsible for the success of the product.
scrum  product_owner  big_product_owner 
august 2015 by microcline
Product Owner = Product Manager + x
An agile product owner is a product manager plus "additional strategic duties including envisioning the product and managing the product roadmap as well as further tactical ones, such as collaborating with the development team throughout the development effort, writing user stories, carrying out release planning, and managing stakeholders."

With a reminder to execute the product owner role collaboratively and involving the Scrum team.
scrum  product_owner  product_management  big_product_owner 
august 2015 by microcline
Agile Product Management with Scrum summarized
Summary of Roman Pichler's book Agile Product Management with Scrum.

The product owner is responsible for the business value of the work of the Scrum team, and has corresponding authority over the product backlog and the product. The product owner says what needs doing, not how to do it, or how much it will take. This is a full time job.
product_owner  scrum 
august 2015 by microcline
Agile Product Management with Scrum : Preface : Summarized
Summary of preface to Roman Pichler's Agile Product Management with Scrum.
scrum  product_owner  big_product_owner 
august 2015 by microcline
Agile Product Management with Scrum : Chapter 1 : Summarized : Understanding the Product Owner role
My own blog post in which I summarize chapter 1 of Roman Pichler's Agile Product Management with Scrum, on understanding the product owner role.
scrum  product_owner  big_product_owner 
august 2015 by microcline
Avoiding Common Product Owner Mistakes
1. The Underpowered Product Owner
2. The Overworked Product Owner
3. The Partial Product Owner (aka small product owner?)
4. The Distant Product Owner
5. The Proxy Product Owner
6. The Product Owner Committee
scrum  product_owner  product_management  big_product_owner 
august 2015 by microcline
The Highlander Principle
There can only be one product owner for any given Scrum team.

"put one person in charge of the product; the individual leads the product development and owns the product on behalf of the company."
scrum  product_owner  big_product_owner 
august 2015 by microcline
Two Common Ways to Staff the Product Owner Role
Option 1: Customer plays the Product Owner role.
Option 2: A Customer Proxy fills the Product Owner role.
product_owner  product_management  scrum 
august 2015 by microcline
The Product Ownership Test
One truly owns a product if they have the right to say no.
product_management  product_owner  scrum  big_product_owner 
august 2015 by microcline
The Scrum Title "Product Owner" must die!
Argument is:

Scrum got it wrong: Product Owner role is way too big, with both tactical and strategic responsibilities. Instead, have a Backlog Manager, maybe called a "Technical Project Manager", responsible only for ongoing backlog prioritization and the necessary interaction with the development team to allow progress on the backlog aligned with needs of the business.

Everything else, from ROI to budgets to roadmap to vision, are all irrelevant, and are not necessary for the Backlog Manager role.
scrum  product_owner  product_management  product_backlog_manager 
august 2015 by microcline
The Scrum Product Owner as Backlog Manager
Instead of Product Owner, separate Product Manager and Backlog Manager, for ISV software after initial release. For custom software and ISV software pre-release, go with single Product Owner ala Scrum orthodoxy.

Term "Backlog Manager" to describe what elsewhere has been called "small product owner".

"For custom software vendors developing the first (or subsequent) versions of a product, there really is a single “Product Owner” that fits with Scrum orthodoxy. There is no “Product Manager” in this scenario representing a market of customers. This “Product Owner” is a representative of the single customer."

"For ISVs developing later releases of an off the shelf product, the backlog management responsibilities can be split from P&L / business responsibilities. The boundaries are set, and a “backlog manager” or “technical product manager” can work with the Product Manager to understand the goals of the next release and execute, while the product manager coordinates sales, channels, support, and other arms of the company. That backlog manager is most commonly known as a “Product Owner.”"
product_management  product_owner  scrum  product_backlog_manager 
august 2015 by microcline
Separating Product Owner and Product Manager roles and mapping their duties
Pursuing the "small product owner" model, a decomposition of duties between the Product Manager and the Product Owner.
scrum  product_owner  product_backlog_manager 
august 2015 by microcline
Story Points Must Die : A Spacetime adventure
Story points are project management theater, distracting from what's really important, which is producing good product.
estimation  project_management  story_points  agile  scrum 
march 2015 by microcline
The Product Owner Role at a Glance
concise overview of what it means to be Product Owner.

"I find it a mistake to primarily view the product owner as a product backlog manager and user story writer."
product_owner  agile  scrum 
february 2015 by microcline
Scrum Product Owner
Product Owner succinctly summarized.
product_owner  scrum  agile 
february 2015 by microcline
ThisAgileLife Ep 56 – Talking Out of Both Ends (Product Ownership)
1h podcast episode on Product Ownership.

Product owner as Steve Jobs? Or as Story sorter? Shields team?
Some annoying contempt for the Product Owner role in here.
scrum  agile  product_owner 
january 2015 by microcline
A few Product Owner questions and answers
On taking the Product Owner role seriously enough.
scrum  product_owner 
january 2015 by microcline
Galen's wandering thoughts on Done
Lots of good stuff in this post. Sprint goals, done-ness permeating your DNA, etc. I don't like the conflation of Definition of Done with Acceptance Criteria with Release Goals with... these are usefully separate concepts and smearing them together doesn't help. But his thoughts about these related topics are pretty good and worth reading.
scrum  definition_of_done 
january 2015 by microcline
Why Alistair Cockburn doesn't like Definition of Done
Definition of Done is about negotiating the distance between "done" and "potentially shippable". If the distance is zero, you don't need a Definition of Done. Knock it off with the Contract Negotiation and get back to producing genuinely Potentially Shippable software every single sprint. kthxbye.
alistair_cockburn  scrum  definition_of_done 
january 2015 by microcline
Definition of Done vs Conditions of Satisfaction
Mountain Goat Software's article on clarifying the relationship between Definition of Done and Conditions of Satisfaction.
definition_of_done  scrum 
january 2015 by microcline
Three Faces of Done
Three Faces of Done article on Scrum Breakfast blog.
scrum  definition_of_done 
january 2015 by microcline

Copy this bookmark:



description:


tags: