Enterprise Agile Transformation Enablers

•

0 likes•476 views

The document discusses enabling an agile transformation in an enterprise. It covers principles like individuals and interactions over processes, customer collaboration over contract negotiation, and responding to change over following a plan. It also discusses implementing early and continuous delivery through techniques like test-driven development, continuous integration, continuous delivery, and DevOps. Finally, it provides eight steps to transform an enterprise, including defining business goals, coaching the right people, going deeper before wider, and measuring success.

Enterprise Agile
Transformation
Enablers
- Tushar Somaiya

Enterprise Agile Transformation Enablers

INDIVIDUALS & INTERACTIONS
OVER
Processes and tools
WORKING SOFTWARE
OVER
Comprehensive Documentation
CUSTOMER COLLABORATION
OVER
Contract Negotiation
RESPONDING TO CHANGE
OVER
Following A Plan
TRUST
Let’s Find Out More About Agile
http://agilemanifesto.org/

Sounds Interesting, Tell Me More…
Let’s Focus On implementing 1st Principle Only:
Our highest priority is to
satisfy the customer through
early and continuous
delivery of valuable software

Let’s Try 2 Week Iteration
10 stories
10 stories
10 stories
10 stories
Time Up!!!
No time for testing or no time to deploy and UAT
Waterfall Within 2 Weeks Iteration (Anti-Pattern)

Let’s Try 2 Week Iteration
10 stories
Let’s say we do manage get all 10 stories tested, deployed, UATed and
release them in production to earn some ROI

What Happens In Iteration 2?
10 stories
+ 10 stories (regression)
10 stories
10 stories
10 stories
Time Up!!!
No time for testing or no time to deploy and UAT

What Happens In Iteration 3?
10 stories
+ 20 stories (regression)
QA starts falling behind and works 1 or 2 iterations behind dev
Dev
QA

What Happens In Iteration 3?
Slowly but surely devs and qas would start working
out of their own backlog. The divide keeps increasing.
Dev
QA

Flow (Good Iteration Is Working On One Story At A Time)
Analysis Code TestDesign

Got It! Let’s Try 2 Week Flow
10 stories
This is working!!!
1 story at a time
1 story at a time

What Happens In 4th Iteration?
10 stories
We would have 10 new stories + 30 old stories to regress!
1 story at a time
1 story at a time

So We Try Traditional GUI – Driven Automation
Requirements
Design
CodeManual Test
Automate
Manual Tests

Waiting For Feature To Be Ready? (Anti – Pattern)
And when the automated regression pack fails we do
not know whether it is due to “real” bug or is it due
to brittle UI driven tests which are “old” now
Does it solve the purpose?
Dev
QA
1 story at a time

Let Go Of Ice Cream Cone (Inverted Testing Pyramid)

Our Concerns Are Isolated, We Can Now Test First & Fast

After 3 Good Iterations…
1 story at a time
1 story at a time
1 story at a time
15 Features +
Automated Regression
Of 37….
Well, Now We Are
Doing Good
10
12
15

But, Now Can Business Keep Up?
1 story at a time• We are building
system very fast
• System is working
correctly
• But is it correct
system?
Dev & QA
UAT

Caution: BDD Is NOT Automation Framework

Too Many Units… How To Integrate & Deploy All Units?

Phew, That Was Easy!
Let’s Focus On implementing 1st Principle Only:
Our highest priority is to
satisfy the customer through
early and continuous
delivery of valuable software
2 Weeks
Iteration
TDD, CI,
CD,
Devops
BDD, Iterative
UAT,
Exploratory
Production Ready
software with live
specifications

The whole is greater than sum of its parts

Business Engagement
QA Automation DevOps
Org & People

Enterprise Agile Transformation Enablers
1. Define “Real” Business Goals
2. Coaching Correct Set Of People
3. Go Deeper Over Wider
4. Defer Tooling And Standardization
5. Form & Fund Change Canoes
6. Empower, Enhance, Enable and Engage
7. Measure and celebrate
8. Time To Scale

Tushar Somaiya
Tushar.somaiya@gmail.com
9869209689
@tusharsomaiya

What's hot

Feedback Loops in Agile Development

Behrouz Bakhtiari

Agile development relies on feedback loops to continuously improve the development process. Short iterations and frequent delivery of working software allows customers to provide early and regular feedback to identify issues and ensure the project stays aligned with their needs. Feedback also comes from testing and following principles like rapid feedback and short releases where developers seek feedback quickly after each change and deliver new versions frequently to speed up the feedback cycle. The goal is to detect and address problems as early as possible through an empirical process of making changes, learning from the results, and evolving the process.

Dev ops is more than CI+CD tools

Sudipta Lahiri

[QE 2015] Michał Kordas - Agile testing: Optimizing the feedback loops

Future Processing

W ostatnich latach nauczyliśmy się, że krótkie pętle sprzężenia zwrotnego, czyli tzw. short feedback loops, mają ogromne znaczenie i są jednym z najważniejszych elementów metodyki agile. Właśnie dlatego zabiorę nas na „wycieczkę” po różnych pętlach, z którymi miałem styczność pracując przy swoich projektach. Zaczniemy od naiwnego podejścia „test-after”, następnie przejdziemy do „test-first”, TDD, projektowania ewolucyjnego, minimalnej analizy, 3 Agile Amigos, podejścia biznesowego. Na koniec poznamy rozwiązania oparte na technice „outside-in” BDD.

In Quality We Trust

Vidmantas Kabošis

Continuously delivering software to big brands (fullscreen edition)

Paul Boocock

The document discusses continuous delivery of software to production environments. It describes setting up a continuous integration pipeline with automated builds, tests, and deployments to staging and production environments. This allows code changes to be deployed safely within minutes or hours, as opposed to months. Key aspects discussed are committing code frequently, ensuring every commit is deployable through automated testing and integration, and making the delivery process reliable, predictable and automated. The goal is to lower the cycle time from code change to production release.

