Hexaware Acquires SMC Squared, a Leader in Building Global Capability Centers-Rolls Out GCC 2.0 Service Line. Learn More
This website uses cookies. By continuing to browse the site, you are agreeing to our use of cookies
Cloud
June 19, 2018
Project/ product development teams might be doing scrum religiously by having fixed-duration sprints, following ceremonies without fail, having time boxed stand-ups, creating artifacts as prescribed but, these may not be enough for being agile. A team that focuses too much on ‘Scrum as a process framework’ emphasizing on ceremonies and events in letter-and-spirit, rather than following it with the intention of achieving agility; often fails to achieve the desired end results. It requires a team to engage in a disciplined approach throughout the product/ project delivery lifecycle to enhance its agility, productivity, and product’s quality as well as to optimize delivery time and efforts. It has to be a consistent endeavor from all the stakeholders like product management group and product engineering team (as agile practitioners) to bring agility by means of continuous improvement.
Agile Scrum is just a framework which needs to be followed within its operating context. A team should not get trapped between the framework’s boundaries. Following are some of the Scrum smells (anti-agile/ dysfunctional scenarios) which indicate that a team is trapped between the processes…
Scrum is definitely the basic and starting framework. But to succeed with agile, it works well when applied effectively with other agility practices.
Product/ project team should make a multi-faced approach to be agile. They can start agile transformation by following Scrum and then slowly moving to agile maturity with inspection & adaption, adapting suitable agile practices and investing in right tools & technologies.
Every outcome starts with a conversation