ScrumPLoP Product Backlog
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
Still loading...
ABCDE
1
Burndown Charts
2
3
Pattern or other work itemBrief DescriptionDeveloper's Estimated Delivery DateRemarksInitials
4
5
Fixed Date PBI3 known uses audit still failsEditorial Team
6
Sprint GoalCopy editing and getting to Done4/4/2017Mark is Captain. Cope says Done. Cesário says Done. Lachlan says Done.Editorial Team
7
Product WakeCopy editing and getting to Done1/5/2017Mark is Captain. Cope agrees Done. And Lachlan. And Cesário.Editorial Team
8
Birds of a FeatherWriters' Workshop, copy editing, getting to Done1/5/2017Now has good header picture. Orphaned. Cope has wrapped it up and put out a call-to-Done. Lachlan says Done. Mark had suggestions that I don't think are needed. Cesário says "Done" and had a side comment.
9
Sprint Backlog ItemCopy editing and getting to Done1/5/2017Mark is Captain. Cope says Done. Lachlan says Done. Cesário says Done.Editorial Team
10
Updated VelocityCopy editing and getting to Done21/4/2017Cope will captain. Incorporated Lachlan's comments. Mark says O.K. Cesário says O.K.cope
11
Small ItemsCopy editing and getting to DoneLachlan is Captain.

Done 21/4/2017
June and Alan have commented that it needs some work because of overlap / potential confusion with the SBI pattern. Cope thinks Done. So do Mark and Cesário.lh
12
Product Backlog SequenceAt least it would be another example sequence1/5/2017Cope is Captain. Mark says O.K.cope
13
Scrum of ScrumsCopy editing and getting to Done1/5/2017Cesário is Captain. Cope says Done.cr
14
MetaScrumCopy editing and getting to Done1/5/2017Cesário is Captaincr
15
Sequence to knit together patterns related to organising multiple Scrum teams
-----------

Scaling Sequence
How do we give visibility to the patterns that deal with an organisation that has more than one Scrum team per product?
--------------------------
We need to evaluate whether the scaling sequence will fit together with the new Value Area pattern(s) and, if so, write it
1/5/2017aoc? cr
16
1/5/2017CR is captain. First draft done. Yay!aoc? cr
17
Whack the Mole

------------------------------------------------------
Clarify difference between Whack the Mole and Daily Clean Code
Copy editing and getting to Done

