In the previous post about distributed scrum teams we have been talking about challenges, let’s focus on the solutions. There is no overall solution; it is a never-ending journey to try doing things better step-by-step in an agile way. Let’s start with the easy things; hardware and software. Don’t be a cheapstake; spending money on these is a …
Items on the left are valued more according to the Agile Manifest. Let’s analyze each of them to find out why remote teams are facing tough challenges. Individuals and interactions over processes and tools Lack of face to face communication Offices in a different timezone Cultural differences High-overhead processes Synchronous communication Working software over comprehensive …
… and here we are; the last scrum event in the Sprint. So what is it about? “The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.” – Scrum Guide Seems to be easy and straightforward but the whole …
One of the last events held at the end of the sprint. It is about to inspect the Increment and adapt the product backlog. According to Scrum Guide: “During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog …
A regular meeting held every day; easy to misunderstand and overlook its purpose. Scrum Guide: “The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours. This optimizes team collaboration and performance …
Sprint planning. The beast. The most heaviest event. Let’s check what Scrum Guide recommends: “The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team. Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. …
What does the Scrum Guide say? “Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. …
I would like to analyze the scrum events in the upcoming posts. Scrum guide is taken as an example, so in each post I am planning to explain that first then I’ll describe how the theory can be applied into practice and what kind of challenges we had to face. The following scrum events will …
We had a plan, we made the plan but we weren’t able to follow due to various reason. It turned out after 6 months that it simply doesn’t work. Product Owner does not want us to sit on already developed features, business want them as soon as possible. No release cycles, no special sprints anymore, …
Scrum guide doesn’t implicitly describe how releases should be performed and doesn’t define the interaction between scrum events and release planning. Actually, the latest update contains more references to the release for instance: explicitly referring to CI: the purpose of each Sprint is to deliver Increments of potentially releasable features. This Increment is usable, so a Product …