Certified LeSS Practitioner course with Venkatesh Krishnamurthy | 5th-7th October 2018

INNOVATION ROOTS is proud to announce its association with Mr. Venkatesh Krishnamurthy’s company Empirical Coach Pt. Ltd. to deliver the Certified LeSS Practitioner workshop in India. The course will be conducted by Venkatesh Krishnamurthy and will be held on 5th, 6th and 7th October 2018 at Bangalore.

This three-day course covers Large- Scale Scrum (LeSS) in an in- depth format, with its corresponding principles, frameworks and rules. It delivers essential information for the adoption and improvement of LeSS for the existing Product Development Group. Large- Scale Scrum (LeSS) knowledge is essential for the application of Scrum principles in a large-scale context.

This three-day course will teach Participants essential Scrum principles, as well as structural rules and guidelines on how to adopt it during development. Participants will learn LeSS overview, stories on LeSS adoptions, exercises and Q & As. The Course will help participants to enhance the knowledge and applicability of existing Scrum and Agile methods, and sharpen their skills as Scrum Master and Agile Coach. They will eventually gain an understanding on how to manage cross-functional, self-managing teams and play the role of Scrum Master in LeSS.

Mr. Venkatesh Krishnamurthy is an esteemed thought leader and published author, who’s specialized in applying Lean and Agile principles into major corporations and work programs. He’s been personally mentored by luminaries such as Craig Larman and Bas Vodde, and has held leadership positions across Australia, USA, Europe and Asia regarding Agile methods that include: Scrum, XP, Kanban, SAFe and Systems Thinking towards delivering outcomes for customers. He was also involved in the hundreds of experiments, that led to the birth of LeSS. The participants will also get a rare insight into them, during the course.

Click here to register

Improvement Backlog | Glossary

Definition:

An Improvement Backlog lists everything that the organization could do better in its use of Scrum. Scrum development team uses product backlogs, team can use an improvement backlog to track the effort of adopting Scrum in organization.

To list out few Items that can make to improvement backlogs are increase adoption of test automation, enable teams to implement continuous integration, figure out how to make sure each team has a product owner, determine how team measures the impact of adopting Scrum. Improvement backlog will emphasize creation of awareness and desire, developing the ability, promote success or transfer the knowledge to other groups.

Further Reading:

Book: SUCCEEDING WITH AGILE Software Development Using Scrum by Mike Cohn