Scrum Archives - Page 2 of 3

18 Feb 2018

Scrum Chapter Mumbai – “Leading Agile adoption”

Goal to answer the question:

“As an aspiring Agile Coach, I want to learn how to lead Agile adoption for my 1st prospective client, so that I can deliver maximum value and improve their ROI for the investment they make in me”

We had some excellent discussions.

https://youtu.be/z_ZjImEezus

Some insights we gained from our discussion:

Understanding ‘The why”: Why is the organization is trying to embrace Agile?
Derive the baseline of where the organization stands before the Agile journey
Facilitate retrospectives and interviews with the C-level executives, mid level managers and the foot soldiers to understand the culture of the organization as well as their Agile readiness.
Educate the organization on the new ways of working and get a top-down and bottom-up buy-in. This can include trainings, brown bag sessions, etc.
Define quantitative business metrics to measure the progress with the idea of continuous improvement and the understanding that all we need to do is try to be “better than yesterday”
… and many more

The 2nd edition of Scrum Chapter Mumbai is planned on Saturday, March 24th from 4:30pm to 7:00pm.

Topic: Moving from “ScrumBut” to “ScrumAnd“

17 Jul 2017

Sprint Planning

Being the first event for Scrum team at the start of a Sprint, Sprint Planning tends to set the tone for the entire duration of Sprint. Doing the right things at this stage will help reduce the stress on the team and prevent cascading effect of any issues that may hamper the Sprint progress. With that in mind, I wanted to share a ready reckoner for Sprint Planning.

	Product Owner	Scrum Master	Development Team
Goal	Occurs at the beginning of the Sprint to collaborate and come up with work plan for the Sprint
Inputs	Product backlog Latest product increment Projected Development team’s capacity during the Sprint Past performance of the development team Definition of “Done” Retrospective Improvements Impediments
General Responsibilities	Ensure that PBI’s under discussion are “Ready” for selection	Facilitates the event Ensure attendees understand the purpose Maintain Time-box	Invite technical and/ or domain experts as needed
Part I: What work can be done?	Discuss the objectives and PBI’s (wish list) for Sprint Provide PBI’s details		Select and forecast the functionality to be developed
Part I: What work can be done?	Craft Sprint Goal
Part II: How the work will get done?	Clarify selected PBI’s and make trade-offs Discuss Acceptance criteria	Be a neutral party to facilitate negotiations between PO and Development team	Decide how selected PBI’s will be converted to “Done” product increment Renegotiate selected PBI’s with Product Owner, if too much or little effort is needed to convert the PBI into product increment Create Sprint Backlog: PBI’s and delivery plan
Outputs	Sprint Goal: Objective set for the Sprint based on the selected PBI’s Guidance for Development Team for the Sprint Gives some flexibility to Development Team regarding implementation of the selected functionalities Should be a logical function that makes Development Team work together rather than working in silos Sacrosanct and doesn’t change throughout the Sprint Sprint Backlog: It contains selected PBI’s, tasks breakdown and plan to deliver the product Increment
Do’s	Be prepared with PBI’s under discussion Follow Scrum values throughout the meeting Keep stakeholders abreast with the decision post the meeting	Listen actively Liaise between Product Owner and Development Team Help keep the discussions on track and time boxed Follow Scrum values throughout the meeting If necessary to keep discussion on track, coach the team on purpose of the meeting	Ensure appropriate understanding of PBI’s and acceptance criteria Be cognizant of “Done” and Retrospective commitments Follow Scrum values throughout the meeting Ensure everyone is aware of impediments you foresee that are out of your control
Don’ts	Negotiate on “Done” for more PBI’s to be completed	Take sides during the discussion	Overcommit

16 Apr 2017

Some feedback from my students for Scrum.org trainings (PSF / PSM)

Feedback on the Scrum.org training (PSF / PSM):

Highly Enthusiastic , with good interactive teaching style , making sure that everyone is active in the class, great way of answering questions with examples

Highly energetic with several anecdotes and practical learning shared during the session. I loved it!! All questions got answered, and plenty of insights shared. Extremely grateful to you for sharing your insights and making me unlearn & learn Scrum.

