Company Culture
Agile transformation implies a culture change and Culture change refers actually to a change of the mindset. We simply cannot change the culture by talking about values, or printing the values together with the company’s vision in big letters at the front door and just by reading that everyday doesn’t change anything until and unless we actually implement changes and make that habit.
Every Organizations have different needs, requirements and constraints to achieve their goal, to become successful. We can’t blindly follow the prescriptions, all details practices need thorough analysis and one has to drill through those for better decision. for instance no one can follow the practice of defining velocity for a team from another team, it should be empirical process. Team themselves should be able to define their average velocity and capacity depending upon the past achievements. Team size is also standard defined by Scrum.org but we can have our own team size depending upon the nature of work. Having more than nine members requires too much coordination and large Development Teams generate too much complexity, apart from this some organization might have team of 10 developer. Other side of the etam size, Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver as required.
Culture is Journey not a Destination
Every office has to set their culture by practicing different things like celebrating Birthdays of employee or organizing some fun activities, team buildings and sometimes celebrate happy hour monthly or quarterly. These events might seems small effort from the company itself but left big impact behind. Team bonding is increased and team member feel free to discuss on anything while working. Communication level increases.
Well what about Agile and Scrum then? how does that fit in your organization? to answer these questions, it really depends on your organization and type of projects you are working on. You need to choose right fit for your organization, in what mode project management should be done. whether Scrum, Kanban, traditional or hybrid methodology would work, you really need to think that. Not every project can be managed by Agile and Scrum Methodology.
Basic Tenants to Agile Culture
The essence of agile methodology is the practice that promotes continuous iteration of development and testing throughout the software development life cycle of the project. These are the basic habitat of Agile development methods.
- People Take Priority Over Process
- Dynamics Rather Than Documents
- Collaboration Rather Than Cascading
- Adaptive Rather Than Prescriptive
- Leadership rather than Management