DOD 2016 - Diogo Oliveira - The OutSystems R&D Continuous Delivery Journey

PROIDEA

YouTube: https://www.youtube.com/watch?v=f-DyEiTN6nc&index=4&list=PLnKL6-WWWE_VtIMfNLW3N3RGuCUcQkDMl OutSystems builds a complex software product. As the company and the product complexity kept growing (and at a faster pace) to a model where we needed to be able to release more frequently, challenges appeared on the way we were doing automated testing and continuous integration / delivery, which demanded significant changes and improvements in these processes, from the tools to the culture. I will share with you our journey towards Continuous Delivery @ OutSystems R&D, namely describing where we were, where are we now (and how are we doing it) and where do we want to go. This is a very interesting story where we were able to change a lot in a relatively small period of time.

DevOPs Transformation Workshop

Jules Pierre-Louis

This document outlines the agenda and objectives for a DevOps transformation workshop. The workshop will cover DevOps foundations, including value stream mapping exercises. It will define DevOps and discuss how to map the current software delivery lifecycle. Key aspects like cycle time, bottlenecks, wait times and processing times will be examined. The workshop aims to help organizations identify inefficiencies and develop future state solutions to reduce cycle times and implement DevOps best practices.

Agile Testing in Enterprise: Way to transform - SQA Days 2014

Andrey Rebrov

This document discusses problems that can occur with traditional testing approaches and how to transition to agile testing practices. It provides two examples of organizations that struggled with long regression cycles, missed estimates, low quality and stress. The root causes are identified as document-based collaboration, lack of testing knowledge by developers, and infrastructure management chaos. Recommendations are made to use Kanban, collaborate on requirements, implement smart metrics, test automation, and a DevOps approach. Specific practices that were implemented include risk management, specification by example, test-driven development, continuous integration, configuration automation, and test automation. The results were increased delivery rates up to 5 times, zero bugs in production, no overtime, and more enjoyable work.

Integrated Dev And Qa Team With Scrum

Ethan Huang

DevOps Enterprise Summit 2016

Shaw Innes

SOLVING MLOPS FROM FIRST PRINCIPLES, DEAN PLEBAN, DagsHub

DevOpsDays Tel Aviv

One of the hardest challenges data teams face today is selecting which tools to use in their workflow. Marketing messages are vague, and you continuously hear of new buzzwords you “just have to have in your stack”. There is a constant stream of new tools, open-source and proprietary that make buyer’s remorse especially bad. I call it “MLOps Fatigue”. This talk will not discuss a specific MLOps tool, but instead present guidelines and mental models for how to think about the problems you and your team are facing, and how to select the best tools for the task. We will review a few example problems, analyze them, and suggest Open Source solutions for them. We will provide a mental framework that will help tackle future problems you might face and extract the concrete value each tool provides. What you’ll learn You’ll learn what signals to watch for to notice you might have MLOps fatigue. How to define the challenge you’re facing and which questions to ask in order to build a “decision tree” for selecting the best-suited tools for the task. A few examples for using this framework in practice on challenges involving data management and automating training/pipeline tasks About 2 years ago we faced a crisis in our DevOps consulting company - the market demand was higher than we could supply. The traditional recruiting process depending on CV and artificial credentials was not working. So we came up with an alternative solution, and since then - we are growing exponentially and diversely. In this talk we will show the practical tools we deployed in order to increase our capacity, and we will show how these tools overcome the inherited bias in the process.

Testing The Legacy: Making Existing Applications Testable Without Epic Efforts

Alex Leonov

If you have an established product which came about before the widespread use of the unit and system testing, then you know the problem. The old code cannot be made testable without a significant effort of throwing it away and writing it anew. What does it mean for the QA? It means endless repetitions of manual test runs. Sounds like fun? Yeah.. Nah! In this presentation you will find two ways to make legacy applications testable through automation: an easy one, and a good one. The main benefit they provide is a basis for the further refactoring of the application, without damaging it. Think of it as a Catch-22: you can't make your old app code testable without severely changing it, and you can't be sure that your changes work because you have no tests to verify them. If you are a QA and you work with older apps and systems doing a lot of manual testing, then this is the topic for you. This talk was given at ITx 2016 in Wellington, New Zealand, for Testing Professionals Network.

Crossing the Continuous Delivery Chasm - J. Paul Reed

Atlassian

The document discusses strategies for transitioning an organization from continuous integration to continuous delivery. It suggests that proper preparation is needed, including ensuring the right people and tools are in place. Continuous integration is the starting point, and the document provides a "gauntlet" to determine how fully teams have adopted CI. On the journey to continuous delivery, the document emphasizes rethinking quality practices and breaking down silos between teams. Continuous delivery requires investment and changes across the entire organization to enable transparency and flow.

How technical excellence helps in LeSS adoption

Anton Bevzuk

This document discusses how technical excellence practices like pair programming, test automation, and continuous integration help organizations adopt the Large Scale Scrum (LeSS) framework. It provides examples of how Dodo Pizza, an international pizza delivery company, implemented these practices across their 7 development teams of 50 engineers. Key benefits included reduced bugs, increased ability to improve legacy code, and higher customer satisfaction through more frequent releases enabled by the technical practices.

Moving From Staged To Pervasive Testing

Rob Lambert

The QA in the DevOps world

Theresa Neate

Let's drop the tester labels such as "functional tester", "system integration tester", "automation tester", etc. More and more teams are cross-functional and team members are required to be poly-skilled. If you are testing you can and should be involved in the full SDLC, which should include deployments and infrastructure. Just like there is application code, there is infrastructure code, which needs testing too. So where do you fit in? How can you remain relevant and helpful in the DevOps world?

