You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2014-03-01-team-yayasan-getting-started.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ So instead of me answering emails to single persons I could answer email on the
56
56
57
57
Finally we created a wiki where we added information around each hospital and clinic.
58
58
59
-
When we had done that we started to have a conversation about where this would lead us. It would lead to greater transparency and that's a really good thing, was the common conclusion in the team. We decided to press on with this idea. I summarised our thinking in a couple of keywords and created a wiki about it. Here's an extract of it
59
+
When we had done that we started to have a conversation about where this would lead us. It would lead to greater transparency and that's a really good thing, was the common conclusion in the team. We decided to press on with this idea. I summarized our thinking in a couple of keywords and created a wiki about it. Here's an extract of it
60
60
61
61
> **Transparency** - We believe that we should seek more and more transparency. It fosters a good and open culture of collaboration and openness. In a transparent setting its easier to get help, easier to share information and harder to hide and do bad things.
62
62
> Ultimately this leads to trust being built up and shared among the members of the organization. We trust each other to do good and I, as member of the organization, knows that everything I do will be visible for everyone else in the organization.
Copy file name to clipboardExpand all lines: _posts/2014-03-24-do-you-think-kanban-can-help-us.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ And thank you for making this an easy question to answer: Yes, kanban will help
48
48
49
49
Well, I return your favour and answer it a bit more elaborated than that.
50
50
51
-
First of all: Kanban or not is not that important. What is important (i think) is to see what you are doing (and problems/opportunities you're facing), strive to complete work fast and help the workflow to work better. This could be summarised in:
51
+
First of all: Kanban or not is not that important. What is important (i think) is to see what you are doing (and problems/opportunities you're facing), strive to complete work fast and help the workflow to work better. This could be summarized in:
Copy file name to clipboardExpand all lines: _posts/2016-10-03-big-room-planning---a-failure-testatment-i-like.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ All in all most of these meetings has been good and useful, especially the prior
35
35
36
36
We then held the meeting itself, involving about 25-30 people in our teams and ca 20-25 people from groups around us that we need to get our stuff out of the door. Some of these people were high-ranking people that (in case) we needed to resolve prioritisation issues and dependencies.
37
37
38
-
Today I've spent the better part of 8 hours trying to summarise and document what was said during the meeting. I'm not quite done yet so maybe a few hours more before it's done.
38
+
Today I've spent the better part of 8 hours trying to summarize and document what was said during the meeting. I'm not quite done yet so maybe a few hours more before it's done.
39
39
40
40
All in all - quite an investment to get our sights aligned and our work planned. We planned for 5 weeks ahead, which is much shorter than recommended by SAFe (8-12 weeks) but still enough that we didn't know for sure what is going to be delivered in the end of the session.
41
41
@@ -65,7 +65,7 @@ It would not be fair to list everything that is bad with one approach without at
65
65
66
66
But here goes; here's a suggestion that requires no changes in organization and a lot less overhead in setting meetings up. We have parts of this in place already in my current team and I long for the time when we can do this smoother than a big room planning.
67
67
68
-
We've created a kanban board for the high-level stories (we summarise those in a one page format stating the hypothesis, size, metrics and other important facts about the feature) that are lined up for development.
68
+
We've created a kanban board for the high-level stories (we summarize those in a one page format stating the hypothesis, size, metrics and other important facts about the feature) that are lined up for development.
69
69
70
70
From this point this is just my thinking out loud, but I'm sure this would work in a smoother, cheaper and faster way than to call a big expensive meeting every X weeks.
Copy file name to clipboardExpand all lines: _posts/2016-10-03-move-the-information-to-the-authority-considered-harmful.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ No-one in the "deploy to production" team or the "Change Management Board" have
33
33
34
34
You need to take this higher up. To the management team. They make the decisions in matters like these, cutting across departments.
35
35
36
-
In order to present this information in a correct way you need to **summarise** the information, calculate a **business case** and present some certainty of **positive** improvement (or they will not look at it) and finally **get time** with the correct people in a meeting where they are ready to make the decision.
36
+
In order to present this information in a correct way you need to **summarize** the information, calculate a **business case** and present some certainty of **positive** improvement (or they will not look at it) and finally **get time** with the correct people in a meeting where they are ready to make the decision.
37
37
38
38
Since they only meet for 1 hour per week (if you are lucky) they will have a lot of things on their agenda. That means that you need to digest and be concrete in the information that you present - making **only the important** parts stand out.
39
39
@@ -99,7 +99,7 @@ If their (mine) kids ask them what they do for work the answer:
99
99
>
100
100
> I'm an powerpoint creator
101
101
102
-
Their job is to summarise, simplify and concretise information, situations, context and problem that one group have, a group that they are not working in, to present to another group of people, that is not in that situation either, so that the second group can make a decision to help the first group.
102
+
Their job is to summarize, simplify and concretise information, situations, context and problem that one group have, a group that they are not working in, to present to another group of people, that is not in that situation either, so that the second group can make a decision to help the first group.
103
103
104
104
It's weird. Hey, even that sentence is weird, but that might be my bad english.
105
105
@@ -137,7 +137,7 @@ For me the idea of "moving authority to the information" is building around thre
137
137
138
138
Another example; at my company, [Aptitud](http://www.aptitud.se), all invoices for things that employees buys will be sent to everyone in the company. Sure you can buy a TV and call it a "computer related working device" - but remember that everyone will see it.
139
139
140
-
**Accountability** - if you make decisions you will also face the consequences. At Amazon this is summarised in the slogan ["You build it - you own it"](http://aronatkins.github.io/2014/12/23/you-build-it-you-own-it.html). You will have to take **responsibility** for the things you do. Just likes adults do in real life.
140
+
**Accountability** - if you make decisions you will also face the consequences. At Amazon this is summarized in the slogan ["You build it - you own it"](http://aronatkins.github.io/2014/12/23/you-build-it-you-own-it.html). You will have to take **responsibility** for the things you do. Just likes adults do in real life.
141
141
142
142
These three go together; demanding transparency without trust is just micromanaging, trusting without any accountability is irresponsible, hold people accountable without giving them authority is cruel.
Copy file name to clipboardExpand all lines: _posts/2017-01-10-kindness.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ tags:
12
12
13
13
I'm very proud of my church (or corps as we say in the [Salvation Army](http://www.salvationarmy.com) - the [Vasa Corps of Stockholm](https://www.fralsningsarmen.se/vasakaren). The moment I came there I felt right at home and I'm more than happy to, voluntary, spend a lot of my leisure time in the different groups of the church.
14
14
15
-
About a month ago I heard someone, that is new to our congregation, say something that summarised a lot of the spirit in the church:
15
+
About a month ago I heard someone, that is new to our congregation, say something that summarized a lot of the spirit in the church:
16
16
17
17
> Here people are saying kind things about each other
Copy file name to clipboardExpand all lines: _posts/2017-08-07-changing-the-die---that-cant-go-faster.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ First of all it's interesting to see that the rest of the car industry considere
37
37
38
38
We have to continue to challenge the current ways to become better.
39
39
40
-
The second observation is that one of the reasons that Taichii Ohno pressed on was that he had a strong guiding star; smaller batches with less inventory. This is famously summarised in Toyota production strategy:
40
+
The second observation is that one of the reasons that Taichii Ohno pressed on was that he had a strong guiding star; smaller batches with less inventory. This is famously summarized in Toyota production strategy:
Copy file name to clipboardExpand all lines: _posts/2018-01-22-create-a-dynamic-updated-chart-in-google-sheets.md
+26-26Lines changed: 26 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,13 +34,13 @@ Meaning; there are a couple of scale-questions (1-6) and one question for which
34
34
35
35
> Can I get the result per team?
36
36
37
-
And me myself I wanted to see the result grouped in thirds (how many vote 1-2, how many 3-4 and how many vote 5-6).
37
+
And me myself I wanted to see the result grouped in thirds (how many vote 1-2, how many 3-4 and how many vote 5-6).
38
38
39
-
This is not too hard to do and even get some nice graphs to show the result in. [Here's a Google Sheet](https://docs.google.com/spreadsheets/d/1aSel__vOK1u3Njsl9_SMKLlIRETY1RXo5V1vtYf_KJ4/) where I'm playing around with this.
39
+
This is not too hard to do and even get some nice graphs to show the result in. [Here's a Google Sheet](https://docs.google.com/spreadsheets/d/1aSel__vOK1u3Njsl9_SMKLlIRETY1RXo5V1vtYf_KJ4/) where I'm playing around with this.
40
40
41
41
## Step 1 - Create sheet for the stats
42
42
43
-
All the data from a survey ends up in a Google Sheet called ["Form Responses"](https://docs.google.com/spreadsheets/d/1aSel__vOK1u3Njsl9_SMKLlIRETY1RXo5V1vtYf_KJ4/edit#gid=0) or something like that. I have created a heet like that, but there's no connection to a form now. Doesn't matter for our purpose. This sheet is now our raw-data and we will not touch it, as it gets the data from the Form.
43
+
All the data from a survey ends up in a Google Sheet called ["Form Responses"](https://docs.google.com/spreadsheets/d/1aSel__vOK1u3Njsl9_SMKLlIRETY1RXo5V1vtYf_KJ4/edit#gid=0) or something like that. I have created a sheet like that, but there's no connection to a form now. Doesn't matter for our purpose. This sheet is now our raw-data and we will not touch it, as it gets the data from the Form.
44
44
45
45
After that I just added a new ["Stats"-sheet](https://docs.google.com/spreadsheets/d/1aSel__vOK1u3Njsl9_SMKLlIRETY1RXo5V1vtYf_KJ4/edit#gid=51274800) where we will make our calculation. To start with I made something really simple; just the average for each question. That is two columns that looks like this:
46
46
@@ -51,9 +51,9 @@ After that I just added a new ["Stats"-sheet](https://docs.google.com/spreadshee
* Column B contains the average. Note that it contains all the values from `Form Responses'!C:C`, including the question title. But the `Average`-function is of course smart enough to ignore the not numeric values
58
58
59
59
## Step 2 - Some grouping
@@ -62,7 +62,7 @@ All though the Responses feature of Google Forms has a nice auto-summary, I want
62
62
63
63
* 1-2 - detractors. They didn't really like whatever this question was about
64
64
* 3-4 - the Meh's. These respondents are a little bit either or…
65
-
* 5-6 - the attractors. These people really liked whatever we asked about.
65
+
* 5-6 - the attractors. These people really liked whatever we asked about.
66
66
67
67
In order to do this we need to use another function; `CountIf`, that counts the number of rows that matches a criteria. Here's an example row to get these values:
68
68
@@ -75,20 +75,20 @@ In order to do this we need to use another function; `CountIf`, that counts the
75
75
* 3-4 - I count the rows that have a value above two (`>2`) and then subtract the number of 5-6.
76
76
* I then added a total for the total number of answers for this question
77
77
78
-
Nothing strange there and I even added a column with percentages for each group, that ended up not using. It was as easy as just diving the number of responses with the total (`=G3/I3`, for example).
78
+
Nothing strange there and I even added a column with percentages for each group, that ended up not using. It was as easy as just diving the number of responses with the total (`=G3/I3`, for example).
79
79
80
-
## Step 3 - Visualising totals
80
+
## Step 3 - Visualizing totals
81
81
82
-
Let's make a diagram out of that to show our result.
82
+
Let's make a diagram out of that to show our result.
83
83
84
84
* Select the data you want to include by holding down CTRL/CMD and selecting the data. This way you can select data that is not next to each other. For my sheet, I selected `A1:A5,C1:C5,E1:E5,G1:G5`
85
85
* Click the button for Insert Chart (or in the menu Insert => Chart)
86
-
* Do some formatting of the labels, legend etc.
86
+
* Do some formatting of the labels, legend etc.
87
87
* I removed the Horizontal axis title
88
88
* Put the Legend on the bottom
89
89
* And updated the Title of the Chart to `Spread of values - all teams`
90
90
91
-
This gave me a nice graph that looks like this and is a good start.
91
+
This gave me a nice graph that looks like this and is a good start.
@@ -109,9 +109,9 @@ I then added a new cell with a drop-down-box for the teams. This is easily done
109
109
* Enter the column with the Teams, in my case `'Form Responses'!B:B`
110
110
* Click OK to create a drop-down list of the team names
111
111
112
-
A nice little trick here is to ensure that you start from the second row in the range because the first row probably contains the title of the question (`Team`) in this case. You can easily do that by giving the range `'Form Responses'!B2:B`.
112
+
A nice little trick here is to ensure that you start from the second row in the range because the first row probably contains the title of the question (`Team`) in this case. You can easily do that by giving the range `'Form Responses'!B2:B`.
113
113
114
-
Pretty nifty; start on B2 and use the entire column.
114
+
Pretty nifty; start on B2 and use the entire column.
115
115
116
116
### Average per team
117
117
@@ -127,16 +127,16 @@ Let's dissect the `AverageIf` formula a bit:
127
127
128
128
* The first part (`'Form Responses'!B:B`) is the range we are going to evaluate our criteria again. "If *these* rows matches"
129
129
* The second part (`$J$18`) is the criteria itself. In this case just: "Same value that is in J18"
130
-
* The $-signs is just a way to make sure that it's always `J18` even when you copy the formula to another cell
131
-
* The final part (`'Form Responses'!C:C`) is the values to run average on.
130
+
* The `$`-signs is just a way to make sure that it's always `J18` even when you copy the formula to another cell
131
+
* The final part (`'Form Responses'!C:C`) is the values to run average on.
132
132
133
133
The whole thing could be read like:
134
134
135
135
> Get all rows whose B-value matches J18 and give me the Average of the values in the C-column
136
136
137
137
### Counts per team
138
138
139
-
Now let's do the same thing to count the 1-2, 3-4 and 5-6 values. This is not as easy it turns out. Because, if you remember we used `CountIf` to count the values. We need a way to evaluate more than one criteria.
139
+
Now let's do the same thing to count the 1-2, 3-4 and 5-6 values. This is not as easy it turns out. Because, if you remember we used `CountIf` to count the values. We need a way to evaluate more than one criteria.
140
140
141
141
Enter `CountIfs` that does precisely that. Here's an example formula, to count 1-2 for a certain team:
142
142
@@ -158,32 +158,32 @@ Do the same for the other formulas (3-4 and 5-6), before continuing:
You can now try it out by select different teams in J18, which should update the values for the formula.
163
+
You can now try it out by select different teams in J18, which should update the values for the formula.
164
164
165
165
### Watch out
166
166
167
-
I noticed that in order to do this *change* people need to be able to *change* the Google Sheet if you share it with others. That is pretty obvious when you think about it, but I forgot to set that when I sent it out.
167
+
I noticed that in order to do this *change* people need to be able to *change* the Google Sheet if you share it with others. That is pretty obvious when you think about it, but I forgot to set that when I sent it out.
168
168
169
169
## Step 5 - Charts, charts, charts
170
170
171
-
Let's, **finally**, use all of this for something useful. Let's create a graph similar to the one above, but only for the team that the user has selected.
171
+
Let's, **finally**, use all of this for something useful. Let's create a graph similar to the one above, but only for the team that the user has selected.
172
172
173
173
* As before, this requires some tricky selection using the CTRL/CMD key and selecting the `A16:A20,C16:C20,E16:E20,G16:G20` values.
174
174
* The rest is the same as before:
175
175
* Click the button for Insert Chart (or in the menu Insert => Chart)
176
-
* Do some formatting of the labels, legend etc.
177
-
- I removed the Horizontal axis title
178
-
- Put the Legend on the bottom
179
-
- And updated the Title of the Chart to `Spread of values - selected team`
176
+
* Do some formatting of the labels, legend etc.
177
+
* I removed the Horizontal axis title
178
+
* Put the Legend on the bottom
179
+
* And updated the Title of the Chart to `Spread of values - selected team`
180
180
181
181
Now the user can change team in the `J18`-dropdown box and see the graph update itself. Like a nice little reporting tool. Here's how the graph looks for me:
I learned a lot about Google Sheets and the formulas I used by trying to figure this out. I hope you did too.
187
+
I learned a lot about Google Sheets and the formulas I used by trying to figure this out. I hope you did too.
188
188
189
-
[My sheet is found here](https://docs.google.com/spreadsheets/d/1aSel__vOK1u3Njsl9_SMKLlIRETY1RXo5V1vtYf_KJ4/edit?usp=sharing). If you want to play around you can duplicate it and play around with it.
189
+
[My sheet is found here](https://docs.google.com/spreadsheets/d/1aSel__vOK1u3Njsl9_SMKLlIRETY1RXo5V1vtYf_KJ4/edit?usp=sharing). If you want to play around you can duplicate it and play around with it.
0 commit comments