Here is my view on the 2017 changes in Scrum Guide proposed by Ken Schwaber and Jeff Sutherland and what they mean for all people using Scrum.
More and more companies decide to establish distributed teams. This is more of a requirement of our times. Effective communication in a distributed team can be a real challenge. However, it is possible to arrange it so that the work will proceed very smoothly.
Are you new in IT industry and scared of some unknown phrases and weird slang? Or you have longstanding experience as a software developer but you want to refresh your knowledge? All reasons to learn something new are good! Let's see what the most common misunderstandings in software development world are these days. All myths needs to be uncovered! At the beginning let's talk about User Story.
Agile retrospective is from my perspective the most important scrum event. The team reflects on how everything went and then decides what changes they want to make in the next iteration. The Agile manifesto states: "at regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." Let’s start from theory in case some of you have never attended one...
A lot of teams in Kainos are using Jira for their development process management and defects management. Jira is very flexible tool, you can have custom process flow and add custom fields to reflect your business needs. Out of the box you will find also simple reports on your team performance. But what if you would like to track some development metrics that are based on custom fields? Or you have many teams and you’d like to aggregate the data and automatically generate reports for all of them with the same format?
When you first hear about Scrum, you will hear about certain meetings, roles and of course, the idea of Sprint. You will also be led to Agile Manifesto, which is the fundamental for Scrum. This is important knowledge which touches the technical and organisational side of Scrum