Passionate About Inspiring Others

Browse below to get a glimpse of what I do that defines who I am. On this page you'll find details about my current & past affiliations, details of my speaking engagements, my accomplishments, presentations, and a few publications.

My

Portfolio

Profile Pic Agile India 2019.JPG
Affiliations

ThoughtWorks

General Manager

September 2017 - Present

Arrk Group

Senior Business Analyst

April 2011 - March 2014

Business Agility Institute

BAM Leader

April 2018 - Present

Deloitte Consulting

Business Technology Analyst

December 2008 - April 2011

ICAgile

Authorized Instructor

May 2017 - June 2019

Springer Nature

Project Manager

March 2014 - September 2017

Why I Stopped Coaching Agility and So Should You! by Vishal Prasad #AgileIndia2020
24:28
ConfEngine

Why I Stopped Coaching Agility and So Should You! by Vishal Prasad #AgileIndia2020

The story goes ... During the Agile Coach Camp at Agile India 2019, we had an interesting discussion driven by Woody Zuill around the concept of Organisational Inertia. This has been a topic of research since the early 80s with the newest research in 2000s as well. The research basically revolves around two aspects: An organisation's incapability to keep up with major shifts The resistance towards change These don't necessarily stop change from happening but considerably slows down the shift. With organisations struggling to survive in a VUCA world, Organisational Inertia becomes one of the critical factors for consideration. Enter, an Agile Coach! Our industries have heavily invested in them in the recent past and continue to do so in order to help them survive in this VUCA world. Shane Hastie addresses this as the Golden Age of Agile Coaching in which coaches can help the poor souls navigate themselves during a period of turmoil. I respect that. But my evil mind links the concepts of Organisational Inertia and the Golden Age of Agile Coaching differently; so during the Agile Coach Camp, I asked folks to run a Thought Experiment which I also mentioned in my talk during Agile India 2019. The hypothesis is: "We can deploy Agile Coaches in organisations and hopefully the organisations will overcome their inertia in 10 years to provide a better work experience to their employees. Contrarily, if Agile Coaches cease to exist, organisations may crumble under their inertia in 5 years and the ones left will be great places to work" ... from a Behavioural Economics standpoint, the second option seems better. Being a SLICE fundamentalist, I decided to run this hypothesis and began my experiment on 3rd June 2019, the day after I finished my last batch of ICAgile's Agile Coaching training. At the time of submitting this proposal, it hasn't been very long since I started the experiment, and it hasn't been easy to deliberately take a step back from coaching interventions. The observations have been interesting (if not amazing) so far and this is my experience report that I wish to share during Agile India 2020. My plan is to run a set of experiments until 31st December 2019 and then decide my way ahead. I mention below the observations so far that I wish to share in my talk but there may be other experiments that I'll share if provided a platform at Agile India 2020. More details: https://confengine.com/agile-india-2020/proposal/11929 Conference Link: https://2020.agileindia.org
Ep 22 : Safety Check During The Retrospective
02:37
Agile Beyond Boundary

Ep 22 : Safety Check During The Retrospective

#SafetyCheck #Retrospective #AgileBestPractices Thank you for tuning into Agile Beyond boundary. Today's Two-minute Gyaan is about #SafetyCheck during the #Retrospectives A Safety Check is a poll that many teams conduct before their retrospective to Check the presence of a safe environment. It is a good way to check if the team is 1. Open to share and 2. Have the right frame of mind to provide feedback If everyone feels safe, then we are okay to proceed but what if everyone does not feel safe? The first intuitive response would be to- postpone this meeting in order to fix the Safety issues first this, however, will be an Antipattern! A retrospective is a place where people discuss • #people • #relationships • #processes and • #tools so, there's no good reason to #postpone this meeting to mend the relationships when this is exactly where it's supposed to happen. There are a few things to be considered to build a safe #environment : If the environment isn’t safe, then – Our regular #retrospective #patterns may not work so one should not hesitate to conduct retrospectives. Which resembles 1. A #group #therapy #session: Many at times people are just upset because they want to be heard. 2. No external attendees: Retrospectives are very sacred to a team, so one must ensure that the attendees are not external like a sponsor or a manager who's responsible for #appraisals or #performance. It is best to leave the team alone, in order to identify their own improvements 3. Maintain Regularity: Retrospectives must be done regularly. This creates a mental state where people accept that a. This is a time to come together and b. #Improve A good frequency is a month or less One should #timebox the retrospective, but you should still have long enough time in order to have heartfelt conversations. These #practices can help create a safe environment. The role of a #skilled #facilitator Also, one must not ignore the role of a skilled facilitator during retrospectives. They can be #internal or #external to a team as long as they are neutral. Many a time Safety Check may be skipped, if the facilitator has/had regular connects with the team members, for example - a #scrum #master. They may choose to still have the Safety Check if the team members asked for it in order to provide transparency or in order to decide a suitable method for conducting the meeting.
SLICE - The Experimentation Mindset by Vishal Prasad #AgileIndia2019
26:29
ConfEngine