Full points for the effective teaching methods employed and your enthusiasm. The answers to the questions demonstrate your Scrum Knowledge and several examples you quote from the industry speak wide experience as a trainer.

Hiren has excellent hold on the subject and explains in such an effective manner that you get answer of further potential question.

Energy is awesome. Scrum knowledge is rated 10/10

Feedback on my book – Scrum Insights for Practitioners:

There are numerous books about Scrum – this begins where most writers stop … Here, not only the Scrum Guide is reworded, but knowledge and experience are conveyed by one who has Scrum knowledge

Excellent. Lucid and interesting, EASY to READ and UNDERSTAND. Overall 101/100

Good List down of point and Ideas for beginners to start with . It acts as a support system for the baby who is trying and learning to walk.

Very insightful and practical. Helped me understand the spirit of scrum and how it can be practically applied.

Got 77/80 in PSM1 !!! Your book is an absolute Bible on Scrum!

22 Jan 2017 - 1

How do the 3 Scrum Roles Promote Self-organization?

The Scrum Team consists of 3 distinct Scrum roles that promote Self-organization: the Scrum Master, the Product Owner, and the Development Team. The accountability of each role complements the accountability of the other roles. Hence, collaboration between these roles is the key to success:

The Scrum Master, through servant-leadership, coaches, facilitates, educates, and guides the team to solve its own problems by using the three pillars of empiricism. The Scrum Master understands that constructive disagreements are necessary to build high performing teams. The Scrum Master allows the team to learn from the cycle of failing, trying, and failing again. The Scrum Master also helps self-organization by proactively and uncompromisingly removing impediments that are beyond the team’s self-organization capability.

The Product Owner closely interacts with stakeholders and product management to identify the most valuable work. The
The 3 Scrum Roles

Product Owner relies on the Development Team for the actual delivery of a potentially shippable software increment in every Sprint. At every Sprint Review, the stake- holders help the team in shaping the future product.

The Development Team members collaboratively select their own work from the Product Backlog ordered by the Product Owner. They collaboratively create actionable activities to realize their forecast as reflected in the Sprint Backlog. They replan their work on a daily basis within the time-boxed Sprint to optimize the team’s output. They deliver a potentially releasable increment (integrated with increments of other teams, if multiple teams are involved) of software at the end of each Sprint. This self-directedness, the ability for people to direct their own work, motivates them and reinforces self-organization.

One of the best examples of self-organization comes straight from Ken Schwaber’s blog post “Self-Organization and Our Belief That We Are in Charge.”

I pose the following question to Scrum Masters: What is the best way to organize 100 developers into Scrum Teams?

According to Ken, he would

let the developers self-organize themselves into Development Teams as per the recommendation in The Scrum Guide that has all the cross-functional skills to build an integrated done Increment every Sprint. The Scrum Master may remind them that all one hundred people must be engaged meaningfully and that mentoring is expected. The Scrum Master may have the lead developers lead a discus- sion about the software and architecture to be worked on, with the underlying dependencies. The Scrum Master may have the Product Owner discuss the intricacies of the Product Backlog. And, if they organize sub-optimally, they can correct and continually adjust team membership as they find out more. Promote a learning organization with Bottom-up intelligence. So the one-hundred-people group self-organizes and divides itself into teams.

This is one of the topics from my book – “Scrum Insights For Practitioners: The Scrum Guide Companion“. Happy reading!

I look forward to hearing your thoughts on how the Scrum roles can further promote Self-organization.

23 Dec 2016

How Is Emergent Architecture Handled in Scrum?

Scrum embraces the Agile principle of emergent architecture and design. Architectural needs emerge due to functional and non- functional requirements. Certain nonfunctional requirements like security, deployment platforms, compliance, and scalability are often of very high value and ordered high in the Product Backlog. Usually some parts of each of those nonfunctional requirements are required for an initial release of a minimum viable product.Business-facing functionality (i.e., functional requirements) also drives architectural and design needs as well. In Scrum, each Sprint serves to build at least one piece of business-facing functionality that has at least some tiny amount of value. So as we evolve the system, we build only enough architecture and design to support the functional and nonfunctional requirements that we are focusing on for that Sprint.

