<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Saket Bansal on Medium]]></title>
        <description><![CDATA[Stories by Saket Bansal on Medium]]></description>
        <link>https://medium.com/@Saket_tg?source=rss-d1338384f5be------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yV5wdGcM5BRW7E8c.jpg</url>
            <title>Stories by Saket Bansal on Medium</title>
            <link>https://medium.com/@Saket_tg?source=rss-d1338384f5be------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:05:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Saket_tg/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Pragmatic Approach to Agile Delivery: Disciplined Agile Delivery]]></title>
            <link>https://medium.com/@Saket_tg/a-pragmatic-approach-to-agile-delivery-disciplined-agile-delivery-7aa138be0898?source=rss-d1338384f5be------2</link>
            <guid isPermaLink="false">https://medium.com/p/7aa138be0898</guid>
            <category><![CDATA[agile-project-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Saket Bansal]]></dc:creator>
            <pubDate>Mon, 20 Apr 2020 12:50:38 GMT</pubDate>
            <atom:updated>2020-04-20T12:50:38.645Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A Pragmatic Approach to Agile Delivery: Disciplined Agile Delivery</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dUmeaexkui15AvbAGUmJpQ.png" /></figure><p><strong>What is Disciplined Agile Delivery(DAD)?</strong></p><p>DAD can be understood as a context-sensitive framework that can be customized according to your specific needs with the help of multiple options.</p><p>This framework offers a collection of ideas that enable an organization to function with agility. These ideas can be selected and used in conjunction with the existing knowledge base to adopt agility.</p><p><strong>There are two popular ways of approaching a problem:</strong></p><p>1. You start at a specific point, look at your problem and try to find solutions. thereby keeping retrospective and learning.</p><p>2. You establish the start and finish points and establish the process by which you will traverse the path from start to finish.</p><p>DAD is a framework that is somewhere in between both these methods. It is an approach that does not offer a clear prescription for solving the problem nor is it a method where you keep thinking and deciding your course of action.</p><p>It offers several tools and techniques to solve a problem and the user can select tools and techniques that are best suited to address their problem. This framework enables you to create your working methodology.</p><p><strong>Concepts relevant to DAD</strong></p><p><strong>Lifecycle</strong></p><p>DAD offers a variety of lifecycle options. To initiate the process, you need to select the appropriate lifecycle relevant to your context.</p><p>However, you need to bear in mind, that the lifecycle is not constant but can change at any stage over your product journey. For instance, you may start with a scrum-based approach and when your product goes through multiple releases it may go towards Lean or Kanban oriented approaches.</p><p><strong>Team Orientation and Environment</strong></p><p>After the selection of the lifecycle, the next area of focus is the team orientation and project environment.</p><p>You may have a distributed team, dispersed team or a collocated team for the project. Besides, your team could be a single/multi-vendor or have any other orientation.</p><p>Each team will have its own lifecycle based on its context. The output of all the teams will need to be integrated to arrive at a common solution.</p><p><strong>Context-Sensitive Process</strong></p><p>Based on your context, lifecycle, and team, you decide your working methodology so that the team and stakeholders remain focused on the problem.</p><p><strong>Goal-Oriented</strong></p><p>The DAD framework prompts you to pick a goal.</p><p>You then compare the various options available relevant to your context, lifecycle, and team.</p><p>For instance, if your goal is to explore Scope.</p><p>You will need to look at all the dimensions such as purpose how users will turn how the flow will turn, to name a few.</p><p>The next step is to look at options available for each dimension.</p><p>For instance, if you explore users, the framework will suggest options such as exploring user personas, user stories or user story mapping, and other options. Hence, you can see all variations of exploring the user dimension in scope.</p><p>Similarly, the framework suggests options for exploring all other dimensions.</p><p>After selecting the options for different dimensions, you can decide your process-flow.</p><p>This is essentially the working of the DAD framework. This framework can also be applied at the enterprise level.</p><p><strong>Agile Governance</strong></p><p>Multiple teams may pick up different choices based on their context and lifecycle. However, they need to integrate with common governance and milestones.</p><p>As soon as we hear the term “milestones”, we associate it with the Waterfall model of project management and may wonder how it is relevant in the agile scheme of work.</p><p>Milestones in DAD are quite different from those in the Waterfall. In DAD, milestones are not documentation or checklist based processes, instead, they refer to agreement between different entities.</p><p>When multiple teams are working on a specific project, a milestone is achieved when different stakeholders agree on a specific point. This is not documentation but just an agreement.</p><p>These alignment-based milestones help integrate different teams using different lifecycles and processes.</p><p>Once you understand its application at the enterprise level, you can determine how the process is relevant to your work environment.</p><p><strong>Supports Project-Based Lifecycles</strong></p><p>Another unique feature of DAD is that unlike other agile methodologies, it is also applicable to a project-based way of working.</p><p>Most of the popular agile frameworks focus on continuous product or flow-based working models. Hence, they do not fit the bill in case you are working in a vendor-customer project-based environment and have a contract to adhere to. But, DAD guides such environments as well.</p><p>This summarizes the content of the framework. To know more I would encourage you to check this video on DAD</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fq1oPKA9X32M%3Fstart%3D314%26feature%3Doembed%26start%3D314&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dq1oPKA9X32M&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fq1oPKA9X32M%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/28ea0a744254d64ff7d3f55a8f3b1822/href">https://medium.com/media/28ea0a744254d64ff7d3f55a8f3b1822/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7aa138be0898" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business Agility-A Holistic Approach to Agility!]]></title>
            <link>https://medium.com/@Saket_tg/business-agility-a-holistic-approach-to-agility-7025f45ff33e?source=rss-d1338384f5be------2</link>
            <guid isPermaLink="false">https://medium.com/p/7025f45ff33e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[business-agility]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Saket Bansal]]></dc:creator>
            <pubDate>Sat, 21 Mar 2020 07:24:28 GMT</pubDate>
            <atom:updated>2020-03-21T07:24:28.857Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7vlxMlHSBrAAD-WTPOKrg.png" /></figure><p>We are all familiar with the concept of agility and its need and implementation in an enterprise. Off late a new phrase “Business Agility” has cropped up that has led to confusion in the minds of professionals as to what it actually implies.</p><p>In an endeavor to clear the cloud about business agility, I, Saket Bansal, have just hosted a panel discussion with some of the experts in the field. And, we will be discussing in detail what business agility implies and how an agile coach can train an enterprise for business agility.</p><p>Our panelists today are Sanjay, Shane, and Rakesh</p><p>Here’s a brief profile of our panelists:</p><p>Sanjay Kumar<br> <br>A senior Agile/Kanban Coach, with over 20 years of IT experience, Sanjay helps organizations learn and transition to Agile in an evolutionary/low-impact manner that aims to bring quick results while maintaining high motivation and low resistance. Although he has not specifically coached business agility, the concept is deeply embedded in the field that he works on.</p><p>Shane Hastie</p><p>Shane Hastie is the Director of Community Development for <a href="http://www.icagile.com/">ICAgile</a>, a global accreditation and certification body dedicated to improving the state of agile learning. ICAgile is deeply involved in helping organizations transition to business agility. In this direction, ICAgile has published a roadmap for training that can help develop the competencies required for becoming agile at the enterprise level. He feels agility needs to woven across the entire organization so that the business becomes agile at the enterprise level.</p><p>Rakesh Singh</p><p>Rakesh is an ICAgile Authorized Instructor for ICP-BAF and experienced faculty/coach/mentor for Leadership in Lean Management and leading Business Process Frameworks/Models. He has been the Head at Siemens for a long time and has been a part of their enterprise-level transformation. His area of interest in business agility is the activities and programs an organization implements at the enterprise level to achieve holistic agility.</p><p>I would like to share with you the key insights of this discussion that has been an enriching experience for me. I am sure you will also stand to benefit from it.</p><p>Business agility has different implications for different people. Before we dig deeper into the different aspects of business agility, let us look at the perspectives of our esteemed panelists on business agility and reach a common ground.</p><p>With this objective, I opened the discussion with the question,</p><p>1. What is Business Agility?</p><p>To start with agility was the domain of the development teams alone with the focus to complete a task quickly and show the result to the client. But once the success of agility was experienced, it was felt that there is a need to scale agility from development to enterprise level. This is because organizations need to adapt and respond to the ever-changing market scenario.</p><p>Business agility is the ability of an organization to respond to change at a rate that not only keeps up with the speed of change but also uses the change to its advantage.</p><p>To adopt business agility at the enterprise level, the mindset needs to shift from resource-based thinking to a humanistic approach wherein people become a source of creative innovation to foster an environment where creativity thrives.</p><p>Business agility is a holistic approach where the entire organization functions with agility. For effective business agility, it is essential that the top management also gets involved in the process. Business agility entails the implementation of agile practices across cross-functional teams such as HR, finance, marketing, to name a few.</p><p>Business agility is no longer an option but a must for organizations to survive in the 21st-century chaos.</p><p>The views of the different speakers gave us a clear idea of what business agility was all about. This led to the question of what prompted the need to implement agility at the enterprise level?</p><p>This is what the panelists had to say when they were asked,</p><p>2. What was missing in Agile practices that prompted the need for business agility?</p><p>These were some issues that organizations faced which business agility addressed successfully:</p><p>When product development was done in software development space, it faced certain bottlenecks which led to product development failing.</p><p>Business agility has provided clarity on what to build and how to build after eliminating the bottlenecks.</p><p>Earlier when different teams in an organization were operating from different locations, it was difficult to understand how these teams will work together. Besides resource optimization was another issue across multiple locations.</p><p>Business agility provides a framework for people to interact with each other and focus on areas that impact each other.</p><p>Before business agility was introduced, the development followed a path of delivery, followed by creation and then discovery.</p><p>Business agility has changed the path to value discovery as the first stage, followed by value creation, and then value delivery to enable the business to adapt to changes.</p><p>However, it is relevant to understand that in the case of an agile model where a business is required to adapt to changes on a minute by minute basis, it faces several constraints. And, these constraints are continually moving. Therefore an organization needs to respond and adapt continuously. In other words, it is a process of continuous evolution for the organization. And, it is imperative that everyone in the organization works collaboratively to affect this process of continuous evolution.</p><p>There is no end state in agility.</p><p>These perspectives made it clear that business agility is the way ahead for organizations in the ever-changing marketplace. So, now we needed to find out how exactly business agility can be implemented in organizations.</p><p>3. How to achieve business agility?</p><p>Firstly change your perspective of your customers. An organization needs to shift its focus from aspects such as profits, returns and other such parameters to a customer-centric approach. Organizations need to offer their customers great value for what they spend. Customer loyalty is an important aspect in the current scenario. An organization needs to focus on building long-term relationships with their customers.</p><p>To achieve these objectives, organizations need to empower those who are in close contact with customers. The paradigm that “Boss knows best” needs to shift to “people closest to customers know best.” And, they will provide inputs to the organization regarding what needs to be done. Returns, profitability, and sustainability are the side effects of a customer-centric approach.</p><p>There is a need to change the mindset of all employees at the individual level. Individual team members need to change their mindset from focusing on just themselves and their task alone to taking collective responsibility.</p><p>Individuals need to realize that there is a leader in each one of them and they need to nurture that leader and proactively shoulder responsibilities. Individuals also need to help other team members for better outcomes.</p><p>The mindset of the leaders also needs to change to adopt agility at enterprise level. Leaders need to develop an agile approach. There needs to be a shift from a culture of giving and taking orders to use of collective intelligence for engagement.</p><p>Organizations need to adopt strategic agility. Strategic agility entails not just working on fulfilling the current needs of the customers but of future needs. Also, being adaptable to new ways of doing business, the ability to switch products in case of a disruption. Strategic business agility is doing things proactively to adapt to unforeseen situations because the future is unpredictable.</p><p>Before an enterprise goes ahead with implementing business agility, it is relevant to assess the roadblocks that it may face. And, this is what the answers by the panelists to the next question highlight.</p><p>4. What are the challenges to business agility?</p><p>External constraints such as managing customers, managing suppliers, and other such constraints over which the business has no control.</p><p>Lack of clarity of vision.</p><p>Over-reliance on processes and tools undermining individual interaction.</p><p>Using the wrong metrics to evaluate the success of agility. The success of agility cannot be assessed by the number of individuals in the organization trained in Agile, but it is measured by business outcomes like time to market, customer satisfaction or product quality to name a few.</p><p>One of the toughest challenges is the lack of agility in leadership.</p><p>An organization’s comfort with the current status and short term thinking instead of focusing on growth aspects of business agility is another challenge to business agility.</p><p>As an agile coach, I was curious to find out the role that a coach is required to play when a business transitions to an agile mode of working. This is what the panelists suggested about how a coach can play a pivotal role in this endeavor of the business.</p><p>5. What is the role of an agile coach in business agility?</p><p>A good coach needs to be a good listener at all levels of the organization.</p><p>An agile coach needs to engage with the leadership of the organization and get insights into the thought process of the leadership. The coach must understand what the leaders care how these aspects can be linked to what needs to be done further down the chain.</p><p>The coach needs to engage in meaningful conversations with the leaders to change their mindset.</p><p>He also needs to understand the business needs, customer needs, and other aspects associated with the business.</p><p>He needs to have familiarity and expertise in design as the coach might be expected to coach stakeholders, business leaders, and teams.</p><p>A coach needs to visualize at the enterprise level and influence, identify, and communicate goals of the organization in a manner that can percolate to operational areas of the business. This will help to figure out the structure, right team formation, skills needed to achieve this goal.</p><p>In a nutshell. the coach is expected to understand the how and why of the organization to develop an agile training program to coach an organization for business agility.</p><p>Summarizing</p><p>Business agility empowers a business to not only respond and adapt to change but also leverage change for its benefit. An agile approach is not just limited to businesses but can also be applied to life so that we accept changes and adapt to them. Agility is especially relevant in the volatile situation that we are currently in. An agile mindset has the potential to empower organizations, communities, and countries to combat the challenges we are facing.</p><p>This was the essence of the discussion that we had. I enjoyed the experience and I am sure you will too! Check out the details of the recording for an in-depth insight into business agility. Stay connected with <a href="http://www.izenbridge.com/">iZenBridge</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FXuZsos-w0Hs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DXuZsos-w0Hs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FXuZsos-w0Hs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bb18992c7563717c280b195ac119b642/href">https://medium.com/media/bb18992c7563717c280b195ac119b642/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7025f45ff33e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should a Scrum Master be a Technical Person?]]></title>
            <link>https://medium.com/@Saket_tg/should-a-scrum-master-be-a-technical-person-aae5bdd12?source=rss-d1338384f5be------2</link>
            <guid isPermaLink="false">https://medium.com/p/aae5bdd12</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[delivery-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Saket Bansal]]></dc:creator>
            <pubDate>Wed, 18 Mar 2020 12:47:32 GMT</pubDate>
            <atom:updated>2020-03-21T07:51:21.872Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WOE1wDAMOHq7GVQTQEPLYg.png" /></figure><p>One of the most mind-boggling questions for a professional aspiring to become a scrum master is “Does a person need to be technically strong for a scrum master job?”</p><p>Many professionals are confused about the extent to which technical expertise is required. Then again, arises the question, “Is technical expertise sufficient to become a scrum master?”</p><p>Coupled with questions like, “Do I need skills other than technical skills to become a scrum master?” or “What exactly does one need to know other than scrum to get a scrum master job?”</p><p>Trainers and consultants have been answering this question where they talk about the role of a scrum master. However, a trainer’s perspective might differ from what is expected by an organization for a job title scrum master.</p><p>If we look at a job seeker’s perspective of the job of a scrum master, what he/she is actually looking for is a job title “Scrum Master.”</p><p>It is important to understand that there is a difference in the “Title” Scrum Master and “Role” Scrum master.</p><p>The title scrum master is essentially the label you have within your company based on the position you hold, while a job role is a function you fill within your organization.</p><p>To explain the difference between a job title and a job role, let us take the example of the job title “Project manager”. A project manager may exist in any organization irrespective of its size or age. But if we dig into the job role of a project manager, we realize that the responsibilities of the project manager are not restricted to just that of project management but might include several other responsibilities in addition.</p><p>Similarly, when you look at a job titled Scrum master, it is relevant to understand that the role of scrum master entails multiple responsibilities in addition to that of a scrum master.</p><p>The problem arises when the terms job title and job role are used interchangeably and we do not realize what exactly a job title and job role imply. In other words, we assume that job title is the same as a job role as defined in the Scrum guide.</p><p>If we go as per the scrum guide, we find that you don’t need any technical knowledge to perform the role of a scrum master. However, you may need technical knowledge to get a job of title scrum master in a particular company.</p><p>We need to realize that while the title is specific to an organization, the job role pertains to the responsibilities you are expected to perform as a scrum master. It comes from a framework that encompasses aspects such as what the organization expects you to do, what you facilitate, how you coach the enterprise or how you coach the product owner, and other related skills, as defined by the scrum guide</p><p>In most cases, a job title is heavier than the job role. However, it might be lighter in other cases. It totally depends on the organization.</p><p>A job title scrum master might include, but not limited to, responsibilities such as that of a scrum master, technical expert, delivery manager, people manager. However, the exact mix of responsibilities is not a standard but totally depends on the organization. It is guided by aspects such as the beliefs of the organization, its DNA, its business model, and other such aspects that define the organization.</p><p>If we look at a service organization, the title scrum master may encompass responsibilities such as client management, contracts, invoicing, to name a few. However, a product-based organization will not have the same expectations from a scrum master. They may expect the scrum master to have technical expertise along with a scrum master role. In other words, what responsibilities are included under the umbrella term “scrum master” depends on the type of organization.</p><p>In the case of organizations that hire people on a regular basis and don’t have a skilled development team, they will expect the scrum master to drive the development effort. They are looking for technical expertise along with a scrum master role under the title scrum master.</p><p>Some organizations may look for a delivery management professional under the title scrum master. Especially in a service organization, the scrum master maybe expected to handle responsibilities such as client management, vendor relationships, contracts, and other delivery related responsibilities besides working as a scrum master</p><p>Sometimes people management skills are also expected wherein the scrum master is expected to manage people and take care of aspects such as managing appraisals, leaves, motivation, and other responsibilities associated with people management.</p><p>Therefore, we see that each organization looks for a typical mix of responsibilities depending on its business model.</p><p>Hence, when you are looking for a job title Scrum Master, you should be aware of the responsibilities expected under the title in the organization that you are seeking employment. And, whether you have the required skills for the role.</p><p>Irrespective of what the expectations of organizations might be, as a professional, it is important for you to make a career path for yourself. You need to focus on what skills you need to develop to position yourself as a scrum master.</p><p>It is recommended that you add skills in areas other than scrum to grow as a professional who can take up multiple roles. You will be ready to work under the title scrum master and shoulder responsibilities such as delivery manager, agile coach, and many more.</p><p>Now arises the question, what specific skills you need to develop?</p><p>You can start by looking at your areas of interest, your background, and other facets of your existing domain, and develop related skill-sets. For instance, if you have delivery management or program management background you can develop agile coaching and delivery management skills. Alternatively, if you have team leadership, technical leadership or technical mentoring background, you can focus on technology space along with a scrum master job. If you have a client handling background or requirement elicitation background, you can retain the domain part of your expertise so that you will be more competent in working as a scrum master along with your domain expertise.</p><p>In a nutshell, you need to develop skills related to your background, area of interest, and experience in addition to those of a scrum master to fit into a job title of scrum master.</p><p>We at <a href="http://www.izenbridge.com/">iZenBridge</a> can help you in working towards your goal of becoming a scrum master with multiple skills.</p><p>We have several resources on our <a href="http://www.youtube.com/izenbridge">YouTube channel </a>including <a href="https://www.youtube.com/watch?v=rGAIhkZobro&amp;list=PLWcvFkRbuunn534zhHAQ0pn0uJ2sCXgjo">interview questions</a> and answers related to delivery management, agile, and other topics that might be needed along with scrum master role.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Foy5ZNNiDSq0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Doy5ZNNiDSq0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Foy5ZNNiDSq0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/188fe6f4e9599d4787456566f63ae27a/href">https://medium.com/media/188fe6f4e9599d4787456566f63ae27a/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aae5bdd12" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>