Varför behöver man ha en retrospective?
Technorati Tags: Scrum, Agile, Implementing Scrum Jag var bara tvungen att lägg upp denna strippen från Implementing Scrum
View ArticleByggstatus med Lavalampor
Technorati-taggar: Team Foundation Server,Continues Integration,X10,Lava lamps Vi håller på att migrera från Visual Studio 2005, Visual Source Safe och CruiseControl.NET till Visual Studio 2008, Team...
View ArticleVisual WIP–work is progressing
Work on Visual WIP is progressing. Lots of refactoring has been done for the last few weeks. I’m trying to move as much as possible of the visuals to xaml files that will be loaded in run time making...
View ArticleScattershot Improvement Lists or Behaviors for Continuous Improvement
It is the end of the sprint and time has come for the retrospective. Scrum Master Jane starts by explaining the objective of the meeting. The retrospective meeting is our time as a team to reflect back...
View ArticleDifferent forces in Scrum and Kanban for the common goal
Scrum and the Kanban method use different forces to achieve this same goal of creating the most possible value over time for the organization by continuously inspecting and adapting the processes and...
View ArticleHow to improve Flow Efficiency with Scrum – #Agile2014 Q&A
Thank you all of you who attended my #Agile2014 session: How to improve Flow Efficiency, Remove the Red bricks! In this, and upcoming posts (part 2) I will answer some of the questions I have received...
View ArticleThe Non-Repetitive Work Fallacy
It is not uncommon to hear people say that software development is non-repetitive work where the work always unique and rarely repeat. It is not uncommon to hear people say that software development...
View Article
More Pages to Explore .....