Important: In every Sprint at a minimum we have to build at least one piece of that business-facing functionality, regardless of how many nonfunctional requirements and architecture we are also focusing on.

Then with every subsequent Sprint, more and more of the architecture and design emerges in response to more and more high-ordered requirements. The purpose of this is to build architecture and design only in response to the highest-valued requirements at the top of the Product Backlog.

An example of how Architecture is handled in Scrum.

Emergent Architecture

In the example shown in the chart, in Sprint 1 the majority of the work done by the Scrum Team is on architecture/infra- structure; however, enough business-facing valuable functionality is still released by the team to deliver value and validate the current architecture work. As the team progresses further Sprint over Sprint, the architectural needs decrease, and the value-driven business functionality delivered increases.

The Development Team also ensures good architecture by ensuring a set of guiding architectural principles that every Development Team member understands and follows while writing code. In addition, architecture is an ongoing discussion in the Development Team focusing on implementing current Sprint Backlog items.

This is one of the topics from my book – “Scrum Insights For Practitioners: The Scrum Guide Companion“. Happy reading!

You can read more about Emergent Architecture and Design here.

12 Dec 2016

How Does Scrum Promote Self-Organization?

Self-organization is something that cannot be imposed on the team. Self-organization does not mean a free run where Development Team members can do whatever they desire. Self-organization happens by setting clear boundaries within which the empowered team members can organize their own work.

04 Dec 2016

The Three Pillars of Empiricism (Scrum)

Empiricism means working in a fact-based, experience-based, and evidence-based manner. Scrum implements an empirical process where progress is based on observations of reality, not fictitious plans. Scrum also places great emphasis on mind-set and cultural shift to achieve business and organizational Agility.

The three pillars of empiricism are as follows:

Three Pillars of Empiricism

Transparency: This means presenting the facts as is. All people involved—the customer, the CEO, individual contributors—are transparent in their day-to-day dealings with others. They all trust each other, and they have the courage to keep each other abreast of good news as well as bad news. Everyone strives and collectively collaborates for the common organizational objective, and no one has any hidden agenda.

Inspection: Inspection in this context is not an inspection by an inspector or an auditor but an inspection by every- one on the Scrum Team. The inspection can be done for the product, processes, people aspects, practices, and continuous improvements. For example, the team openly and transparently shows the product at the end of each Sprint to the customer in order to gather valuable feedback. If the customer changes the requirements during inspection, the team does not complain but rather adapts by using this as an opportunity to collaborate with the customer to clarify the requirements and test out the new hypothesis.

Adaptation: Adaptation in this context is about continuous improvement, the ability to adapt based on the results of the inspection. Everyone in the organization must ask this question regularly: Are we better off than yesterday? For profit-based organizations, the value is represented in terms of profit. The adaptation should eventually relay back to one of the reasons for adapting Agile—for example, faster time to market, increased return on investment through value- based delivery, reduced total cost of ownership through enhanced software quality, and improved customer and employee satisfaction.

Scrum works not because it has three roles, five events, and three artifacts but because it adheres to the underlying Agile principles of iterative, value-based incremental delivery by frequently gathering customer feedback and embracing change. This results in faster time to market, better delivery predictability, increased customer responsiveness, ability to change direction by managing changing priorities, enhanced software quality, and improved risk management.

This is one of the topics I covered in my book – “Scrum Insights For Practitioners: The Scrum Guide Companion“. Happy reading!

20 Nov 2016

Book: “Scrum Insights For Practitioners”

I am pleased to announce my new book — “Scrum Insights for Practitioners: The Scrum Guide Companion”. Thank you all for your support and help.

The Scrum Guide holds the bare and essential rules of Scrum. It provides sufficient information to understand Scrum but leaves much open for interpretation by readers and practitioners. When individuals and organizations follow The Scrum Guide blindly, without understanding the real, deep essence of Scrum—the principles and values underpinning the framework—they likely will fail to reap all the benefits Scrum has to offer.

Scrum Insights for Practitioners fills in some gaps in the understanding of Scrum for individuals or organizations practicing Scrum. This book can be thought of as a companion to The Scrum Guide. I encourage readers to first read The Scrum Guide if you are new to Scrum before reading this book, as this will help you reap the maximum benefits.

