Bugs and errors are part of the reality of building complex software. Good Scrum teams know how to handle such bugs and ensure high quality standards to their frequent releases.
If you are part of a Scrum team, or worse, a Scrum Master, you sometimes have to explains to muggles what is this term referring to.
Helping teams, from a Scrum Master point of view, is not always easy. Especially when it gets into a technical jargon.
I’ve been through a few interviews for Scrum related jobs. Some were memorables. Some others not. Some were just weird!
There are numerous ways to save costs during a software creation lifecycle. Some better than others.
I recently met with one of my ant friends, and he gave me good insights about ants’ major events of the few last years. — A few years ago, an event was organized among ants. It was held in the Amazon forest. A few hundreds ants attended this event. The main topic of this meeting was to discuss about the recent rise of the ‘Queeny’ approach recently adopted by a few millions colonies worldwide. This ‘Queeny’ approach and process...
I read a lot of articles during a week. Some in the morning, during breakfast or on my way to the office. Some during the lunch time, while having a sandwich or a soup in front of my computer. Some other interesting readings at night, while reviewing my blog roll posts or summarizing some Twitter channels or Twitter past favorited items. I rarely comment or reply to these articles. I can agree, disagree or just be in a neutral state of mind in...
When you enter a room full of developers, and it is dead silence, you can never say if this is a good or bad situation. Silence can mean a lot of things for a developers team.
Conventions are always popular events. You can attend good sessions, listen to great speakers and most of all… collect swag!
Maintaining a good and clean product backlog is a tough job. There are always a few items that get included and reach the sprint planning session that… shouldn’t be.
Sprint reviews are always interesting events awaited by several people in a company. We can sit together and inspect the latest app increment status.
Several people ask how is it possible to deliver large and complex system with Scrum. I usually answer that the best way to deliver large and complex system is to start with small and simple versions at first. Scrum encourage such approach. Here is my own imagery creation on such topic: