When implementing agile software development in teams, context seems one of the least noticed factors. That’s remarkable as it is one of the most important aspects to consider when adopting agile methods. With a series of posts I want to shed some light on that topic, looking at context in agile software developments from different angles. Contexts that are relevant and worth to consider when starting agile software development are organizational culture, team setup (distributed or collocated, skill levels, language and cultural differences) and experience in agile methods and principles (maturity).

There is always a debate regarding the ideal size for a scrum team. The scrum guide recommends seven members plus two or minus two as the ideal number. There seems no consensus among the agile community regarding what the best size of a team may be. However, one issue that people are in agreement with is that smaller teams are more functional and productive. A quote from the scrum guide states that “small enough to remain nimble and large enough to complete significant work within a Sprint” The question then is, how small is small? This will depend on a number of factors.

Scrum is a simple and flexible software development methodology or framework. Scrum framework introduces alternatives to traditional project management systems such as Waterfall or Sequential development. In scrum we only have three roles; product owner who represents the clients or users, the scrum master who is the silent leader and the team. From my experience, additional roles are not needed since they don’t usually bring extra benefits. The Scrum framework covers all the necessary aspects for successful software and product development. Instead of additional roles it is possible to have a product owner team, where the different product owners cover different areas of the product. Depending on the degree of innovation and uncertainty in your project, this might be even …

Benefits of Adopting Scrum for Software Development Read more »