Scrum master
New experiences, new workplace #1
Its been almost 3 months since I joined the new company which is a global BFSI shared service center.Here is my take on some of the new experiences :
Read MoreChronicles of a Scrum master #20 : The end of a journey and the start of another
Being a scrum master for the past few years, I am extremely grateful to be given the opportunity to guide, educate and motivate several product teams. This has allowed me to be a better servant leader. In my previous journey, as a first time line manager with direct reports, there were long hours and many […]
Read MoreChronicles of a Scrum master #19 : User stories guide to better development and further refinement
In the world of agile, requirements come in the form of user stories and it is important to understand that the details contained in the stories are needed to absolute clarity for anyone who is going to be working to get this stories done. Consequently, here are several practices which can be adapted to organizations […]
Read MoreChronicles of a Scrum master #18 : Measuring agile
Agile development is fundamentally about the delivery of value to customer via a iterative and incremental process. This value can be a perceived or tangible value, depending on what the end goal is. Hence, in order to measure the success of an Agile project or product, it is imperative to establish the objectives and end […]
Read MoreChronicles of a Scrum master #17 : Technical debt and Support tickets
In agile way of working, technical debt is still present as the team goes about completing stories based on definition of done. What then exactly is technical debt ? This is the accumulation of previous known anomalies, which were not discovered previously before release. It can be in the form of bugs, design changes, code […]
Read MoreChronicles of a Scrum master #16 : Definition of Done (DoD) Part 2
Note : This is a continuation of my Definition of Done (DoD) Part 1 here. 3. Quality The important assessment of a story after its development or work that needs be done is completed (may not be Done yet) is the quality of the work that is produced. This is usually performed by the QA […]
Read MoreChronicles of a Scrum master #15 : Definition of Done (DoD) Part 1
What is a story that is considered done in a sprint ? Each scrum team may have their own version of the Definition of Done (DoD) for each story as long as they agree on the common concept as a whole (from product owner, business analyst to scrum master, developers and testers. It is essentially […]
Read MoreDec 31 2022 – End of year Scrum master chronicles : Agile implementations
Alas, we are reaching the end of 2022 in a matter of days 🙂 Here in this last post of my 2022 scrum master experience, I would like to thank all my fellow readers and wishing everyone a Happy New Year in advance and may your new year resolutions be made real. Going back through […]
Read MoreChronicles of a Scrum master #14 : 5 Values – Courage, Focus, Commitment, Respect, Openness
This has been a post which I wanted to write for some time but struggled till now to find the right words. Its not that its hard to describe but in an agile environment, there are turbulence and winds of change as well as sometimes thunderstorms, hurricanes and typhoons. To maintain the standards of the […]
Read MoreChronicles of a Scrum master #13 : Empiricism and its 3 Pillars (Transparency, Inspection, Adaptation)
What is Empiricism in the agile scrum context ? One thing it is not is about building empires in your product roadmap 🙂 According to the official Scrum guide , “Empiricism asserts that knowledge comes from experience and making decisions based on what is observed”. In other words, empiricism is about fact-based, experience and evidence […]
Read More