Done for now

Author: marcusoftnet

_posts/2013-08-13-repost-some-tools-for-improved-focus-improve-teamwork-and-faster-delivery.md

@@ -1,6 +1,6 @@
 ---
 layout: post
-title: Repost - Some tools for improved focus, improve teamwork and faster delivery
+title: Re-post - Some tools for improved focus, improve teamwork and faster delivery
 author: Marcus Hammarberg
 date: 2013-08-13 15:23:54
 tags:
@@ -12,7 +12,7 @@ tags:
  - Life of a consultant
 ---
 
-### REPOST FROM CODEBETTER
+### RE-POST FROM CODEBETTER
 
 I noticed that [CodeBetter](http://codebetter.com/marcushammarberg/) is slowing down. Maybe dying. I'm preserving [my post from there](http://codebetter.com/marcushammarberg/2013/08/13/some-tools-for-improved-focus-improve-teamwork-and-faster-delivery/), here to my site.
 
@@ -32,7 +32,7 @@ The first thing they did, that I really felt helped them a lot, was to draw thei
 
 - There’s a couple of (very cute, little) dragons over there to the left, did you see them? They indicate stuff that scares us a bit, things that we know little about or things that we know that we will struggle with.
 
-  [Work in progress means that this is the branch of the mindmap that we work on. Green circle means that it's done. And completely Done.](http://codebetter.com/marcushammarberg/files/2013/08/Screen-Shot-2013-08-12-at-13.25.49-.png)](http://codebetter.com/marcushammarberg/files/2013/08/Screen-Shot-2013-08-12-at-13.25.49-.png)
+  [Work in progress means that this is the branch of the mindmap that we work on. Green circle means that it's done. And completely Done.](http://codebetter.com/marcushammarberg/files/2013/08/Screen-Shot-2013-08-12-at-13.25.49-.png)](<http://codebetter.com/marcushammarberg/files/2013/08/Screen-Shot-2013-08-12-at-13.25.49-.png>)
 
 - Work in progress means that this is the branch of the mind map that we work on. Green circle means that it’s done. And completely Done.
 
@@ -68,28 +68,28 @@ The next thing we implemented was the actual board that the team uses to visuali
 
 Here is how their board looks right now:
 
-[This team uses a board built around priority filters.  Only 3 items are priority 1 and hence given our attention up to our capacity.](http://codebetter.com/marcushammarberg/files/2013/08/IMG_4021.jpg)](http://codebetter.com/marcushammarberg/files/2013/08/IMG_4021.jpg)This team uses a board built around priority filters.
+[This team uses a board built around priority filters.  Only 3 items are priority 1 and hence given our attention up to our capacity.](http://codebetter.com/marcushammarberg/files/2013/08/IMG_4021.jpg)](<http://codebetter.com/marcushammarberg/files/2013/08/IMG_4021.jpg)This> team uses a board built around priority filters.
 Only 3 items are priority 1 and hence given our attention up to our capacity.
 
 - Done – these are things that the team have completed. There’s no more work to be done on these
-- Priority  1 – these items are of the highest priority and hence the things that we work on right now. Haha – just imagine if we would work on something that wasn’t highest priority. That would be so stup… now wait – that happens a lot…
+- Priority  1 – these items are of the highest priority and hence the things that we work on right now. Haha – just imagine if we would work on something that wasn’t highest priority. That would be so stupid… now wait – that happens a lot…
   It’s limited to the capacity of the team and right now the team is experimenting with using 3 items as their WIP ([Work in process](http://en.wikipedia.org/wiki/Work_in_process)) limit.  This is done to further enhance their focus on the work at hand, but also has a positive effect on the lead-time, as [Littles law](http://en.wikipedia.org/wiki/Little's_law) teaches us.
-- Priority 2 – these are the items that we will be working on next. It’s urgent and everything, but we don’t have capacity for it right now. We allow for six items in this column, twice the capacity of our prio 1 items.
-- Priority 3 – are items that we think that we will work on next. These stand a big risk of being down prioritized as we close in on moving stuff up to prio 1.
+- Priority 2 – these are the items that we will be working on next. It’s urgent and everything, but we don’t have capacity for it right now. We allow for six items in this column, twice the capacity of our priority 1 items.
+- Priority 3 – are items that we think that we will work on next. These stand a big risk of being down prioritized as we close in on moving stuff up to priority 1.
 
-Since we have limited the Prio 1 items to our capacity (of 3 items in this case) it means that new work cannot be started until a work item is completed and move into Done. We can then *pull* in a new item from Prio 2 (or maybe 3 or something else that was more important).
+Since we have limited the priority 1 items to our capacity (of 3 items in this case) it means that new work cannot be started until a work item is completed and move into Done. We can then *pull* in a new item from priority 2 (or maybe 3 or something else that was more important).
 
-In fact this show that prioritization is tightly coupled to the time that we make the prioritization desicion. The question is really: “what’s most important *now*?” rather than “can you create a list of all items in prioritized order?” Who cares if an item is no 14 or 15 on that list. Things will have changed when we’re about to pick those up anyway. Don’t lock your business agility and opportunities into a long backlog that’s hard to change.
+In fact this show that prioritization is tightly coupled to the time that we make the prioritization decision. The question is really: “what’s most important *now*?” rather than “can you create a list of all items in prioritized order?” Who cares if an item is no 14 or 15 on that list. Things will have changed when we’re about to pick those up anyway. Don’t lock your business agility and opportunities into a long backlog that’s hard to change.
 
 This leads the team towards another goal: smaller items. The faster we can complete the items the more prioritization opportunities we get. Selecting new stuff to work on every 3 months is scary and causes a lot of discussions. Getting a new opportunity twice a week does not. And we decide the size of each item.
 
-We don’t really care about the order of the items in the column. There’s items that we work on, and the rest. That we might start work on later. I wouldn’t be surprised if the priority 2 and 3 columns will be just “Not prio 1″ later for this team.
+We don’t really care about the order of the items in the column. There’s items that we work on, and the rest. That we might start work on later. I wouldn’t be surprised if the priority 2 and 3 columns will be just “Not priority 1″ later for this team.
 
 ## Daily standup
 
 And now finally the new standup question I promised at the outset. At our daily standup we, as a team, ask ourselves only one question:
 
-> What are hindering us from completing the prio 1 items today?
+> What are hindering us from completing the priority 1 items today?
 
 (You can see this question, in Swedish, under the Priority 1 column on the board above).
 

_posts/2018-11-09-bash-script-to-add-files-to-all-repositories-in-an-organisation.md

@@ -1,6 +1,6 @@
 ---
 layout: post
-title: "Bash script to add file(s) to all repositories in an organisation"
+title: "Bash script to add file(s) to all repositories in an organization"
 author: "Marcus Hammarberg"
 date: 2018-11-09 14:10:45
 tags:
@@ -33,7 +33,7 @@ My game plan was pretty easy:
 
 ### Create a static license file
 
-I went to [Choose A License](https://choosealicense.com) , picked an [appropiate license](https://choosealicense.com/licenses/mit/) and create a file out of that text. I ensured to update it with our company name.
+I went to [Choose A License](https://choosealicense.com) , picked an [appropriate license](https://choosealicense.com/licenses/mit/) and create a file out of that text. I ensured to update it with our company name.
 
 ### Clone all repository
 
@@ -62,7 +62,7 @@ That was good because that meant that I understood the second part much easier:
 * That lets us load that barfed json that `curl` command gave us.
 * We loop over that array of results, i.e. the repositories
 * For each (`.each { ... }`) we simply do a `git clone` and use the value in the `ssh_url`
-  * That actuall didn't really work for me so I changed it into `clone_url`
+  * That actually didn't really work for me so I changed it into `clone_url`
 
 All in all I ended up with this script:
 

_posts/2018-12-03-board-visualisation-tips.md

@@ -1,6 +1,6 @@
 ---
 layout: post
-title: "Board visualisation tips"
+title: "Board visualization tips"
 author: "Marcus Hammarberg"
 date: 2018-12-03 21:09:17
 tags:
@@ -38,7 +38,7 @@ Do you see a common theme with all these bullets? They are questions. Because th
 
 Since you create your own board (like a great Jedi) you also can change it. No, wait; you *should* change it. Make it fit your world, your work and your workflow. The closer to reality it is the more close to reality your improvements will be too.
 
-Start with something and tweak it as you go. I always suggest starting by drawing it with a marker on a whiteboard. Not with tape or not as an electronic tool. I've seen very small hinderances or annoyances of making change lead to very strange workflows a few months later.
+Start with something and tweak it as you go. I always suggest starting by drawing it with a marker on a whiteboard. Not with tape or not as an electronic tool. I've seen very small hindrances or annoyances of making change lead to very strange workflows a few months later.
 
 Change the tool to fit your work.
 

_posts/2018-12-12-busy-dentists.md

@@ -10,7 +10,7 @@ tags:
  - Kanban
 ---
 
-When I introduce agile I do that through a nice little quandrat originally from the [This is Lean](https://thisislean.com/) book by [Pär Åhlström](http://parahlstrom.com/) and [Niclas Modig](https://twitter.com/leanonmyself), and visualized by [Håkan Forss](https://www.marcusoft.net/img/thisIsLean.png). I've [wrote about it here](https://www.marcusoft.net/2017/02/comments-on-board-practices-6.html). This post will only focus on the top left triangle - where we focus on maximizing resource utilization.
+When I introduce agile I do that through a nice little quadrant originally from the [This is Lean](https://thisislean.com/) book by [Pär Åhlström](http://parahlstrom.com/) and [Niclas Modig](https://twitter.com/leanonmyself), and visualized by [Håkan Forss](https://www.marcusoft.net/img/thisIsLean.png). I've [wrote about it here](https://www.marcusoft.net/2017/02/comments-on-board-practices-6.html). This post will only focus on the top left triangle - where we focus on maximizing resource utilization.
 
 But I've noticed that personal stories sticks better and I have used a story about my dentist to show an example of a setting that focuses heavily on the resource utilization.
 
@@ -48,7 +48,7 @@ This is what the second part of the story is about
 
 ## Part II - the callback
 
-Torbjörn fixed my tooth in 2-3 pretty advanced treatments and I was then asked to schedule a callback and checkup about a year later. When a year had past, one of these secretaries called me and gave me a timeslot, just a month from the time she called me, in September.
+Torbjörn fixed my tooth in 2-3 pretty advanced treatments and I was then asked to schedule a callback and checkup about a year later. When a year had past, one of these secretaries called me and gave me a time slot, just a month from the time she called me, in September.
 
 Sadly I was out of town that day and asked for a later slot. She sighed and started that same flipping-through-pages-of-the-booking-calendar again; "Well, the next available slot is ... in ... December 5. 1130-1145. It's just a short check-up."
 
@@ -59,8 +59,10 @@ But sure enough, my observations since last time was correct, they all cheerfull
 They proudly told me that there was a waiting list for waiting. You could go on a list that they started to call through if one dentist got a cancellation, due to sickness, for example. "Then we can quickly call these people", she pointed to a list with about 30 numbers, "and quickly fill that empty slot again."
 
 I also overheard, more than one, calls that went like this:
-Secretary: "Hi... Oh, it's broken in half? Ouch - that sounds painful. Well... sadly, we are fully fully booked. The next timeslot is ... next Thursday. Can you come in around 0745?"
-At this point, Torbjörns nurse, came out, moved me into the chair and Torbjörn cheerfully entered. He snapped 2-3 x-rays, looked at them for about a minute and I was on my way. I was cured!
+
+Secretary: "Hi... Oh, it's broken in half? Ouch - that sounds painful. Well... sadly, we are fully fully booked. The next time slot is ... next Thursday. Can you come in around 0745?"
+
+At this point, Torbjörn's nurse, came out, moved me into the chair and Torbjörn cheerfully entered. He snapped 2-3 x-rays, looked at them for about a minute and I was on my way. I was cured!
 
 ## Reflections on part II
 

_posts/2018-12-14-make-a-copy-of-github-repo---the-script-way.md

@@ -45,7 +45,7 @@ Let’s say that the template repository is called `marcusoft/salt-jsfs-reactsta
 
 1. Open the terminal in any folder with a git repository (it can be an empty one, that you create using `git init .`)
 2. Create the repository using `hub create marcusoft/salt-jsfs-reactstarter-vt19`
-3. You will need to login in with the credentials you access the saltsthlm organisation
+3. You will need to login in with the credentials you access the saltsthlm organization
 4. Now make a “bare” clone of the template repository `git clone --bare https://github.com/marcusoft/salt-jsfs-reactstarter`
    1. By adding a flag `--single-branch` we can ensure that we only copy the master branch (which is default, or by add a name). This what we need for the most cases and hence the script (below) has this set.
 5. Now do: `cd salt-jsfs-reactstarter.git`
@@ -97,7 +97,7 @@ rm -rf aTemporaryPlace
 cd $cwd
 ```
 
-And then run it with `bash cloneRepository.sh organization orginal-repo new-repo`, for example `bash cloneRepository.sh marcusoftnet salt-jsfs-reactstarter salt-jsfs-reactstarter`.
+And then run it with `bash cloneRepository.sh organization original-repo new-repo`, for example `bash cloneRepository.sh marcusoftnet salt-jsfs-reactstarter salt-jsfs-reactstarter`.
 
 ## Summary
 

_posts/2019-01-04-kanbanstats-ii-filter-the-process-chart-.md

@@ -31,7 +31,7 @@ Also, I’m going to add this filtering-capability, so that we can filter on oth
 
 ## Setting it up
 
-Just for clarity, I will do this as a separate tab calculating lead times “Leadtimes with filters”. I created it by making a duplicate of the “Lead time calculations”-tab. I kept the chart (that got copied) that is already showing the data in a nice way, but I changed the title to “Filtered lead times” to know what was what.
+Just for clarity, I will do this as a separate tab calculating lead times “Lead times with filters”. I created it by making a duplicate of the “Lead time calculations”-tab. I kept the chart (that got copied) that is already showing the data in a nice way, but I changed the title to “Filtered lead times” to know what was what.
 
 To get some more data to filter on I added a new column, copying over the “Size”-column from the “Raw data”-tab.
 
@@ -129,7 +129,7 @@ Ok - less philosofy and more doing.
   - The URL can be picked up by showing the filter (Data -> Filter views-> Estimated to S for example). See how the URL in the address bar changed to have a `&fvid=` at the end.
     Select the whole address and use that as the first parameter
   - The name is just a name for the filter `Only Size S` for example
-  - The full forumla will look something like `=HYPERLINK("https://docs.google.com/spreadsheets/d/1IinrY-3_wEQUwHucDgHsCMUkFhLOqlBzXkZfc1yLBBI/edit#gid=918968025&fvid=2092689969", "Only Size S")`
+  - The full formula will look something like `=HYPERLINK("https://docs.google.com/spreadsheets/d/1IinrY-3_wEQUwHucDgHsCMUkFhLOqlBzXkZfc1yLBBI/edit#gid=918968025&fvid=2092689969", "Only Size S")`
 - Repeat for all views.
 
 An user can now click one of those links and get the chart filtered.
@@ -147,7 +147,7 @@ I need to show to export the chart as a picture as well, because that could be h
 
 ## Summary
 
-Ok that last part was a bit dissapoiting. Let's move to another simpler world in the [next post](https://www.marcusoft.net/2019/01/kanbanstats-iii-throughput.html) where we will calculate throughput; how much gets done per time unit.
+Ok that last part was a bit disappointing. Let's move to another simpler world in the [next post](https://www.marcusoft.net/2019/01/kanbanstats-iii-throughput.html) where we will calculate throughput; how much gets done per time unit.
 
 In this post we have given the user a bunch of opportunities in how to filter the data and have the charts update to reflect the filter.
 

_posts/2019-01-04-kanbanstats-iii-throughput.md

@@ -63,13 +63,13 @@ I put the unique months in column F and the unique weeks in column H, for now.
 
 ## Appreciation break
 
-Let me just stop and appreciate the amazing Google Sheet for awhile. Many things in the application are mindblowing but right now I wanted to send a special love for the `C2:C` syntax.
+Let me just stop and appreciate the amazing Google Sheet for awhile. Many things in the application are mind-blowing but right now I wanted to send a special love for the `C2:C` syntax.
 
-Take all rows in the C-column, starting on row 2. You can't do that in Excel. I love that. Without it, I would either get the heading or update this formula everytime new rows are added.
+Take all rows in the C-column, starting on row 2. You can't do that in Excel. I love that. Without it, I would either get the heading or update this formula every time new rows are added.
 
 Thank you, Google!
 
-## Round'em up!
+## Round'em up
 
 It's now, thanks to the copying of all the rows in columns A:D, pretty easy to count the number of items finished per month: `=COUNTIF(C2:C, F2)`
 
@@ -95,7 +95,7 @@ Pretty soon you'd want to filter this data as well... I will leave this as an ex
 
 But just to whet your appetite, here's a chart showing the throughput per week and estimated size.
 
-![Througput per estimated size](/img/ThroughputPerEstimatedSize.png)
+![Throughput per estimated size](/img/ThroughputPerEstimatedSize.png)
 
 ## Summary
 
@@ -105,7 +105,6 @@ Pretty happy how this turned out, the only thing is that I now realized that I n
 
 In the next post, we will do something more advanced and start to measure the queue lengths. It will probably be two posts since we need to update the raw data with items that are not finished.
 
-
 ### The links
 
 [My sheet is open](https://docs.google.com/spreadsheets/d/1IinrY-3_wEQUwHucDgHsCMUkFhLOqlBzXkZfc1yLBBI) for anyone to read and, if you want to, make a copy of. If you use it and find it useful - please throw me an attribution or a nice thought. If you make something awesome out of it - please let me know so that I can learn more about this.

_posts/2019-01-04-kanbanstats-simplify-process-stats---get-started.md

@@ -125,7 +125,7 @@ Ok – the chart is thankfully a bit simpler to create, now that we have all the
    3. Select the “Lead time” series and set the “Point size” to 7 px and select a good shape
    4. Select the “Lead time” series and select “Custom” which will pick up our Slug. It will display the value when you hover over it. You can remove the data label if you find it cluttered. You can always enable it again later.
 6. Select Legend and put the legend at the bottom.
-7. You can fiddle around with gridlines for the axis to make it more readable, to your heart's content.
+7. You can fiddle around with grid lines for the axis to make it more readable, to your heart's content.
 
 When that is done you should have something that looks like this.