Once again Unicom organized one of the fabulous rendezvous of intellectual professionals from different walks of the varied industries. Many eminent personalities joined hands together to make this event ‘Agile in Business’ a wonderful fest of intellectual performance in the world of business.
The event ‘Agile in Business’ was held in Delhi on October 22, 2013. India Agile Week 2013 was India’s one of the eminent Agile Event. Our expert trainer/coach Saket Bansal, CEO iZenBridge took a session on Planning Poker Tutorial.
The theme for this year’s event was “Adoption, Maturity, & Evolution.” The entire case had been classified under two major categories of issues which include Managerial Track and a Technical Track.
Jainendra Kumar, Director Product Development, Pitney Bowes begin the keynote session on Product Engineering – A CXO Level View. iZenBridge has its session booked right after Jainendra Kumar,’s impressive session. It was an achievement for us to win such a prestigious position. We had a tutorial session on Agile Estimation, Story Point Estimation and Planning Poker, Hands-On with Planning Poker.
Agile Estimation is a very crucial topic which often leads to confusions too. This is also critical from PMI-ACP® Examination point of view. The objective of the session was to demystify all the issues related to Agile Estimation and how Planning Poker is an effective means to provide a reasonable inputs to release planning Saket Bansal talked at length on Story Point Estimation, User Stories and Planning Poker Strategy.
This Agile Estimation talk session resulted into a very interactive session with participation from most of the professionals attending the event. The program mainly focussed on
During the session one of the attendees came up with a very interesting and a significant question which got answered giving real life examples.
How do yous size a work using Planning Poker, where work is simple, but needs to be repeated at many places? Do you see it on the basis of the type of work (simple/complex) or do you size it on the basis of quantum of work?
The answer to this question is. We do it on the basis of the quantum of work because “size is a substantive input for the Agile Release Planning”.
Check up on the visuals of the event.
No Trainings found