Rohan Mahalekam
Scrum Master / Associate Manager - Project & Program Management
Virtusa (pvt.).
location_on Sri Lanka
Member since 4 years
Share
Rohan Mahalekam
Specialises In
Graduated in IT and strengthen by Project Management Professional (PMP) certification and has over 17 years of experience in the ICT industry, with over 12 years in IT project management and Agile Scrum.
Specialties: Leading/Managing Teams, Project Management, Day-to-Day Operations, etc. in areas of Business Process Outsourcing/Knowledge Process Outsourcing (BPO/KPO), Systems Integration, Software Development, Managed Services, ERP Implementations, Process Improvement, Quality Management compliance to ISO 9001 and 270001 standards and Consultancy.
-
keyboard_arrow_down
Stop Spilling Over - Ensure Shipable product in Every Sprint
Rohan MahalekamScrum Master / Associate Manager - Project & Program ManagementVirtusa (pvt.).schedule 3 years ago
45 Mins
Talk
Advanced
Most of the IT projects which are executed in agile methodology, are always having the problem of "User stories getting spilled over to next sprint", in other words "Commitment is not met" in the sprint. Main reason for this is identified as "Activities which has dependent tasks are backloaded to the latter part of the sprint, e.g. QA work is always backloaded in the sprint due to delay of Grooming, Code development, Developer testing, etc.
This can be managed by having agreed ceremonies, gates in the sprint execution. Ceremonies ensure activities are completed during agreed dates and gates ensure exit and entry criteria are met. -
-
keyboard_arrow_down
Stop Spilling Over - Ensure Shippable product in Every Sprint
Rohan MahalekamScrum Master / Associate Manager - Project & Program ManagementVirtusa (pvt.).schedule 4 years ago
45 Mins
Presentation
Intermediate
Most of the IT projects which are executed in agile methodology, are always having the problem of "User stories getting spilled over to next sprint", in other words "Commitment is not met" in the sprint. Main reason for this is identified as "Activities which has dependent tasks are backloaded to the latter part of the sprint, e.g. QA work is always backloaded in the sprint due to delay of Grooming, Code development, Developer testing, etc.
This can be managed by having agreed ceremonies, gates in the sprint execution. Ceremonies ensure activities are completed during agreed dates and gates ensure exit and entry criteria are met. -
-
No more submissions exist.
