‘Spikes’ are time boxed periods of research and development used in Agile Software Development environments to research a concept and/or create a simple prototype.
There is a lot of debate about whether to estimate sprint requirements in hours or to leave them in Story Points. Personally, I see pros and cons of both approaches but would use Story Points over hours where/whenever possible.
So, you’ve heard about Agile and Scrum, your company is sold into the benefits, you’ve had your Scrum Master training, you’re good to go… and now you need to set up all of the meetings! This post will give you a simple overview of the Scrum Meetings and some suggestions for how you might like to schedule/run them.
Sprint planning should take place on the first day of the sprint. This session is divided into two parts, the first part is attended by the delivery team and the product manager, whereas the second part is usually only attended by the delivery team.
One of the biggest challenges we’ve faced is trying to balance project work or product development with business-as-usual (BAU) work that can’t necessarily be anticipated – how do you manage the risk of disruption?