On this Channel, I talk about things I wish I knew when I started my career in the corporate world. This channel will hold, videos related to strategies, tips, tricks, best practices, and tutorials related to productivity at workplace and life in general.
Your videos are usually great and I want thank you or sharing your knowledge! However, in. this particular video, I believe ended up falling into the same pitfall of others trying to oversimplify mission and vision to one word. Neither of them can be summarized in one word. Even if you are trying to direct thoughts towards a roadmap, WHERE is not enough to define VISION. I want to reach that point in the future (as an analogy to a map) but not at all cost! Therefore, WHERE is not enough. Btw, the usual question is What is your vision, not where!
4:30 I like that, the most real world sattstement based on reality. Now a lot of companies are relying too much on estimation and then re-estimate even worse but you make a fair point, it's context dependent
This seems like waterfall with handoffs at each step. I would argue you should only have one WIP item at a time. Finish the item completely (release to prod) before going to the next item.
All of your videos are like - Man I was looking for this for such a long time! Great job Vibhor! Appreciate all of your efforts! The production quality of your videos is also another level! The BGM however makes me dance and learn at the same time ;) Great job! God bless
Yes but only if you know and have the experience of doing what an Agile Coach does. Just yesterday I wrote a post about it on Winning Strategy vibhorchandel.com/p/what-does-an-agile-coachcoach
I don't agree with the part where it is suggested to avoid breaking the story horizontally. Although this sounds great in theory, often times teams are comprised of specialists in specific tech stacks which has taken them years to gain that expertise. Its naive to think that simply pair programming will allow someone to become a good, let alone an expert in a particular stack. The organization as a whole might not care to push their development team to function like this. By only splitting stories vertically, you are forcing a major shift in the makeup of team and how it operates, just to satisfy the SDLC process.
superb videos and explanation with real life scenarios. While trying to change my organization where I am working as a Scrum master i am planning to cover all videos to refresh my knowledge.
A terrific video that has clarified all my doubts about Kanban Vs Scrum model. Earlier I had a perception that Kanban is only for service and support team. Now, I can assert with promptitude that this might not be the case:
My po created only one userstory for over all developementand asked me to create subtask for every activity in development...is it good?i thought of creating usersstories for ddl/dml and procedure scripts and testing....if we create subtasks then how to maintain and move to very sprint and how to estimate... please give me insight on this ..code is bigquery so we don't have ui
