This is one of the most inspiring and efficient books I’ve ever read. Agile mindset lives on every page of the book. The publication touches many PM areas and puts an agile cover on them. This might be a challenge to finish reading the book with no understanding the agile approach in IT projects. Agile thinking is revealed sometimes explicit, sometimes more subtle throughout the whole content.
The cooperation with external people may be a challenge for agile teams. These people are often experts working as a smaller or bigger part of an agile team. As long as an expert is not a full-time and dedicated team member involved in development lifecycle, this is a challenge to organize common work in a consistent way. We consider factors making the cooperation inconvenient. There are also produced common working agreements supporting organization of mutual collaboration.
Companies are getting bigger, projects do so, and a need of scaling grows. The purpose of this post is focusing on aspects of building agile scaling scheme in an organization. There are taken into account communication and integration aspects. These aspects are often not properly executed or neglected at all. They are in fact inevitable factors in achieving scaling goal.
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.