Scrum is a great way to start practising Agile. But it's not perfect. Are you struggling to get stories tested within the sprint? I sprint planning taking hours and making everyone miserable? These are the slides from the session I presented at Agile Cymru 2016, describing the experience of one team that moved from Scrum to Kanban.
Class syllabus and notes on various digital workflow considerations for photographers. Covers color spaces, backup strategies, file management, and business workflow.
Most of the times I have seen the teams spending immense amount of time in mastering the mechanics than the intent.
Key to successful agile adoption is to have the agile as a team culture than just doing it
My upcoming webinar session titled "State of the art Development Workflow in Agile" will be held on 14th of March 2021.
* Why Agile?
* Popular Agile Frameworks
* Ins and Outs of Scrum - Roles, Values, Events
* Development Workflow
* Branching Strategy
Internal presentation to sum up what it is (and what it is not) Agile.
It was designed as an introduction to the other presentation called "Agile methodologies in short": http://www.slideshare.net/lalaianohies/agile-methodologies-in-short
Whether your business is a small, fast-growing agile shop, or a larger company that is trying to adopt agile methodologies, success hinges on a proper foundation of roles, responsibilities, and processes. In this talk, we’ll cover how Trulia tackles these areas, and discuss how JIRA Agile helped us expand our agile cycles.
Class syllabus and notes on various digital workflow considerations for photographers. Covers color spaces, backup strategies, file management, and business workflow.
Most of the times I have seen the teams spending immense amount of time in mastering the mechanics than the intent.
Key to successful agile adoption is to have the agile as a team culture than just doing it
My upcoming webinar session titled "State of the art Development Workflow in Agile" will be held on 14th of March 2021.
* Why Agile?
* Popular Agile Frameworks
* Ins and Outs of Scrum - Roles, Values, Events
* Development Workflow
* Branching Strategy
Internal presentation to sum up what it is (and what it is not) Agile.
It was designed as an introduction to the other presentation called "Agile methodologies in short": http://www.slideshare.net/lalaianohies/agile-methodologies-in-short
Whether your business is a small, fast-growing agile shop, or a larger company that is trying to adopt agile methodologies, success hinges on a proper foundation of roles, responsibilities, and processes. In this talk, we’ll cover how Trulia tackles these areas, and discuss how JIRA Agile helped us expand our agile cycles.
There are seven things that slow your software team down. Learning to conquer each of them is the key delivering faster.
Originating in the Japanese manufacturing industry in the middle of the 20th century, the ideas behind the seven wastes are still hugely relevant to software development today. I explained each one and how it slows you down, then explained how you can defeat the seven wastes and deliver faster than ever before.
This two-part interactive workshop begins with a detailed look at how to interpret Kanban boards and ask thoughtful questions so that you can improve the work of your teams. We will provide an overview of the Kanban Method and then proceed through a series of eight short exercises that will give you an opportunity to review and interpret various Kanban board configurations with other attendees at your table. After a short break, part two of the session now puts the attendees in the driver’s seat to create their own board configurations. We provide eight business scenario exercises and ask the attendees how they would go about configuring their Kanban board given the unique system constraints for each scenario.
Last year, Stormpath made the big shift from Scrum to Kanban. While we love Agile principles, the Scrum process wasn’t working for us. Kanban made our team more efficient, happier, and increased our focus on quality software. More importantly, it has become a core part of our company culture, and is now used by non-technical teams like Marketing and HR.
Kanban software development focuses on continuous delivery and drives high efficiency by limiting how much work can be done at once. Invented by Toyota and modified by David J. Anderson for software development, Kanban can have a huge impact on modern teams delivering cloud software in continuous environments.
You’re already selling ahead of your roadmap and your dev team is getting pretty big. Trish Khoo outlines two approaches to keeping pace and quality high without hiring an army, drawing on a decade of software testing at Campaign Monitor, Google and Microsoft.
In every successful technology businesses Jeff has worked in, the key challenge has been understanding how to scale technology and when to tackle the technical debt that inevitably accrues as a company runs ever faster and faster in pursuit of its business objectives. Jeff draws on his experience to help you understand what challenges emerge as a company moves from a Developer Centric environment to become more business focused. How can you get the business people to have influence on a developer centric environment? How can you manage the challenges that marketing will present?! What principles can you apply to be aware of problems early? How do you trade Agile Practioners vs Architectural Astronauts in a fast growing business? What are the technical debt trade-offs, what problems can you buy yourself out of? What problems will kill you if you don’t move now?
While most Kanban games usually focus only on the flow of an existing Kanban system demonstrating the path from an existing process to Kanban, this game allows you to learn more about the Kanban philosophy and how to work with it. Learning by doing and having fun at the same time.
The Life of a Feature in Agile Development - Eric DalglieshAtlassian
Here at Atlassian, we are all about creating the best tools to help you get the most out of your agile development. In this session, we'll cover the basics of how we use our products to develop a feature. We'll also show you a few ways to use our products that you might not have considered, that could kick your productivity up a notch. This talk highlights JIRA, Bamboo, HipChat, and Stash.
Introductory Deck used to present Agile framework - Mostly Scrum - to graduate students at Nova Southeastern University.
I was invited as a guest lecturer several times and this is the deck used.
Briefing to educate project managers on two core Agile techniques - Scrum and Kanban. For those with Agile experience, it goes on to present a number of common challenges to successful Agile adoption and how to address those challenges.
So you’ve optimized Kanban at the team level but true to the Theory of Constraints its uncovered new challenges. Cross team dependencies block progress for one team at the expense of another. Individual backlogs create competing priorities for critical resources. Roadmaps for what to work on next are out of date before you can hit print.
Sounds like you need to expand your Kanban. While this may seem like the solution to all the same problems you had at the team level, lets dig into what patterns are different at the portfolio level. Soloed team expertise, fear and hidden work, lack of visibility across projects, and optimization for one problem without regard for another. But as the system matures you will see status meetings disappear, impromptu gatherings around the board, organizing around the highest priority work and more informed decision making.
You aren’t the first organization to be here, so let's break down what you can expect along the way.
A conversation about effective support for your website, with project management, the lifecycle of a project, and many stories.
I've added in a section for smaller dev shops who want a model for maintenance for their projects.
Tilt does not currently employ any quality engineers. How can we deliver quality software? Over the last year the organization has gone from terrifying deploys (followed by
There are seven things that slow your software team down. Learning to conquer each of them is the key delivering faster.
Originating in the Japanese manufacturing industry in the middle of the 20th century, the ideas behind the seven wastes are still hugely relevant to software development today. I explained each one and how it slows you down, then explained how you can defeat the seven wastes and deliver faster than ever before.
This two-part interactive workshop begins with a detailed look at how to interpret Kanban boards and ask thoughtful questions so that you can improve the work of your teams. We will provide an overview of the Kanban Method and then proceed through a series of eight short exercises that will give you an opportunity to review and interpret various Kanban board configurations with other attendees at your table. After a short break, part two of the session now puts the attendees in the driver’s seat to create their own board configurations. We provide eight business scenario exercises and ask the attendees how they would go about configuring their Kanban board given the unique system constraints for each scenario.
Last year, Stormpath made the big shift from Scrum to Kanban. While we love Agile principles, the Scrum process wasn’t working for us. Kanban made our team more efficient, happier, and increased our focus on quality software. More importantly, it has become a core part of our company culture, and is now used by non-technical teams like Marketing and HR.
Kanban software development focuses on continuous delivery and drives high efficiency by limiting how much work can be done at once. Invented by Toyota and modified by David J. Anderson for software development, Kanban can have a huge impact on modern teams delivering cloud software in continuous environments.
You’re already selling ahead of your roadmap and your dev team is getting pretty big. Trish Khoo outlines two approaches to keeping pace and quality high without hiring an army, drawing on a decade of software testing at Campaign Monitor, Google and Microsoft.
In every successful technology businesses Jeff has worked in, the key challenge has been understanding how to scale technology and when to tackle the technical debt that inevitably accrues as a company runs ever faster and faster in pursuit of its business objectives. Jeff draws on his experience to help you understand what challenges emerge as a company moves from a Developer Centric environment to become more business focused. How can you get the business people to have influence on a developer centric environment? How can you manage the challenges that marketing will present?! What principles can you apply to be aware of problems early? How do you trade Agile Practioners vs Architectural Astronauts in a fast growing business? What are the technical debt trade-offs, what problems can you buy yourself out of? What problems will kill you if you don’t move now?
While most Kanban games usually focus only on the flow of an existing Kanban system demonstrating the path from an existing process to Kanban, this game allows you to learn more about the Kanban philosophy and how to work with it. Learning by doing and having fun at the same time.
The Life of a Feature in Agile Development - Eric DalglieshAtlassian
Here at Atlassian, we are all about creating the best tools to help you get the most out of your agile development. In this session, we'll cover the basics of how we use our products to develop a feature. We'll also show you a few ways to use our products that you might not have considered, that could kick your productivity up a notch. This talk highlights JIRA, Bamboo, HipChat, and Stash.
Introductory Deck used to present Agile framework - Mostly Scrum - to graduate students at Nova Southeastern University.
I was invited as a guest lecturer several times and this is the deck used.
Briefing to educate project managers on two core Agile techniques - Scrum and Kanban. For those with Agile experience, it goes on to present a number of common challenges to successful Agile adoption and how to address those challenges.
So you’ve optimized Kanban at the team level but true to the Theory of Constraints its uncovered new challenges. Cross team dependencies block progress for one team at the expense of another. Individual backlogs create competing priorities for critical resources. Roadmaps for what to work on next are out of date before you can hit print.
Sounds like you need to expand your Kanban. While this may seem like the solution to all the same problems you had at the team level, lets dig into what patterns are different at the portfolio level. Soloed team expertise, fear and hidden work, lack of visibility across projects, and optimization for one problem without regard for another. But as the system matures you will see status meetings disappear, impromptu gatherings around the board, organizing around the highest priority work and more informed decision making.
You aren’t the first organization to be here, so let's break down what you can expect along the way.
A conversation about effective support for your website, with project management, the lifecycle of a project, and many stories.
I've added in a section for smaller dev shops who want a model for maintenance for their projects.
Tilt does not currently employ any quality engineers. How can we deliver quality software? Over the last year the organization has gone from terrifying deploys (followed by
Spiking Your Way to Improved Agile Development - Anatoli KazatchkovAtlassian
New feature development in agile should almost always start with a spike. Spikes help to define feature scope, uncover technical unknowns, and provide accurate estimates. In this session we will cover how to introduce spikes into your development cycles and show how Atlassian defines spike goals, focuses spike efforts, and makes feature development more effective.
A brief reflection on the Waterfall approach, review the Scrum elements and artifacts, and their purpose. Demonstrate Agile Scrum by providing real-world examples that delivered successful measurable outcomes to the business.
A 1 Day training that shows you all you need to know about Scrum, the afternoon contains a practical part where we perform several sprints using Lego as our means of production
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.
Technical Excellence Doesn't Just Happen--Igniting a Craftsmanship CultureAllison Pollard
The ninth principle from the Agile Manifesto states that technical excellence enhances agility, but when the codebase is ugly and the deadlines are tight, most teams don’t choose to refactor mercilessly, adopt TDD, or evaluate automated testing tools—unless they have the proper support. In our experience working with multiple teams in a single codebase, developers can feel victim to a legacy codebase if only a few people are writing clean code or refactoring; guiding them on how to decrease technical debt while delivering their projects helps "unstuck" their other agile practices. We will talk about the challenges we’ve seen with Product Owners, Managers, and Scrum Masters interacting with teams at various stages of agile+technical excellence and how a focus on technical practices sparked a wider interest in craftsmanship. Learn how can you influence the team towards the right practices while fostering their sense of ownership. Getting serious about technical excellence requires support from technical and non-technical roles, and we’ll share how we partnered as coaches to help an organization through a technical turnaround with some tips for others who need to do the same.
Creating change from within - Agile Practitioners 2012Dror Helper
Faced with management that do not care about "being agile" what can a single developer do? Quite a lot!
Every developer has the power to improve the organization he works in in small iterative steps – and I can show you how.
If you want to make the change and don't know where to start – look no further, in this session I'll share my experience and show a few tips and tricks I learnt. As well as discuss the do and don'ts that can make all the.
- How to be agile developer in a waterfall company.
- Influencing people without formal authority.
- Using the right practices that makes the difference
- How to avoid alienating people
- Discovering your allies
- Know when to fight and when to "retreat" and cut your losses
- Making a change without disrupting the daily routine
- What being an agile evangelist is all about
This was a presentation given at San Diego Python's Django Day:
http://www.meetup.com/pythonsd/events/95751792/
https://github.com/pythonsd/learning-django
Lean Kanban India 2019 Conference | Agility and DevOps: Needed - an Integrate...LeanKanbanIndia
Session Title: Agility and DevOps: Needed - an Integrated view
Abstract: Why do we associate Business Agility with Kanban and Agile, and Flow of IT work with DevOps? Too much of our DevOps discussion focuses on the throughput, the flow and the automation, and not enough on alignment to Business Value in DevOps. One reason DevOps has been enthusiastically picked up by the Indian IT community is that it seems within IT’s control; the language of CALMS all seem safely within IT’s reach.
This will lead your DevOps journey into a dead end.
This session will pick very different companies on DevOps journeys, and identify the drivers that took these companies onto the Agility journey.
Lean-Agile Development with SharePoint - Bill AyersSPC Adriatics
SharePoint gives us a great platform for developing sophisticated intranet portals and collaboration sites and many other workloads. But it can also be a challenge to use modern software development frameworks like Scrum and XP. Wouldn’t it be great if we could get all the benefits of Agile practices – faster development, predictable deliveries, better quality, less stress and happy stakeholders? In this session we will cover the definitions of Lean, Agile, Scrum, Kanban, XP, and TDD. Then we will look at the specific challenges around Agile SharePoint development and some development techniques to overcome these obstacles. This talk covers both project delivery and engineering. We’ll look at unit tests, integration tests, UI tests, continuous integration and, of course, test-driven development (TDD) with practical experiences from real-life Agile SharePoint projects.
Agile Software Development in practice: Experience, Tips and Tools from the T...Valerie Puffet-Michel
In the Division of Student Affairs at the University of Connecticut, the Applications Development team has been developing and delivering custom software using agile methods for over four years. In this session, we'll share our experiences and give you a behind the scenes look at how agile software development really works by walking you through how we translate the unique business needs of our clients into deployed software.
Similar to Scrum is good - but kanban is better (20)
Developing Distributed High-performance Computing Capabilities of an Open Sci...Globus
COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.
A Study of Variable-Role-based Feature Enrichment in Neural Models of CodeAftab Hussain
Understanding variable roles in code has been found to be helpful by students
in learning programming -- could variable roles help deep neural models in
performing coding tasks? We do an exploratory study.
- These are slides of the talk given at InteNSE'23: The 1st International Workshop on Interpretability and Robustness in Neural Software Engineering, co-located with the 45th International Conference on Software Engineering, ICSE 2023, Melbourne Australia
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI AppGoogle
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-fusion-buddy-review
AI Fusion Buddy Review: Key Features
✅Create Stunning AI App Suite Fully Powered By Google's Latest AI technology, Gemini
✅Use Gemini to Build high-converting Converting Sales Video Scripts, ad copies, Trending Articles, blogs, etc.100% unique!
✅Create Ultra-HD graphics with a single keyword or phrase that commands 10x eyeballs!
✅Fully automated AI articles bulk generation!
✅Auto-post or schedule stunning AI content across all your accounts at once—WordPress, Facebook, LinkedIn, Blogger, and more.
✅With one keyword or URL, generate complete websites, landing pages, and more…
✅Automatically create & sell AI content, graphics, websites, landing pages, & all that gets you paid non-stop 24*7.
✅Pre-built High-Converting 100+ website Templates and 2000+ graphic templates logos, banners, and thumbnail images in Trending Niches.
✅Say goodbye to wasting time logging into multiple Chat GPT & AI Apps once & for all!
✅Save over $5000 per year and kick out dependency on third parties completely!
✅Brand New App: Not available anywhere else!
✅ Beginner-friendly!
✅ZERO upfront cost or any extra expenses
✅Risk-Free: 30-Day Money-Back Guarantee!
✅Commercial License included!
See My Other Reviews Article:
(1) AI Genie Review: https://sumonreview.com/ai-genie-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIFusionBuddyReview,
#AIFusionBuddyFeatures,
#AIFusionBuddyPricing,
#AIFusionBuddyProsandCons,
#AIFusionBuddyTutorial,
#AIFusionBuddyUserExperience
#AIFusionBuddyforBeginners,
#AIFusionBuddyBenefits,
#AIFusionBuddyComparison,
#AIFusionBuddyInstallation,
#AIFusionBuddyRefundPolicy,
#AIFusionBuddyDemo,
#AIFusionBuddyMaintenanceFees,
#AIFusionBuddyNewbieFriendly,
#WhatIsAIFusionBuddy?,
#HowDoesAIFusionBuddyWorks
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
Top 7 Unique WhatsApp API Benefits | Saudi ArabiaYara Milbes
Discover the transformative power of the WhatsApp API in our latest SlideShare presentation, "Top 7 Unique WhatsApp API Benefits." In today's fast-paced digital era, effective communication is crucial for both personal and professional success. Whether you're a small business looking to enhance customer interactions or an individual seeking seamless communication with loved ones, the WhatsApp API offers robust capabilities that can significantly elevate your experience.
In this presentation, we delve into the top 7 distinctive benefits of the WhatsApp API, provided by the leading WhatsApp API service provider in Saudi Arabia. Learn how to streamline customer support, automate notifications, leverage rich media messaging, run scalable marketing campaigns, integrate secure payments, synchronize with CRM systems, and ensure enhanced security and privacy.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Code reviews are vital for ensuring good code quality. They serve as one of our last lines of defense against bugs and subpar code reaching production.
Yet, they often turn into annoying tasks riddled with frustration, hostility, unclear feedback and lack of standards. How can we improve this crucial process?
In this session we will cover:
- The Art of Effective Code Reviews
- Streamlining the Review Process
- Elevating Reviews with Automated Tools
By the end of this presentation, you'll have the knowledge on how to organize and improve your code review proces
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Gamify Your Mind; The Secret Sauce to Delivering Success, Continuously Improv...Shahin Sheidaei
Games are powerful teaching tools, fostering hands-on engagement and fun. But they require careful consideration to succeed. Join me to explore factors in running and selecting games, ensuring they serve as effective teaching tools. Learn to maintain focus on learning objectives while playing, and how to measure the ROI of gaming in education. Discover strategies for pitching gaming to leadership. This session offers insights, tips, and examples for coaches, team leads, and enterprise leaders seeking to teach from simple to complex concepts.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Atelier - Innover avec l’IA Générative et les graphes de connaissancesNeo4j
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Allez au-delà du battage médiatique autour de l’IA et découvrez des techniques pratiques pour utiliser l’IA de manière responsable à travers les données de votre organisation. Explorez comment utiliser les graphes de connaissances pour augmenter la précision, la transparence et la capacité d’explication dans les systèmes d’IA générative. Vous partirez avec une expérience pratique combinant les relations entre les données et les LLM pour apporter du contexte spécifique à votre domaine et améliorer votre raisonnement.
Amenez votre ordinateur portable et nous vous guiderons sur la mise en place de votre propre pile d’IA générative, en vous fournissant des exemples pratiques et codés pour démarrer en quelques minutes.
2. My Perspective
• Based on personal experience – yours may differ
• There are no right answers
• Most significant impact of Agile is retrospection
• Agile is mostly a cultural revolution
• Culture is complex
• Slow to change
• Difficult to measure
Team I learnt
this with
3.
4. Background of Scrum
•Around since the mid-90s
•Gateway drug to Agile
•Easy to understand
•Easy to implement
•It works!
•Has almost become synonymous with Agile
•…but it’s not perfect
5. Problems we found with Scrum
•Sprint Planning Hell
•SqueezedTesting
•Stories not completing in Sprint
9. SqueezedTesting
• Testing cannot happen until the code is written
• Any earlier overrun squeezes testers out the back of the sprint
• Testers get the blame when stories aren’t ready
10. Story Overrun
• Symptom of previous issues
• Analysis and Design squeezed out of the front
• Testing squeezed out of the back
• Sprint just became development
• Carried-over Stories make SprintVelocity harder to measure
11. Root Causes
• Scrum does not differentiate between individuals’ skillsets
• Scrum doesn’t acknowledge dependencies between tasks
15. AWord aboutWIP
•Work in Progress (WIP) should be limited
•“Stop starting, start finishing”
•Incomplete work is “wasted inventory”
•Multi-tasking is bad!
16. Multi-Tasking Exercise
• 1
• 2
• 3
• 4
• 5
• 6
• 7
• 8
• 9
• 10
• A
• B
• C
• D
• E
• F
• G
• H
• I
• J
• I
• II
• III
• IV
• V
• VI
• VII
• VIII
• IX
• X
17. Definition of Done
•Scrum often has a Definition of Done for a whole story
•With Kanban, we had a DoD for each step in the process
Elaborate
• High level design
• AcceptanceTest
Criteria
Dev
• Feature complete
• Unit tests met
• Peer reviewed
Test
• AcceptanceTest
Criteria met
• NFT reqts met
Review
• Business Reqts
met
19. The Estimation Holy Wars
•Estimating is a divisive topic!
•We sized stories on the backlog in simplyT-shirt sizes
•Following the Elaboration phase, we knew more, and re-
estimated, using points
22. What we found
•Coped better with variable story size
•Coped better with urgent work - bug fixes, production issues
•Elimination of Sprints allowed everyone to work continuously
23. Fit with Continuous Delivery
•Scrum is a batch process
•Kanban is a continuous process
I currently work at Microsoft as a technical consultant, advising Microsoft customers on development matters. But that’s not what this session is about.
My background: developer, then architect, then team lead. First read about agile in late 90s, instant recognition. Started practising Agile early 2000s, led Agile teams from 2006/7 on. Certified Scrum Master
I do not have a magic wand. I am simply relating my experiences with a mature dev team
In my opinion, they single most important thing about the Agile Revolution is retrospection. The application of the scientific method to how we work – have a theory, create an experiment to test it, look at the results
ASK the Audience – why are people there?
Hands up if:
You’ve worked in, or closely with, a Scrum team
You’ve had some issues with Scrum
If you’ve used Kanban with a real team
Jeff Sutherland and Ken Schwabe codified scrum in 1995 [They inherited the name ‘Scrum’ from the ground-breaking 1986 paper ‘The New New Product Development Game’ by Takeuchi and Nonaka]
Terminology has entered mainstream - Backlog and Sprint are in common parlance
Skip this if everyone familiar with Scrum
The team was a mature Scrum team – we’d been running Scrum for several years, and with two week Sprints, that was a lot of Sprints.
But our retrospectives kept raising the same issues
Ref Joseph Petrine’s session on Pyschological Aspects of Estimating. Anything more than 90 minutes is wasted!
Simple story (As a User I want to…) turned meeting into Requirements Analysis
Tried asking analysts for more detailed requirements to bring to Sprint Planning
This turned Sprint Planning into Design Meeting
“Solution Design” brought to Sprint Planning
– this required tech staff to do work outside the Sprint
Not entirely relevant to my point, but it made me laugh.
Relevant to the Dilbert cartoon – testers often end up being the bearers of bad news. And culturally, that is a hard job to do – no one likes to be the person who says “No”.
Most development teams are development-centric, for obvious reasons. If the team has this focus on writing the code, everything else becomes a necessary evil. Scrum doesn’t really address this, imo
Culturally, it’s important to get the whole team to focus on the end goal – well designed, well written and thoroughly tested shippable code, that has value
Options for measuring velocity with carried over stories
Actually, the original paper “The New New Product Development Game” by Takeuchi and Nonaka assumes a multi-disciplinary team handing over to each other’s areas of expertise. But I don’t think that Scrum, as most people implement it for software development, really takes individual skills into account
The combination of these two problems led us to look at Kanban.
The typical scrum board just divides activity into three – to do, doing, and done. This level of granularity is not detailed enough
To understand the state of a story, you need to examine the tasks, and understand the connections and dependencies between them
We also added Review as the final stage, so that the implementation could be checked against the original business requirements with the owner of them/the idea
Should be familiar to anyone who has read anything about Kanban. But for those that haven’t, here’s some key points:
Each step that requires some activity has a column
Each column is divided in two – Active and Done
Flow is left to right
Give car maker analogy – making doors faster than they can be fitted results in a pile of doors, which is wasted inventory
Scrum limits work in progress by selecting all the stories for the Sprint at Sprint planning. But that is based on estimates and incomplete knowledge; sometimes stories are bigger than expected, sometimes small. Kanban allows work to be pulled as people have capacity to do it.
Do multi-tasking exercise here? Write down 3 columns – 1 to 10, A to J, I to X (roman); then turn the paper over and do them horizontally
We had an fortnightly initiation meeting for new stories, and sized them in t-shirt size. That was good enough to figure if they were cost effective
The Product owner was measured on two aspects of our site – engagement (how often people visited) and commercial (if we made any money from features). So all new work was assessed against these two criteria
From this, the high value stories were prioritised. At this stage we didn’t worry too much about size – we wanted to do what was valuable / important. But we did include some small stories that could be picked up and done without taking too long, to give us a mix of effort required.
Scrum is really not that good with dealing with bug fixes on production systems. With Kanban, we created a separate horizontal swim lane for bugs and other high priority production work.
Within a Sprint, the elaboration is front loaded, and testing back loaded. Without the Sprint, everyone can work on tasks using their skills continously
With Scrum, you typically only release at the end of the Sprint. This is at odds with the way the industry is moving, which is towards a model based on continuous delivery
With Kanban, you can release each story as it is completed (assuming no cross dependencies)
Our release process wasn’t mature enough to support Continuous Delivery, so we released once a month. A few days before the release, we looked at the stories that were ready to go, and decided on what was to be included, and what wasn’t. So the continuous Kanban development process fitted with a batch release process.