SLICE - The Experimentation Mindset by Vishal Prasad #AgileIndia2019

Agile Principle # 12 defines that at regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly. From Scrum to Kanban and other agile frameworks, this is accomplished through retrospectives and continuous improvement processes. The key to being a successful agile practitioner is to identify areas of improvement and then experiment ways of improving it. But it doesn't stop there; positive improvements ultimately become success stories for other teams and motivates them to experiment with newer ideas which eventually leads to innovation. A negative outcome isn't bad either since it adds to the experience of situations where ideas may not apply. Thus the key to this process lies in being a child, an explorer, and inculcate an experimentation mindset. The SLICE framework addresses this in the following way: • S hare: Share an area of improvement • L earn: Explore the area for ways of improvement • I mplement: Search & apply the learning to identify the success factors • C ollateral: Publish blogs, white papers, presentations, etc. as observations of the implementation • E xpansion: Grow, Seed, and Split in order to explore new venues for success In this talk, I create an environment that inculcates an experimentation mindset and utilise the SLICE framework to drive the exploration. More details: https://confengine.com/agile-india-2019/proposal/7875/slice-the-experimentation-mindset Conference Link: https://2019.agileindia.org/
Scrum Framework | Roles in Scrum | Scrum Rules | Scrum Event & Scrum Artifacts | Sprint |Daily Scrum
01:10:20
KnowledgeHut upGrad

Scrum Framework | Roles in Scrum | Scrum Rules | Scrum Event & Scrum Artifacts | Sprint |Daily Scrum

Scrum Framework: Scrum is not just a process which provides a series of sequences that will help you to produce a high-quality product on time and within a budget. Rather, Scrum is a process framework that allows addressing complex problems to deliver products of the highest possible value. The Scrum framework consists of the Scrum teams with associated Scrum Roles, Scrum Ceremonies, Scrum Artifacts, and Scrum rules. Each component within a Scrum framework has specific grounds and is a key factor to Scrum’s success, whereas the Scrum rules tie the ceremonies, roles, and artifacts together to govern the relationships between them. Topics discussed: 00:40 Introduction 01:36 Scrum - Process Framework 01:48 Scrum Teams 02:00 Empirical Process Model/ Empiricism 02:37 Sprint 04:27 Sprint Planning Meeting 05:28 Daily Scrum Meeting 05:50 Sprint Review 06:28 Sprint Retrospective Meeting 07:00 Scrum Master 07:59 Purpose of scrum 10:54 Why do we need Empiricism? 14:45 The Five Dysfunction of a team 17:18 Advantages of the Scrum Vales 18:16 Five Values of Scrum 18:57 Elements of scrum 19:27 Scrum Events 19:40 Scrum Artifacts 22:59 Development Team 24:32 Users story 25:48 Scrum Master 25:51 Product Owner 26:00 Development team 29:16 Roles in a Scrum Team 30:08 Scrum Events 31:02 Sprint 33:14 Sprint Planning Meeting 36:30 Daily Scrum 38:33 Sprint Review 40:08 Sprint Retrospective 42:02 Scrum Artifacts 43:34 Scrum - Complex Product 45:28 Product Backlog 46:00 Product Backlog Items 48:15 Sprint Backlog 51:27 Transparency of artifacts 53:31 Scrum Anti-Patterns 01:01:05 Immutable Rules 01:05:59 Product Backlog Refinement 01:008:39 Case Studies 📚TAKE THE NEXT STEP IN YOUR CAREER: https://www.knowledgehut.com/ Enroll for Agile Management Courses: https://www.knowledgehut.com/agile-management #Knowledgehut #Agile #Scrum #ScrumFramework #ScrumRoles #Scrumteam #ScrumRules #Sprint #ProductBacklog #ScrumMaster #ProductOwner #ScrumArtifacts #ScrumEvent Follow us on our social handles for more such exciting deals and offers: ▪️ Facebook: https://www.facebook.com/KnowledgeHut.Global ▪️ LinkedIn: https://www.linkedin.com/company/2339512/ ▪️ Twitter: https://twitter.com/KnowledgeHut ▪️ Instagram: https://www.instagram.com/knowledgehut.global/ ▪️ YouTube: https://www.youtube.com/user/TheKnowledgehut
Conference Talks

