- RSS Channel Showcase 2262343
- RSS Channel Showcase 4968550
- RSS Channel Showcase 4920545
- RSS Channel Showcase 1406972
Articles on this Page
- 10/22/08--01:16: _Perspective of Retr...
- 02/06/10--02:58: _Emo-lines
- 05/04/11--05:46: _Micro agile
- 11/17/11--03:44: _Guest blogging at T...
- 03/30/13--05:13: _Retrospective using...
- 05/03/13--06:35: _Ett upplägg för en ...
- 01/30/14--00:06: _Team barometer (sel...
- 09/01/14--01:44: _Facilitating from t...
- 10/22/15--12:22: _Slides från session...
- 05/01/17--10:54: _Constellation retro...
- 05/14/17--21:00: _How to facilitate a...
- 03/12/18--13:28: _The three states of...
- 10/22/08--01:16: Perspective of Retrospective
- 02/06/10--02:58: Emo-lines
- 05/04/11--05:46: Micro agile
- WIP limit
- Regular retrospective
- 11/17/11--03:44: Guest blogging at TV4 Digital Media
- 03/30/13--05:13: Retrospective using Jimmy Cards
- 05/03/13--06:35: Ett upplägg för en heldags affärsplanering
- 01/30/14--00:06: Team barometer (self-evaluation tool)
- 09/01/14--01:44: Facilitating from the Back of the Room at Spotify
- 10/22/15--12:22: Slides från session Agila Arbetsmetoder @ SAST Q20
- 05/01/17--10:54: Constellation retrospective
- 05/14/17--21:00: How to facilitate a lightweight project retrospective
- 03/12/18--13:28: The three states of working agreements
Scrum received some criticism today in Computer Sweden. The article featured an interview of Ken Schwaber and our guy Henrik Kniberg. Tobias Fors from Citerus was giving the comment that Scrum lacked support for retrospective. I am not sure if he was quoted correctly.
I am in the belief that Scrum has three roles, three artefacts and three meetings. Of the latter, there is one you should never skip.
If you coach a scrum team but you're not around to observe them during the sprint, how do you know how they felt about it?
When we develop using agile principles we have learned to "do the simplest thing that can possibly work". What happens if we apply this thought to agile methodology itself?
In my experience the three most important components in a successful application of agile methods are:
I have just, as a guest blogger, posted a new post at the blog owned by the development team at TV4 Digital Media; “Några övningar vi gjort under retrospektiven”. It´s a post, in swedish, describing a few retrospective exercises we have done during the last sprints. I’m contracted by TV4 Digial Media as an Agile read more
I had taken on to facilitate a retrospective for my colleagues’ team. They wanted a different retrospective than the usual. So we borrowed Crisp’s office and used Jimmy Cards! The group was around 15 persons from two teams. They all knew each other well which I believe is crucial as the questions on the cards can read more
Nyligen så hjälpte jag till med att planera och facilitera en affärsplanering hos en kund. Då jag tycker både utfallet och genomförandet var väldigt bra så kommer här en beskrivning av vad vi gjorde och de olika övningar vi hade. Det var en relativt stor grupp som samlats föra att genomföra den årliga affärsplaneringen, vilket read more
Sometimes it’s hard for a team to know if they get tighter and better as a team over time. This is a tool that allows a team to learn just that. Team barometer (self-evaluation tool) in a nutshell The barometer is executed as a survey in a workshop. The survey consists of 16 team characteristics, read more
Last week Jimmy Janlén and I held a shortened version of our course Training from the Back of the Room for our former colleagues at Spotify. Actually it is not “our” course, but Sharon Bowmans. It’s based on her books about how create a more engaging learning experience in the class room, especially when training read more
Otroligt kul att se hur många som fick plats i ett konceptrum i Aula Magna under våra presentationer under SAST Q20! Vi pratade först om kontinuerlig förbättring och sedan om working agreements. Slides hittar du nedan. Kontinuerlig förbättring Working Agreements På Crisp har vi en hel del gratis material och guider, bland annat en Toyota read more
This is a strong retrospective for bringing issues up to the surface. Instead of just one person expressing an issue as a positive or a negative, the whole team feedbacks about the importance of the issue. The team then decides which issues to tackle. The retrospective also exposes issues where there is not common view, read more
Large group retrospectives are long, large, unwieldy facilitations. So much so that they’re typically done only at the end of a project. Holding a 1-2 day retro every few weeks for a large project is neither practical nor responsible, but continually improving the project is also important. So, how do you hold light-weight retrospectives for large read more
You may have read about this elsewhere, but a recent event led me to write this. I feel that the working agreements concept is not given the attention it deserves. Working agreements are about making your culture explicit. It is desirable to have them visualised on your Scrum board as a constant reminder. Question is, read more