Team wide testing

Ethan Huang

This document discusses implementing team wide testing to improve quality and reduce bugs. It describes current problems like developers feeling pressure to deliver code quickly without proper testing. This leads to bugs found later by testers, wasting time on rework. The team analyzed root causes like lack of test automation and testers. They decided to break down silos between developers and testers. The new process involves test-driven development, continuous testing, and demos at quality gates. While not all user stories were completed, the delivered stories had no bugs found by clients, showing the new process improved quality.

Behave automatically: (Almost) Effortless feature testing

STX Next

Quality at Speed - Penny Wyatt

Atlassian

How can a team of 65 developers build and rapidly ship a high-quality product with only six QA engineers? At Atlassian, we’ve introduced the Quality Assistance model that changes the developer QA mindset, and engages developers in exploratory testing so software is developed right the first time. After all, the cheapest time to fix a bug is before it's written. Join us as we walk through the theory, history, and practice of the model, while busting some of the myths about developers and QA. Reject the tradeoff of time, scope, and quality, and finally have your cake and eat it too.

Shifting is more than shifting left

PractiTest

Slides from Jesper Ottosen's 2017 Fall OnlineTestConf session – Shifting is more than shift left. Change is happening to the testing activities. Shift-left automates and codifies the testing activities. Shift-right does it for production. This session was about a couple of other trends, changes, and shifts that are happening to testers and test managers. – Shift-Coach, where It’s more about coaching teams. – Shift-SME, where it’s more about business savvy. – Shift-Deliver, where it’s more about the road to production www.onlinetestconf.com

What's hot (20)

Feedback Loops in Agile Development

Dev ops is more than CI+CD tools

[QE 2015] Michał Kordas - Agile testing: Optimizing the feedback loops

In Quality We Trust

Continuously delivering software to big brands (fullscreen edition)

DOD 2016 - Diogo Oliveira - The OutSystems R&D Continuous Delivery Journey

DevOPs Transformation Workshop

Agile Testing in Enterprise: Way to transform - SQA Days 2014

Integrated Dev And Qa Team With Scrum

DevOps Enterprise Summit 2016

SOLVING MLOPS FROM FIRST PRINCIPLES, DEAN PLEBAN, DagsHub

Testing The Legacy: Making Existing Applications Testable Without Epic Efforts

Crossing the Continuous Delivery Chasm - J. Paul Reed

How technical excellence helps in LeSS adoption

Moving From Staged To Pervasive Testing

The QA in the DevOps world

Team wide testing

Behave automatically: (Almost) Effortless feature testing

Quality at Speed - Penny Wyatt

Shifting is more than shifting left

Similar to Enterprise Agile Transformation Enablers

Testing in a DevOps team

Laurent PY

Testaus 2014 -seminaari: Arto Kiiskinen, Mirasys Oy. Case Mirasys: Toiminnoil...

Tieturi Oy

This document discusses testing challenges for a software company that develops a video management system product with frequent changes to requirements, priorities, and hardware platforms. The key challenges include long-term planning difficulties due to constantly changing priorities, limited testing resources compared to the size of the product and number of developers, and setup time for complex integration tests. It provides recommendations for achieving high team effectiveness through minimizing interruptions, focusing testing on individual stories, and establishing trust in story-level testing to reduce risks for major releases.

有了 Agile，為什麼還要有 DevOps？

William Yeh

▷ https://william-yeh.net/post/2016/05/devops-a-lean-perspective/ 敏捷運動與 DevOps，有某些共同的淵源，但也有不同的偏重取向。 Agile 陣營的人，常會有個疑問：「聽起來，DevOps 好像只是把 Agile 觸角從 Dev 伸到 Ops 端，只是舊瓶裝新酒？」 Waterfall 陣營的人，也常會有個疑問：「聽起來，DevOps 好像只是 Agile 那一票人搞出來的；我們 Waterfall 陣營是不玩這一套的。」真的是這樣嗎？本次活動會以一些小遊戲、一些小短片，帶領大家從 Lean Thinking 角度，重新審視軟體研發的 value stream。回歸 DevOps 的原點，你將能夠自己給出上述問題的答案。 ▷ 2016-05-03 於 Agile Meetup Taipei 演講實況錄影: https://william-yeh.net/post/2016/05/devops-a-lean-perspective/ 全長整整 2 小時，請享用～～～

Beyond Agile Software

Gabriel Hamilton

Agile Testing. Risks, Uncertainty and Why It All Works

Agileee

The document discusses key principles and practices of agile testing, including delivering working software frequently, adapting to changing business needs, eliminating speculation, checking alignment between intentions and actual needs, and emphasizing a whole-team approach to testing where the team succeeds or fails together. It outlines nine key agile testing practices such as acceptance test-driven development, test-driven development, exploratory testing, test automation, continuous integration, and automated deployment.

Agility at Scale: WebSphere’s Agile Transformation

TechWell

In today's rapidly changing environment, organizations—both large and small—must quickly respond to shifting market requirements to remain competitive. To be successful, many are adopting agile development and continuous delivery methodologies to deliver software quickly, while keeping the quality and maintainability high. Several years ago the WebSphere Application Server development teams embarked on the journey from traditional waterfall development to agile. They are now expanding to use both agile and continuous delivery methodologies across their organization worldwide. Susan Hanson shares the challenges of working with a worldwide team across multiple time zones while shifting away from component-based teams. Learn how the team transformed their development processes, tools, and culture to better adapt to changing requirements. See how, by integrating tools, the team is able to have a complete lifecycle from customer-submitted requirements through planning, development, test, and delivery of these requirements back to the customers, allowing for continuous delivery of cloud-based services.

Exec Leadership workshop

Ravi Tadwalkar