Scrum Insights for Practitioners is a perfect companion to The Scrum Guide that helps the practitioners master the Scrum framework by gaining in-depth practical insights and helps answer questions such as these:

What are some common myths, mysteries, and misconceptions of Scrum?
The Scrum Guide recommends three to nine members in a Development Team, but we have fifteen members. Is this Scrum?
Can you share some tactics to do effective Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and Product Backlog Refinement?
My designation is development manager. Does this mean I have no role in Scrum?
How is Scrum Empirical?
Can Scrum Master and Product Owner be the same person?
We don’t have a Scrum Master. Are we still practicing Scrum?
What does Self-Organization really mean?
How does Scrum embrace the four values and twelve principles of the Agile Manifesto?
Please share a case study on Scrum based product development?

Recommendations for the book from the Scrum champions

Take advantage of Hiren’s vast experience and avoid making the common errors people make as they begin their journey. This book contains a wealth of practical information that will be useful to readers as they work to implement the basic theory found in The Scrum Guide—Steve Porter, team member, Scrum.org

In his book Scrum Insights for Practitioners, Hiren has extended the core rules of The Scrum Guide with practices he has found useful. Hiren answers questions regarding Scrum that potentially remain unanswered even after one reads The Scrum Guide. Hiren dismantles common misconceptions about Scrum, regardless of the source of such misconceptions. Hiren elaborates on basic information provided in The Scrum Guide, as well as on the principles underlying Scrum—Gunther Verheyen, Author of “Scrum — A Pocket Guide, a Smart Travel Companion”

Hiren Doshi has written a fine companion to The Scrum Guide, filling in some of the intentional gaps left in the Scrum framework. Using this companion along with The Scrum Guide will undoubtedly improve the outlook for those teams that internalize its teachings.”—Charles Bradley, ScrumCrazy.com

This book will help you understand the nuances of Scrum. It takes a very practical approach toward implementing Scrum without compromising on its values and principles. A useful and handy reference for Scrum practitioners!—Gopinath R, Agile coach and practitioner

Currently the book is available as a physical copy on Amazon. The Kindle version to follow shortly.

I sincerely hope you find great value in each and every page of the book.

Enjoy Reading. Happy Scrumming.

06 May 2016

15 things a Professional Scrum Product Owner (PSPO) actually does

The Product Owners – Steve Jobs and Jeff Bezos

The Professional Scrum Product Owner (PSPO) is an Entrepreneur – a value Maximizer & Optimizer
The PSPO sets a solid vision to help the Scrum Team keep laser sharped focus and direction that helps with incremental progress at the end of each sprint
1 Product == 1 Product Backlog == 1 Product Owner. Having one PSPO for the product helps with the clarity & focus, ensures quick decision making, and single person accountability for the success of the product.
To validate the idea the PSPO frequently releases the increment of software to market to gain real customer insights
The PSPO has the final say on the order of the Product Backlog. The PSPO orders the PBIs in the product backlog by keeping the Value of the PBI, the dependencies between PBIs and the dependencies on the other products in mind.
The PSPO ensures that most valuable functionality is generated all times by the Development Team.
The PSPO accounts for the Return on Investment and Total Cost of Ownership before a feature is built.
The PSPO ensures that all work done by the Development Team originate from the single Product Backlog – a single source of truth.
To determine the value of the product being delivered the PSPO might use metrics like time to market (cycle time / lead time), percentage of the functionality in the released product used by the customers & the overall customer satisfaction
The PSPO is accountable for Interacting and engaging with the Stakeholders.
The PSPO comes to the Sprint planning with a clear business objective in mind and works with the Development Team to craft a sprint goal based upon the forecast
During the actual Sprint the PSPO is accountable for the Product Backlog Refinement, but may delegate the work to the Development Team.
The PSPO is the only one who can abnormally terminate the Sprint in case the Sprint goal becomes obsolete.
The PSPO Is just one person and not a committee
The PSPO builds trust by closely working with Development Teams. He is not hesitant to delegate the work of writing user stories / Product Backlog items to the Development Team.

Blog