Tag: agile

19 January 2015 / Agile & Scrum
Amazing news! Craig Larman is coming to Belgium

Who is Craig Larman? Craig Larman is the co-creator of LeSS (Large-Scale Scrum) with his friend and colleague Bas Vodde. He serves as an organizational design consultant, with emphasis on introducing LeSS for very large and multisite product development (often, embedded systems, telecommunications, or investment banking), and coaching executive teams to succeed with larger enterprise-level agile and lean methods adoption. He is the author of...

14 May 2014 / Agile & Scrum
New WisP session: The SAFe release planning game

Our next session to be announced for WisP 2014 is the SAFe release planning game. This interactive workshop, based on a simulation game, is designed to give participants insights in how to do release planning across several teams working on the same product or value stream. The session provides some background about SAFe and the concept or Agile release trains, to understand some patterns of having several...

10 June 2013 / Less is More
Software craftsmanship vNext

Last week, on 30 and 31 May, I attended the I T.A.K.E. unconference in Bucharest, Romania. I was asked to facilitate a workshop there and chose to combine two of my personal favorite coderetreat sessions into one even more challenging session: TDD as if the baby meant it. I will write about this session and some of the feedback I got on this soon, so...

20 May 2013 / Agile & Scrum
Tooling: How to manage your to-do’s over multiple projects?

In previous article “The Product Owner Iteration – Limit Your WIP” I described one way for a person to manage his/her work on a 2-weekly basis and avoid generating waste in the system. This time I will give you a simple spreadsheet to support you with: -       Requirements management that avoids generating waste -       Team dependency management -       External dependency management -       Prioritization & impact...

13 May 2013 / Agile & Scrum
The Product Owner Iteration – limit your WIP

As the teams are having 2 week iterations to build solutions to problems, the Product Owner has 2 week iterations as well to produce just enough new detailed input for his/her team as the team can handle within a single iteration. The rest is all about communication, collaboration and transparency towards the results and planning of the team. Acknowledge your interest to the team Having...

6 May 2013 / Agile & Scrum
Most common mistakes in scrum ceremonies 7/7: general scrum pitfalls

With great power comes great responsibility You can’t expect a team that is used to working in a command and control environment to suddenly make the switch to becoming a self-organized team without any guidance. All self-organization in nature happens within boundaries. Just like in nature, we will need to set boundaries when we help teams in becoming self-organizing. We need to show them ways...