![]() ![]() The process in which we were working previously may have had a lot of value, but it can get outdated If things work in a certain way, is there no need to change it? That’s not entirely true, we can always be better. "If it works do not touch it." We demonstrate this phenomenon in the way we code and our team processes.Business objectives end up taking a back seat. When a team is large and the team members have different perspectives of the business, it is easy to lose the big picture and start concentrating on the details.The coordination is centralized and does not give much scope or space for self-organization of the team.Making decisions, reaching a consensus and voicing improvement ideas get harder as the teams get larger. ![]() Large teams can hinder collaboration and communication among members.This blog explores our experiment and how we fared at it. When we began to face this challenge, we decided to split the team into smaller groups called squads. This atmosphere isn’t very conducive to continuous improvement, as our ideas could get lost amidst several voices. In large teams, we try to solve the needs of various facets of the business. ![]() This helps us evidence scenarios which may not be problematic at first, but aren’t always suitable for certain conditions. Agile teams teach us to be reactive to unexpected situations and follow a continuous improvement processes. One such challenge is to retain agile practices that provide actual value, over those that are enforced because a manual says so. Working in a large team presents its own set of challenges, more so when the team is distributed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |