Жыл бұрын
Жыл бұрын
Жыл бұрын
Пікірлер
@0225Rachel 9 ай бұрын
very informative.
@mahesh.vengurlekar Жыл бұрын
Precise and to the point info
@Anuragdenigma Жыл бұрын
Thank you. Can you please share the link to download the Leading SAFE 6.0 workbook?
@ericmiltonbrown Жыл бұрын
Inspiring!
@ArvindSingh-tz1xf Жыл бұрын
Very well explained - thank you.
@LeanWisdom Жыл бұрын
Register with this link: us06web.zoom.us/webinar/register/WN_puoyqnrfS4qmvOHpxaL8cA
@wesleyclay2220 Жыл бұрын
*promosm*
@brijeshpandey99 Жыл бұрын
Great 👍
@LeanWisdom Жыл бұрын
Thank You Brijesh
@aadi5000 Жыл бұрын
how can we join this session ?
@LeanWisdom Жыл бұрын
You can join with this link Registration Link - bit.ly/3xEeWKH
@revaapple5521 3 жыл бұрын
Product management is very diluted in Indian market. At best a technical product manager can come close to a product owner
@rohitmania1 3 жыл бұрын
@4:54 is the key
@nagukrithi5990 3 жыл бұрын
Great Video - Great Point ! In one of my past project the architect equated utilization to productivity and since he had the over riding "position" the mgmt went with it. The end result was that the project was delayed by 6 months. I hope he sees this message and understands the difference !
@nagukrithi5990 3 жыл бұрын
This video is very helpful for all teams who are transitioning from waterfall to Agile. This is a classic issue for teams who are not cross function or who still have "developers" and "testers" separately inside an agile team.
@nagukrithi5990 3 жыл бұрын
Very nice overview JP sir
@petriheiramo8047 4 жыл бұрын
I agree with this, except for the statements at the end regarding allowing waterfall inside a story. There are ways in which we can be Agile even inside a story, and we should absolutely go there. We can use acceptance criteria or automated acceptance tests as internal vertical slices, and have working functionality at the end of each slice. Best teams are doing this, and they deliver working, tested code (”Done”) every 15 to 120 minutes.
@maheshmathangi5766 4 жыл бұрын
Good Information very Useful Sir
@jayaprakashprabhakar9715 4 жыл бұрын
Thanks for your feedback, Mahesh ! Let me know once you implement these ideas and get good results ! I will be excited to hear out the results that you got !
@hirocky121 4 жыл бұрын
Great piece of information
@jayaprakashprabhakar9715 4 жыл бұрын
Thanks for your feedback, Abhinav !
@jayaprakashprabhakar9715 4 жыл бұрын
Let me know once you implement these ideas and get good results ! I will be excited to hear out the results that you got !
@Manas2 4 жыл бұрын
In both, the case 10 stories delivered. The team which not even picked stories to work on whether they utilized the free time for learning or Identifying areas for improvements? This answer will tell in the long term who is giving more value to the customer.
@jprakashprabhakar 4 жыл бұрын
Hi Manasa, good point. Agile is about being incremental and in Scrum we should be agile not waterfall. So, instead of looking at delivery at the end of sprint, we should measure how we delivered incrementally in a sprint. This will drive more maturity like automation focus, Continuous Integration, Continuous Delivery etc. Yes, instead of having many WIP, its good to focus on learning / removal of existing technical debts etc. This will bring high quality culture, continuous learning culture etc. Thanks for sharing your views !