------------------------------------------------------------------------
"Aiming" to have a result is a KPI, not a pattern. The cadence aspect of DCC is nonetheless nice. Both should probably be retained but both probably need some cleanup.
1/5/2017Differentiate from Daily Clean Code
--------------------------------
Mark is Captain
lh / mdh
18
Spirit of the GameStill needs some minor cleanup.1/5/2017Mark is Captain
19
Happiness MetricCopy editing and getting to Done1/4/2017Mark is CaptainCope is researching.
20
Team SprintCopy editing and getting to Done1/5/2017Mark is CaptainEditorial Team
21
High Value FirstCopy editing and getting to Done1/5/2017Cope is Captain. Mark agrees Done. Cesário DISAGREES.Editorial Team
22
Daily ScrumRemove ambiguitiesJeff wants a crack at itjs
23
Product Organisation SequenceNeeds a lot of work.End of August 2016 1/5/2017nbh cope
24
Leading TeamNew Pattern (Scaling)1/5/2017Cesário will captaincr
25
Regular Product IncrementCopy editing and getting to Done1/5/2017Lachlan is Captainlh
26
Value Stream ForkProbably done1/5/2017Cope will captain. Tentatively ready for review.cope
27
MitosisNew Pattern (Scaling)1/5/2017Cope will captaincope
28
Tie up Value AreasIn particular Value Area seems to extend Scrum or portray an alternative vision to Scrum, in areas that seem already to be covered by the Meta-Scrum, Independent Velocities, and Scrum of Scrums.1/5/2017Cesário will captaincr
29
Set-Based DesignTo evaluate potential alternative product directions, hold a "bake-off"Hopefully ready by Scrum PLoP 2017EL
30
Teams that Finish Early Accelerate FasterCopy editing and getting to DoneEditorial Team
31
Visible StatusCopy editing and getting to DoneEditorial Team
32
Dependencies FirstCopy editing and getting to DoneEditorial Team
33
One Step at a TimeCopy editing and getting to DoneEditorial Team
34
Greatest ValueCopy editing and getting to DoneEditorial Team
35
Impediment ListCopy editing and getting to Done
36
Organizational Sprint PulseCopy editing and getting to Done
37
Notes on VelocityCopy editing and getting to Done
38
DoneMasterCopy editing and getting to DoneMay eliminate.Editorial Team
39
Discussion: Do we need "PO also implements"?Alexander hates hands-off architects. In Jeff Sutherland's team the PO builds running prototypes to keep their hands dirty.
40
Historical References in patternsGood patterns tell where the idea evolved fromMark pointed this out: See https://www.agilealliance.org/agile101/practices-timeline/
41
PulseUncertainty about the duration of a work episode prevents the work from being done effectively, so work in time units of uniform length15 July 2016nbh
42
Follow the MoonScrum cycles should be attendant to natural rhythms (破). Needs copy editing and getting to DoneFirst draft donegb
43
Scrum TeamCopy editing and getting to Done
44
Collocated TeamCopy editing and getting to Done
45
Small TeamsCopy editing and getting to Done
46
Cross-Functional TeamCopy editing and getting to Done
47
Product OwnerCopy editing and getting to Done
48
Product Owner TeamCopy editing and getting to Done
49
Development PartnershipProbably done. Reviewed at Scrum PLoP 2016cope
50
Surrogate Product OwnerCopy editing and getting to Done
51
Development TeamCopy editing and getting to Done
52
Stable TeamsCopy editing and getting to Done
53
Self-organizing Teamsneeds to describe how local interaction leads to the roles of SM, PO, Dev team - this is for the product organisation sequence - unless we mean self-organising = self-managing (noted by Lachlan)
54
Involve the ManagersCopy editing and getting to Done
55
Knight of the MirrorsCopy editing and getting to Done
56
ScrumMasterCopy editing and getting to Done
57
SheepdogCopy editing and getting to Done
58
CoachCopy editing and getting to Done
59
CheerleaderCopy editing and getting to Done
60
Product Owner TrainerHas never been workshopped? Propose eliminating.
61
Scrum(Master) CoachHas never been workshopped?
62
FirewallNot sure why this is here. Placeholder for now.
63
ScrumMaster Gets FiredHas never been workshopped?
64
Oyatsu JinjaCopy editing and getting to Done. Needs minor language cleanup.
65
Small Red PhoneCopy editing and getting to Done
66
Fixed WorkCopy editing and getting to Done
67
Sprint PlanningCopy editing and getting to Done
68
SwarmingCopy editing and getting to Done
69
Kaizen PulseCopy editing and getting to Done
70
Beyond the Happy BubbleCopy editing and getting to Done
71
ScrumMaster IncognitoCopy editing and getting to Done
72
Norms of ConductCopy editing and getting to Done
73
Emergency ProcedureCopy editing and getting to Done
74
Illegitiumus non InterruptusCopy editing and getting to Done
75
Conway's LawCopy editing and getting to Done
76
Circle of TrustCopy editing and getting to Done
77
Product PrideCopy editing and getting to Done. Enlist Gabby — she once proposed a pattern like this.gb
78
Sacred ScheduleIf you don't end on time, you don't know where you are; Therefore: Don't put off Sprint completion, even for a day.Probably needs to be re-thought, or just folded into Sprintcope & nbh
79
Question: Do we want to include the Harrison / Coplien patterns in the book or just reference them?The book should stand alone but it could get pretty large if we include all the patterns we cite. Maybe just set up a spot on the web? Include half-page patlets for each, together with the quintessential photo?team
80
Audit: Pattern RecognisabilityWe need to audit the patterns to ensure that they are not just documentation of some part of Scrum, but that they can be indexed by the problem they solve to help Scrum teams gain insight to concrete problemsTBD
81
Audit: Pattern Context LinkingThe patterns should flow as a language and should complete each other in a way where the flow between a pair of patterns is explicit and obvious. This needs to be audited and most patterns will need updatingHas to wait for a plenary session at next PLoP (Iceland?)Depends on Sequences, which might help shed some light on doing this. Also needs to be coordiinated with "Create Pattern Language Graphs" (below)team
82
ScrumPLoP things1. Pictures
2. Difference between self-managing, autopoeietic, autonomous
83
Audit: 3 usesMake sure each pattern points to three independently discovered known uses using citable sources.Has to wait for a plenary session at next PLoP (Iceland?)Currently being done incrementallyteam
84
Audit: Is the PO the bad guy?We don't want the patterns to portray the PO as the bad guy.DF
85
Audit: Software focusNeeds to generalise beyond software
86
Consistent citation format
87
Book Picture SelectionWe can use the stuff from presentermedia.com or the ones that Neil found from the LOC or...Is progressing, but we probably should be starting to get explicit copy permissions. Need to check with publisher about what is needed."Done" includes having copy rights. Does it depend on having a financial framework in place?nbh, mdh
88
Create Pattern Language GraphsWe need graphs like the ones in the Org Patterns book to orient people to the patterns and their relationships. Again can use the dag or dotty facilities. Google has facilities to make these "touchable" for the web deliverableBookBinder part is done. Still need Organisational Structure Pattern Language graph.
89
Remove references to non-existent patternsNeed to remove references to patterns that have been deleted or never written. There are about 28 at last count. BookBinder audits can automatically produce the lists but there will be local rewording in each pattern, and the overall flow and wording must be attended to.1 October 2016. Delayed because we need to decide whether we'll need these patterns.Detailed data herecope
90
Scrum Blitz schedulingWe'll need at least one Scrum Blitz to finalize "Overall copy edit" as well as the AuditsOne done in the second week of 2017. Another scheduled for Lisbon before Scrum PLoP. Should have two more.cr, nbh, lh, cope
91
Overall copy editRevisit patterns that haven't been touched in years, and make sure patterns reflect our current understanding and the current state of Scrum (the Scrum Guide has changed since we started)4 of the team members concur that this is a 50- to 150-day job, full-time (½ - 1 day per pattern or other section; parallelism dscouraged). aa predicts end of June for his independent effortIs being done as a team at a ScrumBlitz. Rate is about half the time of the estimate.

