I got a copy of this from the internet, and it was not written by me. yet I found this PPT quite helpful for you to understand the Scrum, so just enjoy it.
Recycling Old Tools to New Uses…
Some say everything old is new again. This is true with requirements management regardless of the type of project methodology you adopt. You have to identify them, gather them, prioritize them, and essentially manage them. The new agile methods like SCRUM require that for your projects you define, collect and manage your requirements just as you did before, but in new ways and new formats.
So why not use proven tools and methods to do so? I will examine the benefits and shortcomings of managing requirements for an agile project method (specifically SCRUM) utilizing the Rational Requisite Pro tool. We will look at the opportunity to manage burn down lists and user stories as two of the important SCRUM process elements, and see how this “Old” tool can support “New” tricks.
I got a copy of this from the internet, and it was not written by me. yet I found this PPT quite helpful for you to understand the Scrum, so just enjoy it.
Recycling Old Tools to New Uses…
Some say everything old is new again. This is true with requirements management regardless of the type of project methodology you adopt. You have to identify them, gather them, prioritize them, and essentially manage them. The new agile methods like SCRUM require that for your projects you define, collect and manage your requirements just as you did before, but in new ways and new formats.
So why not use proven tools and methods to do so? I will examine the benefits and shortcomings of managing requirements for an agile project method (specifically SCRUM) utilizing the Rational Requisite Pro tool. We will look at the opportunity to manage burn down lists and user stories as two of the important SCRUM process elements, and see how this “Old” tool can support “New” tricks.
Mohinder Kohsla Design thinking A complimentary approach to agileAgileCymru
With so many projects not meeting their projected goals, either through over delivery of functionality to not fit for purpose or not meeting market needs due to our inability to accurately capture customer requirements. Developers are looking at new ways of product development such as design thinking that is user-centred in its ability to capture not only the functional, but also the emotional unmet needs of the customer
Scaling Agile with LeSS (Large Scale Scrum)TEST Huddle
In this webinar, Elad will cover the principles that the #LeSS framework has to offer in order to enable bug organisations to become agile.
View webinar recording - https://huddle.eurostarsoftwaretesting.com/resource/agile-testing/scaling-agile-less-large-scale-scrum/
Expanding an Agile Culture in organisations with Design thinkingAngel Diaz-Maroto
This workshop is about how to use a design thinking process an techniques to better understand organisation's culture and minimize resistance to change in the creation of an Agile culture. The strategy is to combine empathy for the context, creativity in the generation of insights and solutions, and rationality to analyze and fit solutions to the context. This solutions are aimed to create reasons for people in the organisation to embrace Agile.
You'll also learn some useful design thinking techniques that you can use in your retrospectives!!
Description:
Design Thinking refers to the methods and processes to investigate complex problems in highly uncertain systems, acquiring information, analysing knowledge, and positing solutions. This workshop is about the usage of this process to better understand organisation's culture and minimise resistance to change in the creation of an Agile culture. The strategy is to combine empathy for the context, creativity in the generation of insights and solutions, and rationality to analyse and fit solutions to the context. This solutions are aimed to create reasons for people in the organisation to embrace Agile.
This iterative process of observation, ideation and implementation can be integrated within your retrospectives and also applied outside IT to create a continuous improvement engine for organisational culture in organisations.
More with LeSS - An Introduction to Large Scale Scrum by Tim AbbottAgile ME
While there are multiple Scrum Scaling Frameworks, Large Scale Scrum is the leading framework for Scrum Scaling that truly drives success. More than just a prescription, we'll discuss the thinking and organizational tools as well as some of the practices that make LeSS truly unique.
Mohinder Kohsla Design thinking A complimentary approach to agileAgileCymru
With so many projects not meeting their projected goals, either through over delivery of functionality to not fit for purpose or not meeting market needs due to our inability to accurately capture customer requirements. Developers are looking at new ways of product development such as design thinking that is user-centred in its ability to capture not only the functional, but also the emotional unmet needs of the customer
Scaling Agile with LeSS (Large Scale Scrum)TEST Huddle
In this webinar, Elad will cover the principles that the #LeSS framework has to offer in order to enable bug organisations to become agile.
View webinar recording - https://huddle.eurostarsoftwaretesting.com/resource/agile-testing/scaling-agile-less-large-scale-scrum/
Expanding an Agile Culture in organisations with Design thinkingAngel Diaz-Maroto
This workshop is about how to use a design thinking process an techniques to better understand organisation's culture and minimize resistance to change in the creation of an Agile culture. The strategy is to combine empathy for the context, creativity in the generation of insights and solutions, and rationality to analyze and fit solutions to the context. This solutions are aimed to create reasons for people in the organisation to embrace Agile.
You'll also learn some useful design thinking techniques that you can use in your retrospectives!!
Description:
Design Thinking refers to the methods and processes to investigate complex problems in highly uncertain systems, acquiring information, analysing knowledge, and positing solutions. This workshop is about the usage of this process to better understand organisation's culture and minimise resistance to change in the creation of an Agile culture. The strategy is to combine empathy for the context, creativity in the generation of insights and solutions, and rationality to analyse and fit solutions to the context. This solutions are aimed to create reasons for people in the organisation to embrace Agile.
This iterative process of observation, ideation and implementation can be integrated within your retrospectives and also applied outside IT to create a continuous improvement engine for organisational culture in organisations.
More with LeSS - An Introduction to Large Scale Scrum by Tim AbbottAgile ME
While there are multiple Scrum Scaling Frameworks, Large Scale Scrum is the leading framework for Scrum Scaling that truly drives success. More than just a prescription, we'll discuss the thinking and organizational tools as well as some of the practices that make LeSS truly unique.
Agile , SCRUM
Introduction
What is Agile Methodology?
What is Scrum?
History of Scrum
Functionality of Scrum
Components of Scrum
Scrum Roles
The Process
Scrum Artifacts
Scaling Scrum
Q & A Session
Scrum is an efficient framework within which you can develop software with teamwork. It is based on agile principles.
This presentation will help you understand agile development in general and Scrum in specific. You will get familiar with its associated terminology along with appropriate examples.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Welcome to the first live UiPath Community Day Dubai! Join us for this unique occasion to meet our local and global UiPath Community and leaders. You will get a full view of the MEA region's automation landscape and the AI Powered automation technology capabilities of UiPath. Also, hosted by our local partners Marc Ellis, you will enjoy a half-day packed with industry insights and automation peers networking.
📕 Curious on our agenda? Wait no more!
10:00 Welcome note - UiPath Community in Dubai
Lovely Sinha, UiPath Community Chapter Leader, UiPath MVPx3, Hyper-automation Consultant, First Abu Dhabi Bank
10:20 A UiPath cross-region MEA overview
Ashraf El Zarka, VP and Managing Director MEA, UiPath
10:35: Customer Success Journey
Deepthi Deepak, Head of Intelligent Automation CoE, First Abu Dhabi Bank
11:15 The UiPath approach to GenAI with our three principles: improve accuracy, supercharge productivity, and automate more
Boris Krumrey, Global VP, Automation Innovation, UiPath
12:15 To discover how Marc Ellis leverages tech-driven solutions in recruitment and managed services.
Brendan Lingam, Director of Sales and Business Development, Marc Ellis
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
UiPath Test Automation using UiPath Test Suite series, part 4
Implementing scrum on a large scale
1. Implementing Scrum on a Large Scale Dan LeFebvre Agile Coach, CSP 3/16-18/2009 1 Orlando Scrum Gathering
2. Biography Over 20 years in software product development as a developer, manager, director, and coach Last 5 years using agile development practices Last 2 years implementing Scrum in a 700 person engineering organization as an Agile Coach Sites in MA, OR, TX, GA, IL Also in Canada – BC, Que Also in Belgium and Noida, India 3/16-18/2009 Orlando Scrum Gathering 2
3. Intent of this Session To take you through the journey of that 700 person engineering organization toward agility through Scrum. How did they decide to go agile? How did they decide to go Scrum? How do they coordinate a large suite release? How do they handle organizationally impediments? What about progress reporting? What were their biggest challenges? What are their challenges yet to face? 3/16-18/2009 3 Orlando Scrum Gathering
6. Cutter Consortium Evaluation Michael Mah and Jim Highsmith Evaluation – both quantitative and qualitative Recommended and sold Agile to CTO 3/16-18/2009 Orlando Scrum Gathering 6
7. “Agile Lite” Goal 11-1 Iterative/incremental development Test Driven Development Emergent/Evolutionary Design Daily Standups Retrospectives Phase gated governance model Commit to contents, dates, cost for a 12 month release Account for entire organizational effort 3/16-18/2009 Orlando Scrum Gathering 7
8. Weakest Link Theory Interdependent suite of products All must ship simultaneously If any of them not agile, suite is in trouble Roll out to entire organization at once 5 full time coaches from Cutter, 5 part time internal coaches After 1 year, only used 5 part time coaches 3/16-18/2009 Orlando Scrum Gathering 8
9. Results Delivered 7-5 Improved Quality More automated tests Agile in the culture 3/16-18/2009 Orlando Scrum Gathering 9
10. Entropy “Inevitable and steady deterioration of a system or society.” The American Heritage® Dictionary of the English Language, Fourth Edition 3/16-18/2009 Orlando Scrum Gathering 10
11. Slip back to old ways All part-time coaches back to their day jobs Committed to 3 suite-wide projects within the same release (each considered all or nothing) Globalization, New UI and new Reporting platform Results Projects fell behind All UI-based automation broke 2 projects stopped doing retrospectives Team morale suffered No or meaningless burncharts so no transparency 3/16-18/2009 Orlando Scrum Gathering 11
12. The Agile Coach Without the coaches, teams had no help Decided to get a full-time Agile Coach Teach agile to new employees Observe and help teams that are struggling Roll out agile to newly acquired companies Become the agile conscience of the organization 3/16-18/2009 Orlando Scrum Gathering 12
13. What to do with management 3/16-18/2009 Orlando Scrum Gathering 13
14. Management still too “Command and Control” Culture is very hierarchical People treated as “resources” Regularly moved from team (workgroup?) to team to handle crises and delays Management makes most decisions Teams do not feel empowered Many teams just going through the motions of agile development “Blame” is typical reaction 3/16-18/2009 Orlando Scrum Gathering 14
15. Collaboration Explained 90 people trained in collaboration skills by Jean Tabaka and Ronica Roth from Rally Learned tools Facilitation techniques Lots of hands-on exercises Results Meetings ran better Better agendas and capturing of group learning Better retrospectives 3/16-18/2009 Orlando Scrum Gathering 15
16. Management not Agile Management not quite agile Very little training was given to managers Still division between Dev and QA 3/16-18/2009 Orlando Scrum Gathering 16 Manager Community Customer Community Developer Community
17. Scrum to the rescue Scrum is a management framework Training focused on the managers and product managers 60 ScrumMaster receive CSM from Ken Schwaber 30 Product Owners receive CSPO from Ken Schwaber Create true cross-functional teams No more “communities” 1 ScrumMaster, 1Product Owner, Team of developers, testers, writer, etc. Managers became ScrumMasters, Product Managers are now the Product Owners 3/16-18/2009 Orlando Scrum Gathering 17
21. How do they synchronize and review the suite? Created the concept of “Release Candidates” Every 6 to 8 weeks Entire system integrated and tested together Suite build and battery of suite tests run weekly Teams hold their own sprints but integrate into last integrated system each week Each team has daily builds and battery of daily tests (some team build more often) 3/16-18/2009 Orlando Scrum Gathering 21
22.
23. Each team presents release plan focusing on dependencies and impacts to SRT
27. Dealing with suboptimization Each team is run fairly independently Each identify and resolve impediments Experiencing the same impediments Different solutions Some solutions impacted other teams 3/16-18/2009 Orlando Scrum Gathering 24
28. First Attempt – Etc. Senior Execs doing the work of prioritizing and resolving organizational impediments Identified by the development teams Resolve by creating small teams to remove the impediment Use Scrum to run the process Issues Execs had no time for this work Reluctant to assign people to impediment removal teams 3/16-18/2009 Orlando Scrum Gathering 25
29. Second Attempt – Scrum Implementation Team Small group of 8 people from across the organization Issues Focused more on process definition instead of impediment removal Not all the skills represented Limited time to work on this, still had day jobs 3/16-18/2009 Orlando Scrum Gathering 26
30. Third Attempt – ScrumMaster Meeting Hold a regular meeting of ScrumMasters to identify, prioritize, and volunteer to resolve impediments This group got some traction Issues Many impediments around Product Ownership Also many architectural impediments 3/16-18/2009 Orlando Scrum Gathering 27
31. Final Attempt – Agile Leaders Meeting Regular meeting of ScrumMasters, Product Owners, and Architects led by Agile Coach Agenda includes a brief coaching session on an agile topic from one of the team Review of resolved impediments, identifying and prioritizing new ones, and volunteering to resolve highest priority Q & A session to solicit help from team and coach on individual issues Resolved over 50 impediments in 1 year 3/16-18/2009 Orlando Scrum Gathering 28
33. Transparency is more translucent Each team uses their own tools for tracking data Flipcharts and post-its Excel – Various workbooks X-Planner Rollup data collected manually Sometimes late Sometimes not complete Apples to Oranges rollup “Blame” culture prevents full disclosure too soon 3/16-18/2009 Orlando Scrum Gathering 30
34. Clearing it up SMT created a standard workbook that normalizes data to facilitate a suite-wide rollup Includes a projected organizational velocity to predict end date “I have never been in an organization that knew more about where it was throughout the lifecycle of the project” – One Senior Staff Member 3/16-18/2009 Orlando Scrum Gathering 31
35. Clearing it up more Implementing VersionOne Centralize the project information Give execs instant access to status of any project Standardize how information is collected and managed throughout the organization Simplify suite rollup Provide unprecedented transparency Create standard reports 3/16-18/2009 Orlando Scrum Gathering 32
37. Suite planning still phase-gated Need still exists to commit to an annual plan Company expects large features to justify the 700 person engineering staff Outside engineering still driven by “waterfall” model Cannot or will not take advantage of iterative delivery 3/16-18/2009 Orlando Scrum Gathering 34
38. Creating a Balance They created a multi-tiered content strategy Commit at the high level Establish budgets at the mid-level Stay flexible at the details Budgets give guidance to Product Owners on what senior management is willing to invest to get the benefit or return 3/16-18/2009 Orlando Scrum Gathering 35
39. Requirements hierarchy Initiatives – Broad areas of focus tied to corporate strategy Headlines – Major Feature Sets/Capabilities within an Initiative Engineering commits to these within a budget Shippable Units – The smallest feature that is worth shipping to a customer Analogous to Minimal Marketable Feature from Software by Numbers Engineering delivers as many of these within the budget of a headline Business Value measured here Stories – User stories as we all know and love 3/16-18/2009 Orlando Scrum Gathering 36
41. Product Plan Portfolio Plan RC 1 RC 2 RC 3 RC 4 Rel 6.2 SU SU SU SU SU SU SU SU SU SU SU SU Headline Headline SU SU SU SU Headline SU Headline SU SU Headline Headline SU Headline Headline Release Plan Rel 6.1.1 Sprint 1 Sprint 2 Sprint 3 Headline Headline Headline As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf As a User, I can jfh hf jahdsdf Headline Rel 6.1.2 Headline Headline Headline Planning and Outputs SprintPlan Started Done Task Task Task Task Task Task
42. Is Done really Done? 3/16-18/2009 Orlando Scrum Gathering 39
43. Unpredictable “tail” Planned 3 months for final stabilization Always goes longer Many unpredictable issues found The Definition of Done (DoD) was not the same across teams Some due to the large amount of legacy code Some based on management interpretation – “Spirit of the Criteria” 3/16-18/2009 Orlando Scrum Gathering 40
44. Executive Bias Setting DoD too “weak” - guideline Leads to too much work during the tail Makes it hard to know where you are Causes integration issues due to impedance mismatch Setting DoD too “Strong” - rule No real progress can be made due to late issues Sets the bar too low on content Executives wants team to “stretch” by setting aggressive DoD but knows he’ll get less (and accepts it) This line is not apparent to the teams 3/16-18/2009 Orlando Scrum Gathering 41
45. Created 2 lists of criteria Definition of Done This is the must be complete to declare victory Quality Goal Strive to complete and must justify shortfall Example DoD – Performance test must be completely run Quality Goal – Performance must not have degraded by more than 5% with no S1 defects 3/16-18/2009 Orlando Scrum Gathering 42
46. DoD is too much for each Sprint Doing all the work needed for shipping each sprint is considered wasteful Some tests run almost as long as a sprint! Lots of legacy code with manual tests 3/16-18/2009 Orlando Scrum Gathering 43
47. Modify DoD and QG by timebox Defined unambiguously by SMT For Ship – include everything that must be done For RC – remove what they are unable or unwilling to do each RC For Sprint – remove what they are unable or unwilling to do each Sprint 3/16-18/2009 Orlando Scrum Gathering 44
52. Enticing rest of Organization to be more Agile There is still a “batch” approach to preparing Service and Customer training Marketing not strongly tied in with Product Management and the Product Owners 3/16-18/2009 Orlando Scrum Gathering 49
53. Performance and Compensation still very individualized Has a negative effect on teamwork Some teams view ScrumMaster/Manager as an evaluator and aren’t as open with issues Individual goals trump team goals or organizational goals 3/16-18/2009 Orlando Scrum Gathering 50
54. Still treat people as “resources” Cannot break habit of moving people from team to team Cannot break habit of needing “full utilization” Cannot break habit of accounting for hours worked 3/16-18/2009 Orlando Scrum Gathering 51
55. Recent Restructuring Increased fear Potential to reduce transparency Potential to reduce teamwork to “CYA” Lowered morale Lower energy Potential less commitment 3/16-18/2009 Orlando Scrum Gathering 52
56. Loss of the Coach They eliminated the position of Agile Coach Entropy may set in again No focus for getting help to the teams Impediments mechanism may break down Training of new employees and organizations will be affected 3/16-18/2009 Orlando Scrum Gathering 53
58. Where are they? Scrum is implemented throughout Mechanism for organizational impediments in place Transparency is improving Improvements to engineering practices are on-going Quality is improving Planning is becoming more flexible 3/16-18/2009 Orlando Scrum Gathering 55