Agile India Conference 2020

Talk

Virtual

Converge Coimbatore 2019

Workshop

Coimbatore

Agile Coach Camp India 2019

Open Space

Bengaluru

Discuss Agile Day 2016

Talk

Pune

Discuss Agile Day 2015

Experience Report

Pune

Converge Pune 2020

Talk

Virtual

Converge Bengaluru 2019

Talk

Bengaluru

Agile Gurugram 2019

Talk

Gurugram

PlayScrum Conference 2016

Workshop

Pune

FailConf 2019

Talk

Hyderabad

APGI Conference 2019

Talk

Pune

Pune Agile UnConference 2018

Talk

Pune

Global Testing Retreat 2016

Workshop

Pune

Converge Pune 2019

Workshop

Pune

Agile India Conference 2019

Talk

Bengaluru

APGI Conference 2018

Workshop

Pune

Agile India Conference 2016

Experience Report

Bengaluru

Accomplishments

To play, press and hold the enter key. To stop, release the enter key.

Presentations
Publications

Be a BA - Appreciated Anti-Patterns of a Business Analyst

Book

Work in Progress

(Paramount Advisory - Book contains Explicit Sarcasm)

Each of the chapters in this book highlights an anti-pattern that a Business Analyst enacts during their workday and usually gets appreciated for it. I’m kidding of course, Business Analysts hardly ever get appreciated; they so long for it though that they bend over backwards in almost all circumstances just to get a pinch of acceptance from their tribe. It is this primeval desire that leads to the suspension of ego to the wants of the general masses out of a sense of helpfulness. Yeah, it sounds great, until one realises that the reason it’s called “general” masses is because their collective wisdom hardly ever understands the depth of an iceberg of knowledge that’s needed for good analysis in the first place. It is this behaviour of a Business Analyst (doubt if I should even call you one) that leads to anti-patterns, and yes, this paragraph more or less sets the tone of this book I believe.

Agile Days of Future Past

Scrum Alliance

July 2016

(Public articles are now deprecated by Scrum Alliance; don't know why)

My current journey begins in August 1970, when Dr. Winston W. Royce presented his views on "Managing the Development of Large Software Systems" at the proceedings of IEEE WESCON. This revolutionary paper introduced software engineers like me to the world of Waterfall (or, as I like to call it, "what-the-fall"). But we usually skipped the part in our textbooks where Dr. Royce himself stated that pure Waterfall software development would never work. Dr. Royce stated that in order to eliminate most of the development risks, five additional features must be added to the basic what-the-fall approach.

For me, this is the first "manifesto for software development," because it provides the general guidelines for better software development.

Agile Forecasting with Focus Factor

Scrum Alliance

July 2014

(Public articles are now deprecated by Scrum Alliance; don't know why)

How many deliverables should we commit to our customers in, say, the next two weeks? An intriguing question asked by many Agile teams at the beginning of every iteration. The answer to this question depends largely on the team's thinking, philosophy, and skills -- which unfortunately cannot be measured. Then how do we forecast the deliverables?

How about a mathematical formula that provides an unbiased control based on the historical achievements of the team, which can be used for prediction? That's exactly what focus factor does. Focus factor is a simple mathematical formula for forecasting the number of deliverables possible in an iteration. This number can be arrived at by considering the capacity and velocity of a development team.