Workshop Getting More out of Agile and Lean at Goto Berlin 2016
Teams and their stakeholders learn Agile and Lean practices to develop the right products, deliver faster, increase quality, and create happy high performing teams at GOTO Berlin 2016.
Teams and their stakeholders learn Agile and Lean practices to develop the right products, deliver faster, increase quality, and create happy high performing teams at GOTO Berlin 2016.
In my workshops I often play the impediment game with teams. In that game team members discuss impediments that happen during Scrum sprints or Kanban flows, and decide how to deal with them and who should solve the impediment. The "who" is most often "any team member". But in practice I see that teams struggle with impediments, and often expect the Scrum master or a manager to solve them. Let's explore what can be done to have impediments solved by Scrum team members.
The practices in the workshop Getting More out of Agile and Lean will help you to develop the right products for your business and customers, reduce your delivery time, increase the quality of your software, and create happy high performing teams.
In the workshop Valuable Agile Retrospectives for Teams you will practice exercises for facilitating retrospectives in teams.
Conference season isn't over yet. There are several great agile and software development conferences that I will be attending and covering for InfoQ in the upcoming months before the holidays start.
The Software-Centric Systems Conference facilitates the exchange of knowledge and experiences in the crucial and strategic discipline of complex software development.
In this interactive workshop you can practice different exercises from the Retrospective Exercises Toolbox to facilitate retrospectives. You will learn the “what” and “why” of retrospectives, the business value and benefits that they can bring for your team.
Agile teams use product backlogs to manage their requirements. Product owners prioritize the user stories. To enable delivering products with sufficient quality agile teams need to have user stories that are ready at the start of an iteration.
I will be covering the GOTO Amsterdam conference for InfoQ. GOTO Amsterdam is a practitioner-driven enterprise software development conference designed for team leads, architects, and project management and is organized "for developers by developers".
I met Hugo Messer a couple of years ago, when I connected with Bridge Global who started publishing guest posts from me. We talked about working with remote teams to find out that our thoughts on this are quite similar. In this guest post Hugo explores how Scrum can help distributed software development teams.
NO and YES are two simple words, yet practice shows that professionals often have difficulties in using them. Actually it's very easy, certainly when you want to work in an agile way. Dare to say NO when you are unsure if you can do what's requested. When you say YES it means that you will deliver the product, on time with the right quality.
Regularly I get questions if you can measure defects and if you should measure them. The short answer is: You can measure them, and it can have value to do so, but only if you take action. Quality matters, and defects can provide you with valuable information about the quality of your product, but measuring alone doesn't improve quality. You need to dive deeper to have a good understanding and then act upon that.