The daily scrum is the heartbeat of a scrum team.As Scrum is a compression algorithm for organizational and engineering best practices, this meeting is not a Scrum invention but it is considered an Agile best practice independently from the adopted framework. It is also known as StandUpMeeting (1993 Jim Coplien), “daily scrum” (1997 Ken Schwaber), […]
You are browsing archives for
Tag: agile
Spikes 102
In my previous article “Spike 101” I introduced the concept of Spike and it’s general use in Agile. In that article we saw that: Spikes are investigation activities -e.g: research, design, investigation, exploration, prototyping- to gain the knowledge to solve a problem. As Scrum doesn’t prescribe any particular type for Backlog Items, it is up […]
Spikes 101
Scrum is often described as a very prescriptive framework despite this is not the case. Take for example the various type of backlog items that we are used to deal with in our favourite backlog visualisation tool. Some work with Epics and User Stories only, others use a mix of Stories and Tasks, others add […]
Stranger things can happen at the end of a sprint
As the end of the Sprint is approaching, usually in the last few hours before demo or even after, some team member decides to rush activities. What for the whole Sprint (1-4 weeks) and surely till “yesterday” wasn’t possible to complete in 1-2 days, suddenly can be finished in few hours, or it must absolutely […]
Update yourself
A manifesto for Scrum adoption in your life. Assuming you already heard about Agile, Scrum, Sprints and Retrospectives. As in any scrum team, the iterative and incremental process culminate in a retrospective, where members receive and elaborate feedback, taking actions to inspect and correct behaviours, remove obstacles, fix issues. If we are in an Agile […]