The document outlines an agenda for a Lean-Agile leadership workshop for executives. It will begin with comparing waterfall vs Lean-Agile methodology, focusing on adopting a value-driven mindset by looking at culture first. It will then cover Agile product management, discussing topics like limiting work in progress, prioritization using journey maps and story maps, and the product owner role. Executives will also have a Q&A about Agile transformation journeys and be provided with self-learning aids.

Lloyd roden the fragility of agility

Bouvet ASA

The document provides lessons for successfully implementing Agile practices based on common problems organizations face. It discusses that Agile requires changes to processes, culture, and development approaches. The top 10 lessons include understanding the reasons for adopting Agile, preparing the team through training, balancing functionality and non-functional requirements, avoiding overwork that reduces productivity, and using automation to complement rather than replace manual testing. Proper implementation of Agile requires adapting practices while upholding the Agile manifesto.

A Lean Tour of Lean Software Development

TechWell

Ken Pugh presented on lean software development. He began with background on lean as focusing on continuous delivery of high quality applications through eliminating waste. He discussed measuring and delivering business value, transparency, and developing in small pieces that can be delivered incrementally. Pugh covered value streams and identifying actions, times, delays, and inefficiencies to calculate process cycle efficiency. The goal of lean is to eliminate waste and delays to improve efficiency.

Creating testing tools to support development

Chema del Barco

Reducing passive interruptions

Andrei Tognolo

The document discusses reducing passive interruptions when coding. It notes that programmers can take 10-15 minutes to resume work after an interruption and lose their context and flow. Passive interruptions occur when waiting for feedback like test results or page loads. The document advocates for reducing these interruptions through techniques like instant code reloading, fast tests, and immediate feedback to allow programmers to stay in flow. It argues this is important for designing and verifying ideas quickly during development.

A Software Tester's Travels from the Land of the Waterfall to the Land of Agi...

Yuval Yeret

In my work, I have come across many software testing organizations/groups. Some use the waterfall method and may be in the first stages of exposure to Agile-based methods. Some are on the journey to switch between methods, and some have already been using Agile and are looking for ways to do this more effectively. In this article, I will try to describe the experience of a typical software tester when his organization decides to move to Agile. Note: This is an english translation of a "Thinking Testing" hebrew magazine article from 2012

The 7 Deadly Sins Of Almost Being Agile

lazygolfer

Lean Engineering: Engineering for Learning & Experimentation in the Enterpris...

Rosenfeld Media

DevOps: The Key to IT Performance

Nicole Forsgren

Dr. Nicole Forsgren will present the latest research that uncovers what really drives business outcomes of market share, profitability, and productivity as well as DevOps transformation awesomeness... Hint: these need the right mix of IT, culture, and practice, and include continuous delivery and lean management. This exciting research was done with Jez Humble and Gene Kim, and is promising exciting new projects in the space.

Agile testing

Raj Indugula

Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.

Agile is Dead :: Pixels Camp 2017

Pedro Gustavo Torres

This document discusses how Agile has become outdated or "dead" due to misinterpretations and misapplications over time. The author argues that many companies claim to be Agile but are actually focused on processes and tools rather than outcomes. True Agility values individuals, interactions, working software, and responding to change. The author suggests companies need to refocus on delivering value to customers rather than following rigid practices. Overall, the document criticizes a "cargo cult" mentality around Agile and advocates returning to its original principles of empowering individuals, collaboration, and continuous improvement.

DevOps/Flow workshop for agile india 2015

Yuval Yeret

Serverless in production, an experience report (Going Serverless, 28 Feb 2018)

Domas Lasauskas

This document discusses best practices for preparing serverless applications on AWS Lambda for production. It describes the author's experience deploying 170 Lambda functions and 1.2GB of code into production with a 95% cost savings compared to EC2. Key practices covered include testing, monitoring, logging, distributed tracing, CI/CD pipelines, configuration management, and security. The author advocates for building on principles over tools and shares several tools for serverless development.

Data-Driven Software Mastery @Open Mastery Austin

Arty Starr

What if we could measure the indirect costs of pain building up on a software project? What if we could measure the loss of productivity, the escalating costs and risks, and could steer our projects with a data-driven feedback loop? By measuring the friction in “Idea Flow”, the flow of ideas between the developer and the software, we can create a data-driven feedback loop for learning what works. Rather than making decisions based on anecdote and gut feel, we can start driving our improvement decisions with real data. Data-Driven Software Mastery is about learning and improving faster than ever. Find out how you can: • Identify the biggest causes of productivity loss on your software project. • Avoid spending tons of time solving the wrong problems • Collaborate with other industry professionals in the art of data-driven software mastery Idea Flow gives us a universal language for describing our experience, so we can share the patterns and principles of what works. With a feedback loop, we can run real experiments! Idea Flow turns the development community into a scientific community.

Similar to Enterprise Agile Transformation Enablers (20)

Testing in a DevOps team

Testaus 2014 -seminaari: Arto Kiiskinen, Mirasys Oy. Case Mirasys: Toiminnoil...

有了 Agile，為什麼還要有 DevOps？

Beyond Agile Software

Agile Testing. Risks, Uncertainty and Why It All Works

Agility at Scale: WebSphere’s Agile Transformation

Exec Leadership workshop

Lloyd roden the fragility of agility

A Lean Tour of Lean Software Development

Creating testing tools to support development

Reducing passive interruptions

A Software Tester's Travels from the Land of the Waterfall to the Land of Agi...

The 7 Deadly Sins Of Almost Being Agile

Lean Engineering: Engineering for Learning & Experimentation in the Enterpris...

DevOps: The Key to IT Performance

Agile testing

Agile is Dead :: Pixels Camp 2017

DevOps/Flow workshop for agile india 2015

Serverless in production, an experience report (Going Serverless, 28 Feb 2018)

