#productbacklogrefinement — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #productbacklogrefinement, aggregated by home.social.
-
Bill Wake's 2003 article explaining the INVEST acronym is STILL among the best guidance ever written for writing effective #productbacklog items.
Thank you, Bill. 🖖
Original article: https://xp123.com/invest-in-good-stories-and-smart-tasks/
-
Bill Wake's 2003 article explaining the INVEST acronym is STILL among the best guidance ever written for writing effective #productbacklog items.
Thank you, Bill. 🖖
Original article: https://xp123.com/invest-in-good-stories-and-smart-tasks/
-
Bill Wake's 2003 article explaining the INVEST acronym is STILL among the best guidance ever written for writing effective #productbacklog items.
Thank you, Bill. 🖖
Original article: https://xp123.com/invest-in-good-stories-and-smart-tasks/
-
Bill Wake's 2003 article explaining the INVEST acronym is STILL among the best guidance ever written for writing effective #productbacklog items.
Thank you, Bill. 🖖
Original article: https://xp123.com/invest-in-good-stories-and-smart-tasks/
-
Bill Wake's 2003 article explaining the INVEST acronym is STILL among the best guidance ever written for writing effective #productbacklog items.
Thank you, Bill. 🖖
Original article: https://xp123.com/invest-in-good-stories-and-smart-tasks/
-
Bill Wake's 2003 article explaining the INVEST acronym is STILL among the best guidance ever written for writing effective #productbacklog items.
Thank you, Bill. 🖖
Original article: https://xp123.com/invest-in-good-stories-and-smart-tasks/
-
Bill Wake's 2003 article explaining the INVEST acronym is STILL among the best guidance ever written for writing effective #productbacklog items.
Thank you, Bill. 🖖
Original article: https://xp123.com/invest-in-good-stories-and-smart-tasks/
-
Bill Wake's 2003 article explaining the INVEST acronym is STILL among the best guidance ever written for writing effective #productbacklog items.
Thank you, Bill. 🖖
Original article: https://xp123.com/invest-in-good-stories-and-smart-tasks/
-
@billseitz @bernie @anil Ok. Background check the three of us help organizations with Scrum, Kanban, DevOps etc.
FWIW I know and love (platonic) Ron. I've read that post, many times. One could argue our 3% Better Approach is an antidote to Ron's point.
I'm open to another another angle. Should I write about #ProductBacklogRefinement for Kanban? How does it differ from Scrum land?
-
Their item still spent a long time sitting in a queue and it doesn't matter what the queue was.
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
A ThreePercentBetter Production In partnership with @bernie and @anil
3/3 Bad Estimate
-
Their item still spent a long time sitting in a queue and it doesn't matter what the queue was.
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
A ThreePercentBetter Production In partnership with @bernie and @anil
3/3 Bad Estimate
-
Their item still spent a long time sitting in a queue and it doesn't matter what the queue was.
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
A ThreePercentBetter Production In partnership with @bernie and @anil
3/3 Bad Estimate
-
Their item still spent a long time sitting in a queue and it doesn't matter what the queue was.
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
A ThreePercentBetter Production In partnership with @bernie and @anil
3/3 Bad Estimate
-
Their item still spent a long time sitting in a queue and it doesn't matter what the queue was.
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
A ThreePercentBetter Production In partnership with @bernie and @anil
3/3 Bad Estimate
-
Another reason to dislike Ready, it encourages a local optimization. It makes the Scrum Team look good, by improving their cycle time, without necessarily improving things for the client. Example a Definition of Ready holds up a feature for 4+ weeks will requirements are being gathered. Now the Scrum Team looks good when they work on the item their cycle time will be low. However the customer isn't any happier.
-
Another reason to dislike Ready, it encourages a local optimization. It makes the Scrum Team look good, by improving their cycle time, without necessarily improving things for the client. Example a Definition of Ready holds up a feature for 4+ weeks will requirements are being gathered. Now the Scrum Team looks good when they work on the item their cycle time will be low. However the customer isn't any happier.
-
Another reason to dislike Ready, it encourages a local optimization. It makes the Scrum Team look good, by improving their cycle time, without necessarily improving things for the client. Example a Definition of Ready holds up a feature for 4+ weeks will requirements are being gathered. Now the Scrum Team looks good when they work on the item their cycle time will be low. However the customer isn't any happier.
-
Another reason to dislike Ready, it encourages a local optimization. It makes the Scrum Team look good, by improving their cycle time, without necessarily improving things for the client. Example a Definition of Ready holds up a feature for 4+ weeks will requirements are being gathered. Now the Scrum Team looks good when they work on the item their cycle time will be low. However the customer isn't any happier.
-
Another reason to dislike Ready, it encourages a local optimization. It makes the Scrum Team look good, by improving their cycle time, without necessarily improving things for the client. Example a Definition of Ready holds up a feature for 4+ weeks will requirements are being gathered. Now the Scrum Team looks good when they work on the item their cycle time will be low. However the customer isn't any happier.
-
#DefinitionOfReady
Under some circumstances a Definition of Ready helps a Scrum (or Kanban Team) ensure their Product Backlog Items are well thought out. This means nothing is consider for Sprint work that would get probably get stuck.I've already pointed out that ready encourages mini-waterfall/gate system.
-
#DefinitionOfReady
Under some circumstances a Definition of Ready helps a Scrum (or Kanban Team) ensure their Product Backlog Items are well thought out. This means nothing is consider for Sprint work that would get probably get stuck.I've already pointed out that ready encourages mini-waterfall/gate system.
-
#DefinitionOfReady
Under some circumstances a Definition of Ready helps a Scrum (or Kanban Team) ensure their Product Backlog Items are well thought out. This means nothing is consider for Sprint work that would get probably get stuck.I've already pointed out that ready encourages mini-waterfall/gate system.
-
#DefinitionOfReady
Under some circumstances a Definition of Ready helps a Scrum (or Kanban Team) ensure their Product Backlog Items are well thought out. This means nothing is consider for Sprint work that would get probably get stuck.I've already pointed out that ready encourages mini-waterfall/gate system.
-
#DefinitionOfReady
Under some circumstances a Definition of Ready helps a Scrum (or Kanban Team) ensure their Product Backlog Items are well thought out. This means nothing is consider for Sprint work that would get probably get stuck.I've already pointed out that ready encourages mini-waterfall/gate system.
-
@sysop408 @bernie @anil Sheldon thanks. Mastodon limits context. #ProductBacklogRefinement is the activity in Scrum (and I guess Kanban) where the team and the Product Owner review the items that are coming up in the near term to make sure that there is a common understanding of what they want to build. This article is good starting point: https://resources.scrumalliance.org/Article/product-backlog-refinement
-
Pivot in Public. Nearly a month of writing about #ProductBacklogRefinement I'm seeing little engagement. As a student of #LeanStartup I want to learn from my audience.
Write in candidates are also appreciated.
A ThreePercentBetter production in partnership with @bernie and @anil
#EffectiveMeetings #BuildInPublic #PivotHelp me understand:
-
Pivot in Public. Nearly a month of writing about #ProductBacklogRefinement I'm seeing little engagement. As a student of #LeanStartup I want to learn from my audience.
Write in candidates are also appreciated.
A ThreePercentBetter production in partnership with @bernie and @anil
#EffectiveMeetings #BuildInPublic #PivotHelp me understand:
-
Pivot in Public. Nearly a month of writing about #ProductBacklogRefinement I'm seeing little engagement. As a student of #LeanStartup I want to learn from my audience.
Write in candidates are also appreciated.
A ThreePercentBetter production in partnership with @bernie and @anil
#EffectiveMeetings #BuildInPublic #PivotHelp me understand:
-
Pivot in Public. Nearly a month of writing about #ProductBacklogRefinement I'm seeing little engagement. As a student of #LeanStartup I want to learn from my audience.
Write in candidates are also appreciated.
A ThreePercentBetter production in partnership with @bernie and @anil
#EffectiveMeetings #BuildInPublic #PivotHelp me understand:
-
Pivot in Public. Nearly a month of writing about #ProductBacklogRefinement I'm seeing little engagement. As a student of #LeanStartup I want to learn from my audience.
Write in candidates are also appreciated.
A ThreePercentBetter production in partnership with @bernie and @anil
#EffectiveMeetings #BuildInPublic #PivotHelp me understand:
-
This set of tips summarized from https://www.shortcut.com/blog/how-to-do-backlog-refinement-less-wrong
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
-
This set of tips summarized from https://www.shortcut.com/blog/how-to-do-backlog-refinement-less-wrong
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
-
This set of tips summarized from https://www.shortcut.com/blog/how-to-do-backlog-refinement-less-wrong
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
-
This set of tips summarized from https://www.shortcut.com/blog/how-to-do-backlog-refinement-less-wrong
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
-
This set of tips summarized from https://www.shortcut.com/blog/how-to-do-backlog-refinement-less-wrong
What other tips would you offer? (Fair warning, I will tell the world).
#EffectiveMeetings I'm slowly looking to every single detail I can find on #ProductBacklogRefinement
-
- Collaboration should involve hearing from all voices, a good ScrumMaster should be facilitating to give everyone an opportunity to share
- Don’t get too far ahead - 3ish Sprints of well understood work is enough. (Some will argue even less is better)
- You don’t need to detail each and every acceptance criteria in Backlog RefinementWhat other tips would you offer? (Fair warning, I will tell the world).
-
- Collaboration should involve hearing from all voices, a good ScrumMaster should be facilitating to give everyone an opportunity to share
- Don’t get too far ahead - 3ish Sprints of well understood work is enough. (Some will argue even less is better)
- You don’t need to detail each and every acceptance criteria in Backlog RefinementWhat other tips would you offer? (Fair warning, I will tell the world).
-
- Collaboration should involve hearing from all voices, a good ScrumMaster should be facilitating to give everyone an opportunity to share
- Don’t get too far ahead - 3ish Sprints of well understood work is enough. (Some will argue even less is better)
- You don’t need to detail each and every acceptance criteria in Backlog RefinementWhat other tips would you offer? (Fair warning, I will tell the world).
-
- Collaboration should involve hearing from all voices, a good ScrumMaster should be facilitating to give everyone an opportunity to share
- Don’t get too far ahead - 3ish Sprints of well understood work is enough. (Some will argue even less is better)
- You don’t need to detail each and every acceptance criteria in Backlog RefinementWhat other tips would you offer? (Fair warning, I will tell the world).
-
- Collaboration should involve hearing from all voices, a good ScrumMaster should be facilitating to give everyone an opportunity to share
- Don’t get too far ahead - 3ish Sprints of well understood work is enough. (Some will argue even less is better)
- You don’t need to detail each and every acceptance criteria in Backlog RefinementWhat other tips would you offer? (Fair warning, I will tell the world).
-
- Everyone has a different definition of ready. (Hint I warned that Ready has some risks)
- Product Backlog is being refined 6+ Sprints out - too much detail too far ahead team members feel their time is being wasted.The Cure (cue 80’s music)
- PO preps before refinement - they deeply understand what they want worked on, they know who needs to be there and as others have suggested they might even tell people in advance what will be worked on
2/4 #EffectiveMeetings #ProductBacklogRefinement -
- Everyone has a different definition of ready. (Hint I warned that Ready has some risks)
- Product Backlog is being refined 6+ Sprints out - too much detail too far ahead team members feel their time is being wasted.The Cure (cue 80’s music)
- PO preps before refinement - they deeply understand what they want worked on, they know who needs to be there and as others have suggested they might even tell people in advance what will be worked on
2/4 #EffectiveMeetings #ProductBacklogRefinement -
- Everyone has a different definition of ready. (Hint I warned that Ready has some risks)
- Product Backlog is being refined 6+ Sprints out - too much detail too far ahead team members feel their time is being wasted.The Cure (cue 80’s music)
- PO preps before refinement - they deeply understand what they want worked on, they know who needs to be there and as others have suggested they might even tell people in advance what will be worked on
2/4 #EffectiveMeetings #ProductBacklogRefinement -
- Everyone has a different definition of ready. (Hint I warned that Ready has some risks)
- Product Backlog is being refined 6+ Sprints out - too much detail too far ahead team members feel their time is being wasted.The Cure (cue 80’s music)
- PO preps before refinement - they deeply understand what they want worked on, they know who needs to be there and as others have suggested they might even tell people in advance what will be worked on
2/4 #EffectiveMeetings #ProductBacklogRefinement -
- Everyone has a different definition of ready. (Hint I warned that Ready has some risks)
- Product Backlog is being refined 6+ Sprints out - too much detail too far ahead team members feel their time is being wasted.The Cure (cue 80’s music)
- PO preps before refinement - they deeply understand what they want worked on, they know who needs to be there and as others have suggested they might even tell people in advance what will be worked on
2/4 #EffectiveMeetings #ProductBacklogRefinement -
I love the title Less Wrong Backlog Refinement. This article pleasantly surprised me. This is a tool vendor site (it’s goal is to be a better than JIRA Scrum/Kanban tool), most tools vendors do not understand Scrum.
They open with Anti-Patterns:
- Meeting is used to assign work
- Team Member My opinion doesn’t matter, often because the PO is telling, not listening
- PO is Micromanaging or it’s opposite absent
- PO is unprepared -
I love the title Less Wrong Backlog Refinement. This article pleasantly surprised me. This is a tool vendor site (it’s goal is to be a better than JIRA Scrum/Kanban tool), most tools vendors do not understand Scrum.
They open with Anti-Patterns:
- Meeting is used to assign work
- Team Member My opinion doesn’t matter, often because the PO is telling, not listening
- PO is Micromanaging or it’s opposite absent
- PO is unprepared -
I love the title Less Wrong Backlog Refinement. This article pleasantly surprised me. This is a tool vendor site (it’s goal is to be a better than JIRA Scrum/Kanban tool), most tools vendors do not understand Scrum.
They open with Anti-Patterns:
- Meeting is used to assign work
- Team Member My opinion doesn’t matter, often because the PO is telling, not listening
- PO is Micromanaging or it’s opposite absent
- PO is unprepared -
I love the title Less Wrong Backlog Refinement. This article pleasantly surprised me. This is a tool vendor site (it’s goal is to be a better than JIRA Scrum/Kanban tool), most tools vendors do not understand Scrum.
They open with Anti-Patterns:
- Meeting is used to assign work
- Team Member My opinion doesn’t matter, often because the PO is telling, not listening
- PO is Micromanaging or it’s opposite absent
- PO is unprepared -
I love the title Less Wrong Backlog Refinement. This article pleasantly surprised me. This is a tool vendor site (it’s goal is to be a better than JIRA Scrum/Kanban tool), most tools vendors do not understand Scrum.
They open with Anti-Patterns:
- Meeting is used to assign work
- Team Member My opinion doesn’t matter, often because the PO is telling, not listening
- PO is Micromanaging or it’s opposite absent
- PO is unprepared