It is not a secret that companies are always looking for better ways to handle their software development needs to avoid projects dragging for long periods. Agile software development is one of the most preferred ways of software development due to its dynamic development nature, whereby, requirements and solutions evolve during the entire development process. The emphasis on collaboration between different self-organizing and cross-functional teams is at the core foundation of this method. Characteristics of a good agile development team When selecting a team for agile software development, a company should ensure that at a minimum, they meet the following factors.

What is the first thing to do when working as a Scrum Master with a new team? Whether the team is experienced in agile software development or not, it is important to create a basis that all future collaboration is build upon. This is the key to avoid misunderstandings based on assumptions or a lack of clarification which will affect all future collaboration and in worst case might damage trust. Therefore I believe a simple session or exercise should be the first step whenever start working with a team: Set expectation and boundaries! This post focuses on expectations as the basis for collaboration as Scrum Master with your team. Make use of your Scrum Master toolbox in order to keep …

The First Thing To Do As Scrum Master With Your Team Read more »

All of you who are familiar with the Agile Software Development Manifesto, this post seems familiar. Actually the inspiration for it comes from the Agile Manifesto, which says: Customer collaboration over contract negotiation My inspiration for this post actually comes from that. Only that I don’t want to limit collaboration to contracts. Collaboration is something that I find usefully in any part of software development, even outside of software development. But let’s focus on work space in this post. Whenever I worked in an collaborative environment, I enjoyed it. It wasn’t that important what the subject of the project was or which methodology or project management framework was used. What brought the joy was collaboration with colleagues, clients or other …

Collaboration vs Negotiation Read more »

Individuals and Interactions over Processes and Tools. This statement is part of the agile manifesto. It highlights the importance of people and communication within the project. The key to understanding this statement is understanding the meaning of the word over. It may seem simple yet many people get it wrong. The word over is repeated four times in the Agile manifesto. The word over in this context means that while processes and tools are important in software development, individuals and interactions are more valued. This doesn’t mean we do away with the tools and processes. Actually we cannot work without them, but we should put more emphasis on the people and effective communication rather than following rigid processes. Developers love …

Unfold The Agile Manifesto – Part 2 Read more »

In IT as well as other areas communication or the conveyance of information is an important factor. As you might have experienced yourself, communication in general is an error-prone thing. Misunderstandings and perceptions occur regularly and have an impact. Wrongly understood information could lead to unnecessary costs for your organization and frustration amongst staff.