Data-Driven Software Mastery @Open Mastery Austin

More from Tushar Somaiya

7 - Recommendation From Decos For Tushar Somaiya

Tushar Somaiya

Tushar Somaiya conducted agile development training for the employees of DEeDS Software Development Pvt. Ltd. The training sessions helped the employees better understand agile elements and dynamics. Tushar tailored the course based on discussions with technical leaders and the organization's culture and development environment. Participants provided excellent feedback and appreciated Tushar's knowledge, clear explanations, and ability to address their concerns. The finance manager was impressed with Tushar's interactive training style and recommends him highly based on the successful training.

6 - Recommendation From ABS For Tushar Somaiya

Tushar Somaiya

5 - Remommendation From Andreas Wintersteiger For Tushar Somaiya

Tushar Somaiya

Tushar Somaiya co-trained with Dr. Andreas Wintersteiger in a Certified Scrum Master (CSM) class in Pune, India. Dr. Wintersteiger observed Tushar facilitate sessions on Scrum roles, product backlog, user stories, and Scrum meetings. He saw that Tushar has a solid understanding of Scrum and agile principles. Dr. Wintersteiger also felt that Tushar's training style was effective at conveying information to participants and that he incorporated feedback to improve. Therefore, Dr. Wintersteiger fully supports Tushar's application to become a Certified Scrum Trainer.

4 - Recommendation From Gregory Smith For Tushar Somaiya

Tushar Somaiya

2 - Recommendation From Kiran Thakker For Tushar Somaiya

Tushar Somaiya

Kiran Thakkar, an Agile coach and trainer, observed Tushar Somaiya, an Agile coach at Thoughtworks in Mumbai, India, co-train at Kiran's two-day Certified Scrum Master course in September 2012. Kiran found Tushar to be very knowledgeable and passionate about Scrum and agile development. Tushar co-trained effectively on topics like agile benefits, sprint reviews and retrospectives, keeping the class engaged. Kiran recommends Tushar conduct additional co-training outside of India to experience different audiences and styles.

1 - Recommendtion From Alan Atlas For Tushar Somaiya

Tushar Somaiya

Tushar Somaiya co-trained a CSM class in New Delhi with Alan Atlas in February 2012. They exchanged course materials and modified Atlas' basic CSM course for Somaiya to deliver. Feedback on the class was very positive. Atlas was impressed with Somaiya's enthusiasm and eagerness for Agile, which made him an effective instructor. He also enjoyed conversations with Somaiya and feels he is ready to be a CST based on his experience and stories about real world work with Scrum.

Scale agile down instead of scaling it up

Tushar Somaiya

People everywhere are talking about scaling agile and different frameworks and ideas to support this. Fancy and rather complicated scaling agile frameworks have not only taken shape but probably have started becoming mainstream. All these frameworks apparently claim to facilitate communication and collaboration. However, as group size rises, all sorts of issues emerges. Even if more people provide a greater pool of resources, they also require greater amounts of coordination and management, to the point where size becomes an impediment. Scaling up might trigger not only “coordination loss” & “motivation loss” but also “relational loss”. Small teams are agile!! I guess, thats the reason Scrum urges to work in small teams. As small as 5 to 9 members. So let’s explore if there is a possibility to scale down instead of scaling up? And, how can you scale down? What does it take? Has anyone scaled down yet? Is there a structure to scale down? Can it be replicated?

Agile Lecture at S. P. Jain Institute of Management and Research

Tushar Somaiya

Why scrum works - A NeuroScience Perspective @ Scrum Gathering India 2013

Tushar Somaiya

Have you ever thought why scrum works? That too from NeuroScience perspective? We all acknowledge and understand that we have moved beyond and past machine age or service era and are living in what is called “Knowledge Era”. Focus of current times is shifting from behaviours to values. From people to brain. Yet, we know very little about people or brain or its working. Through this talk, I will attempt to link hard neuroscience to scrum and its practices to see why it works or does not work. Also we would look at practices required beyond scrum to create an environment where scrum can flourish. Or even exists!

Introduction to agile

Tushar Somaiya

Role of scrum master

Tushar Somaiya

It is the team who does all the work. Team is self-organising. Team decides and plans. So what is the role of scrum master? Is it a full time role? How is it different from a project manager? Can a project lead or manager be a scrum master? It is probably the least understood and the most abused role in scrum. Let's explore these points in details further on April 10, 3:00 PM. 3 Roles in Scrum Role of scrum master Challenges of a scrum master Skills, Knowledge & mindset required Full time or part time? Future career path of scrum master Benefits: Uncover the true role of a scrum master which is that of a facilitator, protector, negotiator and a coach. Understand the true meaning of coaching. Learn how scrum master can coach the team. Understand the skills, knowledge and mindset required as a scrum master. Perform better as a scrum master by getting introduced to some magical techniques and fad words like gamestorming, innovation games and visual thinking to facilitate collaborative decision making. Learn points which you can use to make people understand the vital role a scrum master plays. Appreciate the difference between project manager and a scrum master. Learn who can be a good scrum master. Attend the webinar and separate yourself from the crazy herd of people blindly accepting or discarding the role of scrum master!!

Agile pandemic.pptx

Tushar Somaiya

Executives role in agile

Tushar Somaiya

Tushar Somaiya is an experienced agile coach and trainer who founded ShuHaRiAgile and CoachingDojo to provide agile training and coaching. He has over 13 years of IT experience and 6 years of agile experience. He is a certified coach who helps teams discover their potential through neuroscience-based coaching. Tushar is passionate about creating democratic and self-organizing teams and believes in servant leadership.

More from Tushar Somaiya (13)

7 - Recommendation From Decos For Tushar Somaiya

6 - Recommendation From ABS For Tushar Somaiya

5 - Remommendation From Andreas Wintersteiger For Tushar Somaiya

