This post takes into review Agile Retrospectives Making Good Teams Great book by Esther Derby and Diana Larsen, foreword by Ken Schwaber . The book teaches how to organize and lead retrospectives from A to Z from the conceptual point of view.
The traditional circles and soup technique is performed usually on retrospectives of not successful sprints. The technique could be used for release and project retrospectives as well. Basing on my observations there are very often small successes even in failed sprints. The circles and soup technique does not respect them. I would like to present here my extension to the circles and soup technique which I use at work. I call it multiverse circles because this one introduces the parallel positive universe in addition to the impediments base.
The aim of this publication is to consider usability of estimation in software development context. We will cover here a matter of estimation rather than exact estimation techniques. The consideration has in mind particularly agile environment. I wrote this post basing on my experience and observations. I have worked in various teams with different approaches to estimation. In some teams estimation techniques were changed along with time.
This post is a review of a book for professional programmers. The Clean Coder: A Code of Conduct for Professional Programmers  is the complete title of the book. The book is written by Robert C. Martin (aka Uncle Bob) . This publication is a must to read and being familiar with for professional software developers. All the content has a profound foundation based on the Robert C. Martin’s experience. The author gives guidelines how a professional programmer acts.
This post is a discussion about scope of the Daily Scrum. Scope is considered in terms of meeting duration time, participants and discussion topics. Emphasis is particularly put on discussion topics. The general assumption is following The Scrum Guide™. Scrum is a framework and allows us to suit it for an exact Scrum Team characteristics. We will cover here what is worth to include and what is not on the Daily Scrum meeting.
This article is about agile usability considering agile principles in software development environment. We will try help in finding an answer for a question if agile is a right approach for a project. This post in particular is focused on Scrum framework as an agile method.
One of the challenges of work in a distributed team is sprint planning. In fact every Scrum event is important. I published Challenges of work in distributed teams some time ago which addresses work in distributed teams. This time I’d like to take into account sprint planning because this event tend to be particularly tiring when performed remotely. According to The Scrum Guide™ this is the longest event (except sprint itself) during a whole iteration. In addition to that this one is crucial in order to provide right input into a new sprint backlog. Every minute spent with an online tool make us more exhausted than it would be done on site.
This post is a short review of book Scaling Agile: A Lean JumpStart. The purpose of this book is introducing into scaling Agile using Lean Thinking. In my opinion it is recommended to have at least basic understanding of Agile principles and how they work in practice before diving into scaling area. It is about Agile, not only about Scrum.