aa prediction was not met, and no update.
cr, lh, cope, mdh, (aa separately)

nbh removed as disengaged
92
Legal and financial frameworkWe need a sink for the book royalties under a tax-free dispensation. It would be good if we also could be relieved of the adminstration.We could maybe use Hillside as the administrator of these agreementsCheck with Joe Yoder
93
Bring existing Scrum PLoP agreements up-to-dateThe legal and financial framework will change the parties named in the Scrum PLoP agreement. The agreement must be updated and all signatories must sign off.Depends on "Book legal and financial framework"
94
Professional copy-editIt would be good to choose our own copy editor to bring the English quality up to publication standards. Past performance by publishers' copy editors has been of irregular qualityDepends on a funding source and "Legal and Financial Framework." Could be deferred until after the Alpha book, but that creates an uncomfortable ménage à trois with the publlsher and weakens our negotiating position
95
Alpha BookA toolset that allows us to produce an alpha version of the printed book, along with enough topical content to make it interesting. Depends on book design / outline.

This is a benchmark and not an MVP. MVP doesn't apply to books and probably not at all in Agile: q.v. Luke Hohmann
7/1/2018There is a risk to this effort if we convert toolset mid-streamcope
96
Patlets AppendixKind of like in the Org Patterns bookjk
97
Approach PublishersIt's important to not do this too early, as it destroys credibility with the publisher if we bring a draft manuscript ("MVP") and then spend months readying the product. cope
98
New administrative environmentPeople don't like Google Docs, &c. for administering the patterns, and Ademar has proposed a simpler alternative hosted on git or some other site. This can start as a prototype and then grow.Should be before ScrumPLoP 2015, to make sense and to be worth doing? Maybe shoot for Scrum PLoP 2017Pushed down on the backlog because the value is becoming lower relative to the costaa
99
Patron-Supported UnderstandingScrum does not have buy-in from management. Therefore: Solution : Educate, get a patron and show resultjeos
100
Historical RetrospectiveProjects too often re-invent the wheel; Therefore: Start each new project with a retrospective over similar historic projectsRelates closely with Learning Registercope
Loading...
 
 
 
Sheet1