4 - Recommendation From Gregory Smith For Tushar Somaiya

2 - Recommendation From Kiran Thakker For Tushar Somaiya

1 - Recommendtion From Alan Atlas For Tushar Somaiya

Scale agile down instead of scaling it up

Agile Lecture at S. P. Jain Institute of Management and Research

Why scrum works - A NeuroScience Perspective @ Scrum Gathering India 2013

Introduction to agile

Role of scrum master

Agile pandemic.pptx

Executives role in agile

Recently uploaded

Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...

Erasmo Purificato

20240702 QFM021 Machine Intelligence Reading List June 2024

Matthew Sinclair

WhatsApp Image 2024-03-27 at 08.19.52_bfd93109.pdf

ArgaBisma

一比一原版(msvu毕业证书）圣文森山大学毕业证如何办理

uuuot

原版一模一样【微信：741003700 】【(msvu毕业证书）圣文森山大学毕业证成绩单】【微信：741003700 】学位证，留信学历认证（真实可查，永久存档）原件一模一样纸张工艺/offer、在读证明、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。本公司拥有海外各大学样板无数，能完美还原。 1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700 【主营项目】一.毕业证【q微741003700】成绩单、使馆认证、教育部认证、雅思托福成绩单、学生卡等！二.真实使馆公证(即留学回国人员证明,不成功不收费) 三.真实教育部学历学位认证（教育部存档！教育部留服网站永久可查）四.办理各国各大学文凭(一对一专业服务,可全程监控跟踪进度) 如果您处于以下几种情况： ◇在校期间，因各种原因未能顺利毕业……拿不到官方毕业证【q/微741003700】 ◇面对父母的压力，希望尽快拿到； ◇不清楚认证流程以及材料该如何准备； ◇回国时间很长，忘记办理； ◇回国马上就要找工作，办给用人单位看； ◇企事业单位必须要求办理的 ◇需要报考公务员、购买免税车、落转户口 ◇申请留学生创业基金留信网认证的作用: 1:该专业认证可证明留学生真实身份 2:同时对留学生所学专业登记给予评定 3:国家专业人才认证中心颁发入库证书 4:这个认证书并且可以归档倒地方 5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息 6:个人职称评审加20分 7:个人信誉贷款加10分 8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才办理(msvu毕业证书）圣文森山大学毕业证【微信：741003700 】外观非常简单，由纸质材料制成，上面印有校徽、校名、毕业生姓名、专业等信息。办理(msvu毕业证书）圣文森山大学毕业证【微信：741003700 】格式相对统一，各专业都有相应的模板。通常包括以下部分：校徽：象征着学校的荣誉和传承。校名:学校英文全称授予学位：本部分将注明获得的具体学位名称。毕业生姓名：这是最重要的信息之一，标志着该证书是由特定人员获得的。颁发日期：这是毕业正式生效的时间，也代表着毕业生学业的结束。其他信息：根据不同的专业和学位，可能会有一些特定的信息或章节。办理(msvu毕业证书）圣文森山大学毕业证【微信：741003700 】价值很高，需要妥善保管。一般来说，应放置在安全、干燥、防潮的地方，避免长时间暴露在阳光下。如需使用，最好使用复印件而不是原件，以免丢失。综上所述，办理(msvu毕业证书）圣文森山大学毕业证【微信：741003700 】是证明身份和学历的高价值文件。外观简单庄重，格式统一，包括重要的个人信息和发布日期。对持有人来说，妥善保管是非常重要的。

Research Directions for Cross Reality Interfaces

Mark Billinghurst

Coordinate Systems in FME 101 - Webinar Slides

Safe Software

If you’ve ever had to analyze a map or GPS data, chances are you’ve encountered and even worked with coordinate systems. As historical data continually updates through GPS, understanding coordinate systems is increasingly crucial. However, not everyone knows why they exist or how to effectively use them for data-driven insights. During this webinar, you’ll learn exactly what coordinate systems are and how you can use FME to maintain and transform your data’s coordinate systems in an easy-to-digest way, accurately representing the geographical space that it exists within. During this webinar, you will have the chance to: - Enhance Your Understanding: Gain a clear overview of what coordinate systems are and their value - Learn Practical Applications: Why we need datams and projections, plus units between coordinate systems - Maximize with FME: Understand how FME handles coordinate systems, including a brief summary of the 3 main reprojectors - Custom Coordinate Systems: Learn how to work with FME and coordinate systems beyond what is natively supported - Look Ahead: Gain insights into where FME is headed with coordinate systems in the future Don’t miss the opportunity to improve the value you receive from your coordinate system data, ultimately allowing you to streamline your data analysis and maximize your time. See you there!

The Increasing Use of the National Research Platform by the CSU Campuses

Larry Smarr

“Intel’s Approach to Operationalizing AI in the Manufacturing Sector,” a Pres...

Edge AI and Vision Alliance

For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/07/intels-approach-to-operationalizing-ai-in-the-manufacturing-sector-a-presentation-from-intel/ Tara Thimmanaik, AI Systems and Solutions Architect at Intel, presents the “Intel’s Approach to Operationalizing AI in the Manufacturing Sector,” tutorial at the May 2024 Embedded Vision Summit. AI at the edge is powering a revolution in industrial IoT, from real-time processing and analytics that drive greater efficiency and learning to predictive maintenance. Intel is focused on developing tools and assets to help domain experts operationalize AI-based solutions in their fields of expertise. In this talk, Thimmanaik explains how Intel’s software platforms simplify labor-intensive data upload, labeling, training, model optimization and retraining tasks. She shows how domain experts can quickly build vision models for a wide range of processes—detecting defective parts on a production line, reducing downtime on the factory floor, automating inventory management and other digitization and automation projects. And she introduces Intel-provided edge computing assets that empower faster localized insights and decisions, improving labor productivity through easy-to-use AI tools that democratize AI.

GDG Cloud Southlake #34: Neatsun Ziv: Automating Appsec

James Anderson

The lecture titled "Automating AppSec" delves into the critical challenges associated with manual application security (AppSec) processes and outlines strategic approaches for incorporating automation to enhance efficiency, accuracy, and scalability. The lecture is structured to highlight the inherent difficulties in traditional AppSec practices, emphasizing the labor-intensive triage of issues, the complexity of identifying responsible owners for security flaws, and the challenges of implementing security checks within CI/CD pipelines. Furthermore, it provides actionable insights on automating these processes to not only mitigate these pains but also to enable a more proactive and scalable security posture within development cycles. The Pains of Manual AppSec: This section will explore the time-consuming and error-prone nature of manually triaging security issues, including the difficulty of prioritizing vulnerabilities based on their actual risk to the organization. It will also discuss the challenges in determining ownership for remediation tasks, a process often complicated by cross-functional teams and microservices architectures. Additionally, the inefficiencies of manual checks within CI/CD gates will be examined, highlighting how they can delay deployments and introduce security risks. Automating CI/CD Gates: Here, the focus shifts to the automation of security within the CI/CD pipelines. The lecture will cover methods to seamlessly integrate security tools that automatically scan for vulnerabilities as part of the build process, thereby ensuring that security is a core component of the development lifecycle. Strategies for configuring automated gates that can block or flag builds based on the severity of detected issues will be discussed, ensuring that only secure code progresses through the pipeline. Triaging Issues with Automation: This segment addresses how automation can be leveraged to intelligently triage and prioritize security issues. It will cover technologies and methodologies for automatically assessing the context and potential impact of vulnerabilities, facilitating quicker and more accurate decision-making. The use of automated alerting and reporting mechanisms to ensure the right stakeholders are informed in a timely manner will also be discussed. Identifying Ownership Automatically: Automating the process of identifying who owns the responsibility for fixing specific security issues is critical for efficient remediation. This part of the lecture will explore tools and practices for mapping vulnerabilities to code owners, leveraging version control and project management tools. Three Tips to Scale the Shift Left Program: Finally, the lecture will offer three practical tips for organizations looking to scale their Shift Left security programs. These will include recommendations on fostering a security culture within development teams, employing DevSecOps principles to integrate security throughout the development

[Talk] Moving Beyond Spaghetti Infrastructure [AOTB] 2024-07-04.pdf

Kief Morris

Pigging Solutions Sustainability brochure.pdf

Pigging Solutions

Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment. How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.

How Netflix Builds High Performance Applications at Global Scale

ScyllaDB

AC Atlassian Coimbatore Session Slides( 22/06/2024)

apoorva2579

MYIR Product Brochure - A Global Provider of Embedded SOMs & Solutions

Linda Zhang

This brochure gives introduction of MYIR Electronics company and MYIR's products and services. MYIR Electronics Limited (MYIR for short), established in 2011, is a global provider of embedded System-On-Modules (SOMs) and comprehensive solutions based on various architectures such as ARM, FPGA, RISC-V, and AI. We cater to customers' needs for large-scale production, offering customized design, industry-specific application solutions, and one-stop OEM services. MYIR, recognized as a national high-tech enterprise, is also listed among the "Specialized and Special new" Enterprises in Shenzhen, China. Our core belief is that "Our success stems from our customers' success" and embraces the philosophy of "Make Your Idea Real, then My Idea Realizing!"

@Call @Girls Pune 0000000000 Riya Khan Beautiful Girl any Time

amitchopra0215

Cookies program to display the information though cookie creation

shanthidl1

Running a Go App in Kubernetes: CPU Impacts

ScyllaDB

K2G - Insurtech Innovation EMEA Award 2024

The Digital Insurer

BLOCKCHAIN FOR DUMMIES: GUIDEBOOK FOR ALL

Liveplex

What's Next Web Development Trends to Watch.pdf

SeasiaInfotech2

Recently uploaded (20)

Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...

20240702 QFM021 Machine Intelligence Reading List June 2024

WhatsApp Image 2024-03-27 at 08.19.52_bfd93109.pdf

一比一原版(msvu毕业证书）圣文森山大学毕业证如何办理

Research Directions for Cross Reality Interfaces

Coordinate Systems in FME 101 - Webinar Slides

The Increasing Use of the National Research Platform by the CSU Campuses

“Intel’s Approach to Operationalizing AI in the Manufacturing Sector,” a Pres...

GDG Cloud Southlake #34: Neatsun Ziv: Automating Appsec

[Talk] Moving Beyond Spaghetti Infrastructure [AOTB] 2024-07-04.pdf

Pigging Solutions Sustainability brochure.pdf

How Netflix Builds High Performance Applications at Global Scale

AC Atlassian Coimbatore Session Slides( 22/06/2024)

MYIR Product Brochure - A Global Provider of Embedded SOMs & Solutions

@Call @Girls Pune 0000000000 Riya Khan Beautiful Girl any Time

Cookies program to display the information though cookie creation

Running a Go App in Kubernetes: CPU Impacts

K2G - Insurtech Innovation EMEA Award 2024

BLOCKCHAIN FOR DUMMIES: GUIDEBOOK FOR ALL

What's Next Web Development Trends to Watch.pdf

Enterprise Agile Transformation Enablers

1. Enterprise Agile Transformation Enablers - Tushar Somaiya

3. Team Transformation

4. Let’s Go Agile So the story goes…

5. INDIVIDUALS & INTERACTIONS OVER Processes and tools WORKING SOFTWARE OVER Comprehensive Documentation CUSTOMER COLLABORATION OVER Contract Negotiation RESPONDING TO CHANGE OVER Following A Plan TRUST Let’s Find Out More About Agile http://agilemanifesto.org/

6. Sounds Interesting, Tell Me More… Let’s Focus On implementing 1st Principle Only: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software

7. But How Do We Do It?

8. Let’s Try 2 Week Iteration 10 stories 10 stories 10 stories 10 stories Time Up!!! No time for testing or no time to deploy and UAT Waterfall Within 2 Weeks Iteration (Anti-Pattern)

9. Let’s Try 2 Week Iteration 10 stories Let’s say we do manage get all 10 stories tested, deployed, UATed and release them in production to earn some ROI

10. What Happens In Iteration 2? 10 stories + 10 stories (regression) 10 stories 10 stories 10 stories Time Up!!! No time for testing or no time to deploy and UAT

11. What Happens In Iteration 3? 10 stories + 20 stories (regression) QA starts falling behind and works 1 or 2 iterations behind dev Dev QA

12. What Happens In Iteration 3? Slowly but surely devs and qas would start working out of their own backlog. The divide keeps increasing. Dev QA

13. Water Scrum Fall (Anti-Pattern)

14. If Not Waterfall Then What?

15. Let’s Understand Waterfall (QUEUE)

16. Queue Analysis Code TestDesign

17. Queue Analysis Code TestDesign

18. Queue Analysis Code TestDesign

19. Queue Analysis Code TestDesign

20. Queue Analysis Code TestDesign

21. Queue Analysis Code TestDesign

22. Queue Analysis Code TestDesign

23. Queue Analysis Code TestDesign

24. Queue Analysis Code TestDesign

25. Queue Analysis Code TestDesign

26. Queue Analysis Code TestDesign

27. Queue Analysis Code TestDesign

28. Queue Analysis Code TestDesign

29. Queue Analysis Code TestDesign

30. Queue Analysis Code TestDesign

31. Queue Analysis Code TestDesign

32. Queue Analysis Code TestDesign

33. Queue Analysis Code TestDesign

34. Queue Analysis Code TestDesign

35. Queue Analysis Code TestDesign

36. Queue Analysis Code TestDesign

37. Let’s Understand Agile (FLOW)

38. Flow (Good Iteration Is Working On One Story At A Time) Analysis Code TestDesign

39. Flow (Good Iteration Is Working On One Story At A Time) Analysis Code TestDesign

40. Flow (Good Iteration Is Working On One Story At A Time) Analysis Code TestDesign

41. Flow (Good Iteration Is Working On One Story At A Time) Analysis Code TestDesign

42. Flow (Good Iteration Is Working On One Story At A Time) Analysis Code TestDesign

43. Flow (Good Iteration Is Working On One Story At A Time) Analysis Code TestDesign

44. Flow (Good Iteration Is Working On One Story At A Time) Analysis Code TestDesign

45. Flow (Good Iteration Is Working On One Story At A Time) Analysis Code TestDesign

46. Flow (Good Iteration Is Working On One Story At A Time) Analysis Code TestDesign

47. Got It! Let’s Try 2 Week Flow 10 stories This is working!!! 1 story at a time 1 story at a time

48. What Happens In 4th Iteration? 10 stories We would have 10 new stories + 30 old stories to regress! 1 story at a time 1 story at a time

49. Well, now what?

50. Automation Is The Key

51. So We Try Traditional GUI – Driven Automation Requirements Design CodeManual Test Automate Manual Tests

52. Waiting For Feature To Be Ready? (Anti – Pattern) And when the automated regression pack fails we do not know whether it is due to “real” bug or is it due to brittle UI driven tests which are “old” now Does it solve the purpose? Dev QA 1 story at a time

53. Let’s Isolate Concerns (GUI & API)

54. Let Go Of Ice Cream Cone (Inverted Testing Pyramid)

55. Our Concerns Are Isolated, We Can Now Test First & Fast

56. After 3 Good Iterations… 1 story at a time 1 story at a time 1 story at a time 15 Features + Automated Regression Of 37…. Well, Now We Are Doing Good 10 12 15

57. But, Now Can Business Keep Up? 1 story at a time• We are building system very fast • System is working correctly • But is it correct system? Dev & QA UAT

58. Hence, Automate Acceptance Testing

59. Caution: BDD Is NOT Automation Framework

60. Too Many Units… How To Integrate & Deploy All Units?

61. Can Ops Keep Up Now?

62. Phew, That Was Easy! Let’s Focus On implementing 1st Principle Only: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software 2 Weeks Iteration TDD, CI, CD, Devops BDD, Iterative UAT, Exploratory Production Ready software with live specifications

63. Let’s Transform Enterprise Now!

64. The whole is greater than sum of its parts

66. #1 Define “Real” Business Goals

67. #2 Coach Correct Set Of People

68. Business Engagement QA Automation DevOps Org & People

69. #3 Go Deeper OVER Wider

70. #4 Defer tooling and standardization

72. #5 Form & Fund Change Canoes

74. #7 Measure & Celebrate Success Progress

75. #8 Time To Scale

76. Enterprise Agile Transformation Enablers 1. Define “Real” Business Goals 2. Coaching Correct Set Of People 3. Go Deeper Over Wider 4. Defer Tooling And Standardization 5. Form & Fund Change Canoes 6. Empower, Enhance, Enable and Engage 7. Measure and celebrate 8. Time To Scale

77. Tushar Somaiya Tushar.somaiya@gmail.com 9869209689 @tusharsomaiya

Enterprise Agile Transformation Enablers

More Related Content

What's hot

What's hot (20)

Similar to Enterprise Agile Transformation Enablers

Similar to Enterprise Agile Transformation Enablers (20)

More from Tushar Somaiya

More from Tushar Somaiya (13)

Recently uploaded

Recently uploaded (20)

Enterprise Agile Transformation Enablers