120 complete swarm (#210)

* 120: Add survey data * 120: Update README
2018-04-27 12:10:39 +08:00 · 2018-04-27 12:10:39 +08:00 · 039f48b43f
parent 84e48ddf9b
commit 039f48b43f
2 changed files with 147 additions and 5 deletions
--- a/ideas/120-swarm-process/README.md
+++ b/ideas/120-swarm-process/README.md
@ -1,8 +1,9 @@
 ---
 id: 120-swarm-process
 title: Formalize swarm process
-status: Limbo
+status: Completed
 created: 2018-04-02
+ended: 2018-05-01
 category: meta
 contributors:
    - martinklepsch
@ -19,7 +20,7 @@ future-iterations: yes

    Idea: 120-swarm-process
    Title: Formalize swarm process
-    Status: In Progress
+    Status: Completed
    Created: 2018-03-30
    Requires (*optional):
    Replaces (*optional):
@ -144,8 +145,16 @@ Description:
 - iii. Town Hall presentation outlining lifecycle, well-definition and roles.
 - iv. Send out survey through Polly.

-### Iteration 3
-(Buffer)
+Town Hall Update: 2017-04-23
+
+Progress last two weeks: Update manual and template, clarify swarm’s role in
+org; static site index; ongoing support and knowledge spreading. 80% of Core
+OKRs covered!
+
+Goals for next two weeks: Retainer. Start to wind down swarm. Bounty up
+outstanding issues. Ongoing support.
+
+Lessons learned so far: Updating manual README index is terrible UX.

 ## Success Metrics

@ -158,7 +167,6 @@ Three primary success metrics.
 - 1.2. It is clear to me when a swarm ends
 - 1.3. It is clear to me what it means for a swarm to be well-defined
 - 1.4. It is clear to me what is expected of a swarm lead
- 1.5. It is clear to me what is expected of an evaluator

 ### 2. CORE SWARM/OKR COVERAGE.
 80% of Core OKRs are explicit covered by well-defined, in progress swarms.
@ -176,6 +184,30 @@ future experimentation and compensation tied to it:
 This swarm will be time-boxed to one month and marked as completed May 1 OR when
 success metrics have been met.

+## Mini-post mortem
+
+Success metric 2 and 3 achieved. Success metric 1 ended up at 3.7 / 3.7 / 3.9 /
+3.9 respectively, whereas we were aiming for 4.5/5. for this one. So still some
+work to be done there (see section below). Also got a static site index as a bonus at (ideas.status.im)[https://ideas.status.im/].
+
+Will require ongoing support to make sure we follow through, but this can be
+done outside of swarm model, similar to code review etc.
+
+### A few survey take-aways
+
+See raw results in (survey-results)[town-hall-7-survey-results.md].
+
+- Swarm start clarity: global notifications on when swarms start
+
+- Swarm start clarity: some work done in draft/prep mode, line blurry
+> Comment: If in-progress event was tied to compensation being unlocked this would be very clear -- Oskar
+
+- Swarm end clarity: success criteria validation? exit criteria still not clear
+> Comment: Hopefully this will become more clear as more and more swarms finish. -- Oskar
+
+- Swarm well-defined clarity: can be stated more clearly in terms of user stories
+> Comment: In TEMPLATE now https://github.com/status-im/ideas/blob/master/TEMPLATE.md#user-stories - something UXR can assist with too -- Oskar
+
 ## Supporting Role Communication

 ## Copyright
--- a/ideas/120-swarm-process/town-hall-7-survey-results.md
+++ b/ideas/120-swarm-process/town-hall-7-survey-results.md
@ -0,0 +1,110 @@
+# Raw data from survey after Town Hall 7
+
+## 1. It is clear to me when a swarm starts
+
+(sent to #general)
+
+Strongly Agree 12% (6)
+Agree 54% (28)
+Neutral 25% (13)
+Disagree 10% (5)
+Strongly Disagree
+
+Average: 3.7
+Total Votes: 52
+
+### Comments
+
+> Neutral: WHere are they announced, who validates and create the slack channel?,
+> 
+> Disagree: Sometimes the lines between in progress & draft seems to be a bit blurred ( some work is done before is officially in progress for example).
+> 
+> Agree: Oskar's work on that site (and the fact I have had to review a lot of stuff there for bounties) has left me with great insight into the process.
+> 
+> Neutral: I'm not sure how swarms officially start. Some seem to start without an idea and others seem to stay in draft.
+> 
+> Neutral: Well, it's like clear, but i'd add some global notification (maybe in core channel) like '@channel - this is official start of the swarm #XXXX, join the respective channel!'
+> 
+> Neutral: Start of work and formal establishment of the swarm may overlap.
+> 
+> Agree: I *think* it's when a PR has been requested.,
+> 
+> Agree: It seems that swarms can start even when they are in draft mode - or is that not the case. I guess hence the relative clarity
+> 
+> Disagree: If a swarm lead is not super clear about when the swarm actually starts, then it's not clear when one starts.
+> 
+> Disagree: There is a certain amount of work required to get the swarm started in the first place - defining scope and all that. So, what is the difference between the moment this prep work starts and the moment when actual swarm starts?,
+> 
+
+## 2. It is clear to me when a swarm ends
+
+(sent to #general)
+
+Strongly Agree 16% (8)
+Agree 49 (28)
+Neutral 29% (15)
+Disagree 6% (3)
+Strongly Disagree
+
+Average: 3.7
+Total Votes: 51
+
+### Comments
+
+> Agree: Scope is done, milestones achieved,
+> 
+> Agree: Highly depends on swarm,
+> 
+> Neutral: not enough data to answer this, it is clear on paper (when exit criteria are met) but I would like to see it before in action.
+> 
+> Strongly Agree: OKRs and clear exit criteria make this much easier and we seem to be developing an org shorthand (P0, P1 etc) that allows us to talk about complex things quickly and simply enough for everyone to get a handle on things. This should be strongly encouraged.
+> 
+> Agree: It requires checking after a while whether it hasn't been re-activated, but the concept is clear.
+> 
+> Neutral: Who validates the success metrics?
+> 
+> Agree: All OKRs and exit criteria have been met.,
+> 
+> Neutral: Feels a little less clear and seems as though some swarms with remaining iterations get overshadowed by new swarms or ideas. 
+> 
+> Neutral: Depends on how clear is exit criteria
+> 
+> Disagree: The whole point of a swarm is to be somewhat eternal and yet somewhat ephemeral. To say when a swarm ends is kind of... non sequiter? Would that be the correct word? In any case, it never really ends when started up imv.
+> 
+
+## 3. It is clear to me what it means for a swarm to be well-defined 
+
+(sent to #general)
+
+Strongly Agree 10% (5)
+Agree 61% (31)
+Neutral 25% (13)
+Disagree 4% (2)
+Strongly Disagree
+
+Average: 3.8
+Total Votes: 51
+
+### Comments
+
+> Disagree: I dont know how is this well-defined right now but it may be my personal view. In terms of scope mostly. Like all swarms (almost) are some kind of feature-based (like fast-status for ex) but scope is not well defined, like it is not only the issues fixing to me but it is achieving some UX cases that we can check with real users (in 90 % cases). So personally i think this could be improved and stated more clearly, like which scenarios (UX cases / user stories / whatever ) we want to achieve in terms of particular swarm (team) and separate them to iterations according to the workload and capacity
+> 
+> Agree: Must have a specific set of _achievable_ OKRs and exit criteria and resources that can dedicate some time. 
+
+## 4. It is clear to me what is expected of a swarm lead
+
+(sent to #swarms)
+
+Strongly Agree 15% (4)
+Agree 63% (17)
+Neutral 15% (4)
+Disagree 7% (2)
+Strongly Disagree
+
+Average: 3.9
+Total votes: 27
+Agree or strongly agree: 78%
+
+### Comments
+
+No comments.