You will learn how to set the stage and provide clear boundaries within each ceremony. Heck, this practical knowledge will help you in any meeting, not just Scrum. With this knowledge you will get the team to collaborate with each other and with you.
Target audience: Fresh and experience scrum masters wishing to acquire additional tools and skills and agile coaches leading organizational change.
A good anti-pattern has 2 elements:
1. A repeated pattern of action that appears beneficial, but ultimately produces more bad consequences than beneficial results.
2. A refactored solution exists that has been proven in actual practice and is repeatable.
So, what are common pitfalls that new (or even experienced) agile practitioners fall into? Learning about and watching out for these anti-patterns is a great way to inspect and adapt your agile practice.
You will learn how to set the stage and provide clear boundaries within each ceremony. Heck, this practical knowledge will help you in any meeting, not just Scrum. With this knowledge you will get the team to collaborate with each other and with you.
Target audience: Fresh and experience scrum masters wishing to acquire additional tools and skills and agile coaches leading organizational change.
A good anti-pattern has 2 elements:
1. A repeated pattern of action that appears beneficial, but ultimately produces more bad consequences than beneficial results.
2. A refactored solution exists that has been proven in actual practice and is repeatable.
So, what are common pitfalls that new (or even experienced) agile practitioners fall into? Learning about and watching out for these anti-patterns is a great way to inspect and adapt your agile practice.
Scrummaster Needed Desperately at 2016 Scrum AustraliaBernd Schiffer
There is a lot of reluctance within organisations to place ScrumMasters, let alone to spend money to hire them. Surely this role can be done by one of the developers, right? After all, it’s only a minor role, isn’t it? Far from it! The ScrumMaster is a full-time role. Without it, who can take care of the agile process on behalf of a busy Scrum team?
One way to help teams and management understand the value of the ScrumMaster’s role is to show them the volume and importance of tasks a ScrumMaster can fulfil, and the consequences of what happens if nobody takes care of these tasks. This session not only presents the 42 tasks of a ScrumMaster’s role but will clearly show that every Scrum team needs a ScrumMaster.
Three steps to transform from a waterfall to an Agile orgElad Sofer
A long long time ago, in a galaxy far far away... before the LeSS framework existed as a clearly defined framework, a few chosen Agile coaches were trying to restore agility to the galaxy by introducing the organization to the concepts that were later named as the LeSS framework.
This is a story about one Agile coach trying to help a product group in a security company to improve their business success by optimizing the whole rather than parts, by eliminating silos and getting rid of the fore waterfall forces of the dark side
Олександр Стороха "Why you can`t lead alone huge team effectively or importan...Lviv Startup Club
Lviv Project Management Day 2017
Олександр Стороха "Why you can`t lead alone huge team effectively or importance of delegation and developing agile leaders"
Scrummaster Needed Desperately at LAST Conf 2016 in Melbourne, AustraliaBernd Schiffer
There is a lot of reluctance within organisations to place ScrumMasters, let alone to spend money to hire them. Surely this role can be done by one of the developers, right? After all, it’s only a minor role, isn’t it? Far from it! The ScrumMaster is a full-time role. Without it, who can take care of the agile process on behalf of a busy Scrum team?
One way to help teams and management understand the value of the ScrumMaster’s role is to show them the volume and importance of tasks a ScrumMaster can fulfil, and the consequences of what happens if nobody takes care of these tasks. This session not only presents the 42 tasks of a ScrumMaster’s role but will clearly show that every Scrum team needs a ScrumMaster.
Advanced Scrum: Answering the Difficult QuestionsRyan Ripley
Advanced Scrum was presented at the Path to Agility Conference 2017 and was centered around the audiences questions and concerns about their Scrum practices and implementations.
Presented during a webinar with Discuss Agile, August 9, 2018.
I’ve met many ScrumMasters. Some of them have been full time dedicated ScrumMasters, but far from all.
In this webinar we will discuss the benefits of having a full time and dedicated ScrumMaster, and the challenges getting there.
When you register, we encourage you to list your ideas of why it is good to have a full time dedicated scrum master and the challenges you have faced.
We will also reveal and discuss an often forgotten responsibility of a ScrumMaster. Which, if addressed, may help the development team and the rest of the organization dramatically.
Practical Scrum Workshop by SEO Rescue. A Practical hands on approach to training. please contact Shaf Cangil on linkedin or www.seorescuenow.co.uk to book a training session.
Somewhat internal presentation on how we use Scrum for Agile Development at Firmhouse. We have very small software teams so we made some changes to the "strict" Scrum rules to best incorporate our team.
Scrummaster Needed Desperately at 2016 Scrum AustraliaBernd Schiffer
There is a lot of reluctance within organisations to place ScrumMasters, let alone to spend money to hire them. Surely this role can be done by one of the developers, right? After all, it’s only a minor role, isn’t it? Far from it! The ScrumMaster is a full-time role. Without it, who can take care of the agile process on behalf of a busy Scrum team?
One way to help teams and management understand the value of the ScrumMaster’s role is to show them the volume and importance of tasks a ScrumMaster can fulfil, and the consequences of what happens if nobody takes care of these tasks. This session not only presents the 42 tasks of a ScrumMaster’s role but will clearly show that every Scrum team needs a ScrumMaster.
Three steps to transform from a waterfall to an Agile orgElad Sofer
A long long time ago, in a galaxy far far away... before the LeSS framework existed as a clearly defined framework, a few chosen Agile coaches were trying to restore agility to the galaxy by introducing the organization to the concepts that were later named as the LeSS framework.
This is a story about one Agile coach trying to help a product group in a security company to improve their business success by optimizing the whole rather than parts, by eliminating silos and getting rid of the fore waterfall forces of the dark side
Олександр Стороха "Why you can`t lead alone huge team effectively or importan...Lviv Startup Club
Lviv Project Management Day 2017
Олександр Стороха "Why you can`t lead alone huge team effectively or importance of delegation and developing agile leaders"
Scrummaster Needed Desperately at LAST Conf 2016 in Melbourne, AustraliaBernd Schiffer
There is a lot of reluctance within organisations to place ScrumMasters, let alone to spend money to hire them. Surely this role can be done by one of the developers, right? After all, it’s only a minor role, isn’t it? Far from it! The ScrumMaster is a full-time role. Without it, who can take care of the agile process on behalf of a busy Scrum team?
One way to help teams and management understand the value of the ScrumMaster’s role is to show them the volume and importance of tasks a ScrumMaster can fulfil, and the consequences of what happens if nobody takes care of these tasks. This session not only presents the 42 tasks of a ScrumMaster’s role but will clearly show that every Scrum team needs a ScrumMaster.
Advanced Scrum: Answering the Difficult QuestionsRyan Ripley
Advanced Scrum was presented at the Path to Agility Conference 2017 and was centered around the audiences questions and concerns about their Scrum practices and implementations.
Presented during a webinar with Discuss Agile, August 9, 2018.
I’ve met many ScrumMasters. Some of them have been full time dedicated ScrumMasters, but far from all.
In this webinar we will discuss the benefits of having a full time and dedicated ScrumMaster, and the challenges getting there.
When you register, we encourage you to list your ideas of why it is good to have a full time dedicated scrum master and the challenges you have faced.
We will also reveal and discuss an often forgotten responsibility of a ScrumMaster. Which, if addressed, may help the development team and the rest of the organization dramatically.
Practical Scrum Workshop by SEO Rescue. A Practical hands on approach to training. please contact Shaf Cangil on linkedin or www.seorescuenow.co.uk to book a training session.
Somewhat internal presentation on how we use Scrum for Agile Development at Firmhouse. We have very small software teams so we made some changes to the "strict" Scrum rules to best incorporate our team.
Rolling out Agile in Paddy Power Product DevelopmentPaul Hayes
Slides from the presentation I gave at Sureskills 'Agile - Making it Work' breakfast briefing in Dublin on November 27th. I describe the reasons for introducing Scrum, how we went about it, and the improvements that the change has delivered.
Quick reference to start Agile/SCRUM IT Development based on personal experiences and best practices. Most effective approach is "learning by doing" so after a short introduction simply start executing and keep learning and improving your process. It will show an exciting adventure with great results.
Most important change is the paradigm shift from one-off project to process and get mind set to continuous delivery.
Implementing Scrum for large scale projects (@DCB14)Biser Simeonov
This presentation is based on a real life experience trying to implement Scrum methodology for one of our large-scale Drupal projects in the Municipality of Copenhagen. I'll be focusing on what our approach is, what challenges the team is facing along the project execution and the lessons learned.
Beside all successful stories related to how flexible, how fancy and dev friendly the idealistic Scrum approach is, I will be discussing with you also some of the most critical topics from project management perspective. This is why I’ll put extra focus on how Scrum works in an ideal world and what are the challenges implementing it for a real project:
• Why Scrum is good enough to be applied for a complex Drupal project;
• Defining and understanding well enough the different roles in Scrum;
• “Self-organized team” or how the production team's mindset should be changed;
• Is there an option to deliver a Scrum project with already predefined scope and fixed budget;
• User stories definition , acceptance criteria, technical debt, retrospective meetings: do we really need to take care of these;
• The most common mistakes understanding Scrum and how to prevent them;
• Tips that will lead us to a successful project delivery using Scrum;
Using an Agile Inception to Kick Off a ProjectVictor Bonacci
Agile Inceptions are powerful and fast ways to get a team to internalize a vision. It’s a two-day investment that saves the company months of up-front planning and allows the teams to begin immediately deliver core product functionality.
The inception model is a kickoff strategy that is repeatable and well-vetted. At it’s core, the inception deals with how we scope. The session(s) relies on full participation by an engaged audience, and co-location is crucial as we swarm around note-cards on tables and walls.
Over the past few years the APM Governance SIG has been at the forefront of developing new thinking on governance, for example we have published guides – Directing Change, Co-Directing Change, Sponsoring Change. In recent discussions around specific high profile projects, practitioners have explained how organisations have struggled to apply traditional approaches, methods and controls to the growing number of Agile projects. It is therefore the ambition of the GovSIG to develop guidance for the agile governance of agile projects / portfolios.
SIG members came together to explore the governance lessons from Agile projects to date and to set the framework for developing guidance for the governance of Agile projects. There was a short presentation to set the scene and then a workshop session which was led by Brian Wernham and Martin Samphire. Brian Wernham is author of the book “Agile Project Management for Government”.
High Quality Software Development with Agile and ScrumLemi Orhan Ergin
Module 1. Born to fail
- Why projects are failing
- Waterfall & traditional software development
Module 2. Agile
Module 3. Scrum
Module 4. Writing high quality software with Agile
- XP
- How Google Write Software
Module 5. Do's and dont's
- How Scrum might fail
- Myths and realities
Module 6. How to kick off Scrum
The ultimate presentation about Scrum, the world's leading project management framework for agile software development.
http://www.noop.nl
http://www.jurgenappelo.com
Scrum Master Lessons from my 4 Year Old SonRyan Ripley
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
How would we define Scrum? How could we convince people to do Scrum? I believe that agreements are more powerful than rules. I also believe that Scrum implements patterns that most of us have experienced in our own most successful projects. Let's test that belief and see how we can apply that to facilitating Scrum adoption. During this interactive workshop, we:
• Share and reflect on the experiences from our own best projects
• Look for patterns in those projects
• Compare Scrum with our own best experiences
• Explore an agreement-based adoption strategy
The workshop also includes some additional food for thought: What if we considered the Scrum Flow as a series of opportunities to ask ourselves powerful questions?
What does a Scrum Master do all day if a Daily Scrum is only 15 minutes? This talk - “A Day in the Life of a Scrum Master” - will explore the role beyond simple facilitation of the Sprint Ceremonies. Attendees learn four different areas of focus for a balanced approach to the role.
You Cant Be Agile If Your Code Sucks (with 9 Tips For Dev Teams)Peter Gfader
Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers.
Great software engineering teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live.
I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions.
* Why would a company like to be "agile"?
* How can a company achieve that?
* How can you achieve Technical Excellence in your software teams?
* What developer skills are more important than languages, methods or frameworks?
----
What is the difference between Agile and Business Agility? I will use this as an intro exercise.
---
What is "Business Agility"? Why is Agility important? What is Software Craftsmanship?
What can we do to improve our Technical Excellence?
https://beyond-agility.com
Agile Tour Zurich Three Secrets of Agile LeadersPeter Stevens
How do leaders achieve long-term goals? How do they inspire people to achieve goals larger than themselves? Three stories of successful leaders, three secrets, and three tips for becoming a better leader. (Hint: The answer is hiding in plain sight.)
Agile in Action - Agile Overview for DevelopersMatt Cowell
Excerpt from a presentation I gave to the University of Alabama Association for Computing Machinery in November 2010. I wanted to give the students a practical overview of Agile and Scrum and give them some perspective on what Agile means for developers.
L'approche de tests par propriétés est une alternative aux techniques de tests basés sur des exemples.
Cette approche est conçue pour tester les aspects d'une propriété qui doit toujours être vraie. Ceci permet de couvrir un grand éventail de valeurs d'entrées programmatiquement et de tester celles-ci en un seul test. Contrairement aux tests basés sur des exemples où l'on doit faire un test pour chaque exemple.
Nous couvrirons les outils requis pour débuter à utiliser les tests par propriété.
Nous construirons ensemble une suite de tests afin de démontrer la puissance de cette approche dans un cas réel.
- Accès aux données (CRUD) avec Entity Framework et quelques optimisations d eperformance grâce à des extensions pour EF Core. Des alternatives à EF Core telles que ORMLite nous aborderons également.
- Gestion de services multitenant avec L'injection de dépendance dynamique
- Api versioning
- Streaming
- la compression
- L'intégration avec Application Insights & live metrics
- Protéger les données secretes avec AzureKeyvault
- Healthcheck
- Policy retry et circuit breaker sur les HttpClient et call sql avec Polly
- Mise à jour de la partie 1 concernant TestServer: utilisation de la webapplicationfactory
Groupe Excel et Power BI - Rencontre du 25 septembre 2018MSDEVMTL
Voici la présentation d'introduction du groupe d'usagers Montreal Modern Excel and Power BI du 25 septembre 2018. Elle vous montre notamment comment aller récupérer les documents de nos meetings.
Authenticating, validating, caching, error handling, logging, documenting, testing and profiling are common features in web API, here are code samples to show how to implement them!
Stephane Lapointe: Governance in Azure, keep control of your environmentsMSDEVMTL
June 11th 2018
Azure Group
Subject: Governance in Azure, keep control of your environments.
Speaker: Stephane Lapointe, Azure MVP
It's very easy to lose control over what's happening in your Azure environments. In this talk, see solutions for managing security, costs, and governance. We'll talk about tools like tags, RBAC, policies, Azure Security Center & Azure Advisors to implement initiatives that will greatly help your management in Azure.
Eric Routhier: Garder le contrôle sur vos coûts AzureMSDEVMTL
11 juin 2018
Groupe Azure
Sujet: Garder le contrôle sur vos coûts Azure
Confériencier: Eric Routhier
Azure permet aux entreprises d'être plus agiles et plus innovantes en décentralisant la gestion de l'infrastructure. En contrepartie, les coûts augmentent souvent rapidement et les administrateurs se demandent parfois s'ils l’exploitent vraiment à son plein potentiel. Apprenez comment gagner une meilleure visibilité sur votre consommation Azure et surtout apprenez quelques trucs pour réduire votre facture considérablement!
Open id connect, azure ad, angular 5, web api coreMSDEVMTL
Dans cette se session nous allons démystifier la configuration et l'utilisation d'Open Id Connect avec Azure AD.
L'application cliente sera un SPA Angular 5, implémentant la librairie ADAL.JS, enfin nous allons voir comment proétéger une WebAPI avec un JSON Web Token (JWT)
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.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
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.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...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.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
3. Benjamin Day
• Brookline, MA
• Consultant, Coach, & Trainer
• Microsoft MVP for Visual Studio ALM
• Team Foundation Server, Software Testing,
Scrum, Software Architecture
• Scrum.org Classes
• Professional Scrum Foundations (PSF)
• Professional Scrum Master (PSM)
• Professional Scrum Developer (PSD)
• www.benday.com, benday@benday.com, @benday
8. Assumptions
• You’re technical. I’m technical.
• For today, we’re talking about a fairly technical Scrum Master
• (Don’t forget the needs of the business though.)
• This talk =
Scrum Mastering + “Getting your project started right”
12. ~148 ft / ~45 m
~15ft/~4.8m
Team 1 Team 2
Target Target
The Curling Sheet
13. Curling Stones
~40 lb. stones
Polished granite
It’s got a handle
8 stones per team
14. ~148 ft / ~45 m
~15ft/~4.8m
Note: that stone’s not to scale
Get your stones as
close as possible to
the center of the
target
Each team
takes turns
Team with the most
stones closest to the
center of the target
wins
15. Throwing
3 team members per throw
Thrower
- Stone in hand
- Pushes off with legs
Starts glide towards target
Thrower has to release stone
46. What does the Scrum Master do?
• Keeper of the process
• Help the team deliver
• Argue for and defend the team
• Help the Product Owner
47. Top 10 Ways: Things to Think About
• What can you do to help your team?
• What can you do to help your product owner?
• What can you do to help yourself?
• What can you do to help your organization?
• Change your Daily Scrum
48. Here are all the things I wanted to put in this
talk.
• What can you do to help your team?
• Written DoD
• Encourage self-organization
• Try to help minimize the work in progress.
• Remind them to keep talking. One major downside of TFS is that people can sometimes think of it as an excuse to not talk.
• Remind them about how much and how creatively you can decompose a PBI
• Emergent Architecture.
• Remind them they don't report to you
• What can you do to help your product owner?
• Product owner checklist
http://productownerchecklist.org by Lare Lekman
• Remind them that they need to stay engaged and that their engagement is critical for the success of the team and the effort.
• Remind them to plan ahead a bit and share their vision
• Help with credibility by planning 2 to 3 sprints out
• What can you do to help yourself?
• You can't fix everything.
• Watch for burnout.
• Do whatever it takes to get you to believe in self-organization
• What can you do to help your organization?
• Get them cozy with the fact that change will be coming.
• Changing of plans is a "feature" not a "bug."
• Inoculate them so that they won't panic when change inevitably happens.
• Question how products align with teams. Bring work to the teams rather than bringing Teams to the work. Let the Teams stay together
and focused on a limited amount of stuff and they'll go faster.
• Help them think about sprint lengths. Sprints help scope risk. Sprints force you to pause from time to time to see where you actually are.
It helps keep you honest. Have you *actually* delivered anything? Why and why not?
• Practice explaining Story Points.
• Explain that Scrum doesn't replace the existing org structure. It is a layer on top of the existing org structure. While it probably won't
change anyone's job, it might change how they perform their job.
• Think like a data scientist.
http://blogs.hbr.org/2013/11/how-to-start-thinking-like-a-data-scientist/
• Watch out for fear. Fear is *everywhere*.
• Address the QA problems.
• What does QA do at the front side of the sprint?
• Answer collaborate with fellow team members to ensure that everyone knows how stuff is going to be
tested.
• Basically, front-load your quality focus.
• Change your daily standup
• Consider dumping "3 questions"
• Consider switching who "runs" the standup
• Watch for people being bored and/or tuning out
• Bored people implies doing too much work and/or a wobbly sprint goal
• Bored people implies multiple teams of 1 rather than a team of X. You have people who sit near each
other rather than actual functional team.
• What is your Velocity?
• If you don't have estimates, you can't have a velocity.
• If you don't have a DoD, velocity is problematic.
• If you're wobbly on DoD, your velocity is suspect.
• Be firm on DoD. No partial credit.
• Better Retrospectives
• Write them down. Review the results.
• Try to walk through the sprint day by day and ask people how they felt, what was going on on this day,
why is the burndown going up or down? This helps them to *remember* what was happening.
• Common Objections to Scrum
• Leading vs Coaching
• Coaching organizations
• Coaching teams
• Common objections
49. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming & testing
practices
8. “Kick it over the wall to QA”
9. Teams : Products
10. Retrospective
50. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
51. Definition of Done (DoD) =
Everything it takes to say something is
completely done.
52. What is your DoD?
• Closest thing to a “silver bullet” in Scrum
• Technical Debt will ruin you.
• Write it down.
• Review and discuss it regularly.
58. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
63. Want to be a super hero?
Go see a therapist.
(I’m not kidding.)
64. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
65. 2 to 3 Sprints of Product Backlog
• Helps give the PO “room”
• Helps everyone to know what’s going on.
• Be ready to answer where a PBI (aka. “feature”) is on the backlog.
• How many sprints out?
• Discuss your *written* DoD with the PO, executives, and stakeholders
• Why is it in their best interest?
66. Fit for purpose.
• Remember that not everything is, needs to be, or should be a work of
art.
• Balance “Time to Market” with “Long-term Maintenance”
• Communicate with the business in terms they understand
• (Hint: this is probably money and resources.)
68. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
80. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
83. If everyone on your team is working on
separate PBIs,
is the team really a team?
84. Finish one thing. Then do the next thing.
• Try to craft the work so that multiple people are working on related
things
• Complete that thing. Move on to the next thing.
• Try to drive stuff to DoD early.
• This ensures that you’re delivering something in the sprint.
86. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
89. Emergent Architecture.
• Build what you need.
• It’s a spectrum.
Suicidal
Non-Planning
Sanity
&
Balance
Big
Design
Up-Front
90. Emergent Architecture.
• Build what you need.
• It’s a spectrum.
Suicidal
Non-Planning
Sanity
&
Balance
Big
Design
Up-Front
91. Emergent Architecture.
• Build what you need.
• It’s a spectrum.
Suicidal
Non-Planning
Sanity
&
Balance
Big
Design
Up-Front
92. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
98. Loose coupling.
• Code to interfaces.
• Use the Dependency Injection Pattern
• (Pass dependencies in on the constructor.)
• Consider an IoC Framework
• Use the Repository Pattern
• Remember Single Responsibility Principle
99. Build for Testability
• Unit test, unit test, unit test
• Unit test != Integration Test
• Test one layer at a time in isolation
• No database connections from a unit test
• Integration tests in a separate project
• Keep yourself honest
100. For the love of all things
precious & beautiful…
101. …DON’T USE A SHARED DEVELOPMENT
DATABASE!!!!!!!!
103. Eliminate the "works on my box" problem *early*.
• Set up automated builds from the very beginning.
• If you're using TFS, use Gated Check-in builds
• Deploy your database as part of your builds.
• Run your unit tests from the builds
104. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
105. Never say
“Kick it over the wall to QA” again.
• Us vs. Them
• QA is part of the team
• QA’s work should be part of the DoD
107. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
108. How do Teams align to Products / Projects?
• Watch out for partial allocations
• Do team members have more than one Daily Scrum?
• Rather than 1 team per 1 product,
try 1 team that supports multiple products
109. Teams to Products
• Bad
• Billing System has a Billing Team
• Accounting System has an Accounting Team
• CRM system has a CRM Team
• Website has a Website team
• People are 50% allocated to multiple teams.
110. Teams to Products
• Better
• Team A
• Billing
• Accounting
• Team B
• CRM
• Website
111. Teams to Products
• Best
• Team A and Team B are cross-functional
• Either team can do tasks from Billing, Accounting, CRM, or Website
112. The Product Owner as a
work funnel.
…then the Product Owner
adjusts the Product Backlog…
CEO’s crazy
dreams
Accounting
Project
Medical
Records
Project
Development
Team
Product
Owner
• Product Owner has to decide priority for the team
• The team can’t do everything at once
• There has to be priorities
• The team isn’t qualified to balance these priorities
Entonnoir?
113. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
121. Top 10 Ways
1. What is your DoD?
2. People Skills
3. Credibility
4. What is your Sprint Goal?
5. Do less.
6. Emergent Architecture
7. Good programming &
testing practices
8. “Kick it over the wall to
QA”
9. Teams : Products
10. Retrospective
Assumptions
In this case, the Scrum Master is somewhat technical
I'm technical. Right or wrong, my Scrum Mastering style tends to go deep on the technical stuff.
You have to remember the needs of the business though. You're not building this stuff for the sake of the technology. You're building this stuff for the sake of the business. In all likelyhood, it's about making money. The technology enables the making of the money which pays for you to write the software which makes more money and pays for more software. Rinse and repeat.
This talk will straddle the line between Scrum Mastering and "Getting your project started right"
Things that have caused my teams constant headaches that kill velocity
What is your Definition of Done (DoD)?
There's no magic bullet in Scrum...but this one is pretty close.
Write. Your. DoD. Down.
Discuss your DoD a lot.
Technical debt will ruin you. The little bits of not quite entirely done will crush your "agility".
If anyone says "Done vs. Done Done", hire someone to murder that person in their sleep. Ok. Well, maybe not murder them but that's a big deal.
No partial credit. It's either done or not done.
People Skills
Trust your gut. Pause from time to time and ask yourself how you're feeling.
Therapy. We all have issues. Trust me...even though you *think* you know what they are, you don't really know. There are tons of issues and little stupid things you do that you could use to figure out. Getting in tune with your own inner life will help immensely.
Credibility is your greatest asset.
Keep your backlog ordered for at least 2 sprints worth of work. Be ready to answer at a moment's notice when a feature is forecast to be delivered.
That written DoD is your best friend when you're talking to product owners and executives and stakeholders. Make sure that they understand why DoD and Quality is in their best interest.
Be careful to not lose sight of "fit for purpose". Sometimes, you're not getting paid to create a work of art. It's a balance between "time to market" and "long term maintenance".
Do yourself a favor and say "forecast" rather than "commitment"
Try to communicate in terms that the business understands. (Answer: probably money.)
What's your Sprint Goal?
Review your SG in your daily standups.
If your sprint goal is simply a "select Title from SprintBacklog" you're probably doing it wrong.
Do less.
Aka. Minimize Work in Progress
If everyone on your team is working on separate PBIs, is the team really a team?
Try to craft your work so that you have more than one person working on something at a time. Drive that PBI to completion ASAP and only then move on to the next PBI.
Remember your DoD and work to drive your PBIs to DoD-compliance as soon as possible.
If something is DoD-done, you've already pretty much delivered something in that sprint.
The anti-pattern is being 2 days from the end of your sprint and nothing is DoD-done yet.
Do less.
Aka. Minimize Work in Progress
If everyone on your team is working on separate PBIs, is the team really a team?
Try to craft your work so that you have more than one person working on something at a time. Drive that PBI to completion ASAP and only then move on to the next PBI.
Remember your DoD and work to drive your PBIs to DoD-compliance as soon as possible.
If something is DoD-done, you've already pretty much delivered something in that sprint.
The anti-pattern is being 2 days from the end of your sprint and nothing is DoD-done yet.
Do less.
Aka. Minimize Work in Progress
If everyone on your team is working on separate PBIs, is the team really a team?
Try to craft your work so that you have more than one person working on something at a time. Drive that PBI to completion ASAP and only then move on to the next PBI.
Remember your DoD and work to drive your PBIs to DoD-compliance as soon as possible.
If something is DoD-done, you've already pretty much delivered something in that sprint.
The anti-pattern is being 2 days from the end of your sprint and nothing is DoD-done yet.
Good programming and unit testing practices let you worry less.
The goal is to make Refactoring as painless as possible. Refactoring should not strike terror into your soul(s).
Remember...requirements will change and people will change their minds.
Build for maintenance.
It's a metaphysical certainty that you're going to have to change stuff.
You won't get your "requirements" right.
Your customers / stakeholders *will* change their minds.
Keep things loosely coupled.
Program to interfaces
Use Dependency Injection
Read up on the Repository Pattern
Remember Single Responsibility Principle.
Build for testability.
Unit test, unit test, unit test.
And when I say *unit* test I mean *unit* not integration test.
Get comfortable with mocks, stubs, and fakes.
Unit tests should not connect to a service or a database
Unit tests should test only one "layer" at a time
Keep unit tests and integration tests in separate projects. Integration tests can talk to the database but they should also only talk to one layer at a time.
For the love of god, don't use a shared development database
No shared test data.
If at all possible, use the Visual Studio Database Projects.
Eliminate the "works on my box" problem *early*.
Set up automated builds from the very beginning.
If you're using TFS, use Gated Check-in builds
Deploy your database as part of your builds.
Run your unit tests from the builds
Think about maintain a minimal Inventory.
Inventory is sunk cost.
Anything you write has to be maintained.
Write less code. I'm not saying to use lots of frameworks like NHibernate or Entity Framework or RIA Services...I'm not saying don't use them either. Just keep in mind that everything you write you have to maintain.
Do less.
Aka. Minimize Work in Progress
If everyone on your team is working on separate PBIs, is the team really a team?
Try to craft your work so that you have more than one person working on something at a time. Drive that PBI to completion ASAP and only then move on to the next PBI.
Remember your DoD and work to drive your PBIs to DoD-compliance as soon as possible.
If something is DoD-done, you've already pretty much delivered something in that sprint.
The anti-pattern is being 2 days from the end of your sprint and nothing is DoD-done yet.
Do less.
Aka. Minimize Work in Progress
If everyone on your team is working on separate PBIs, is the team really a team?
Try to craft your work so that you have more than one person working on something at a time. Drive that PBI to completion ASAP and only then move on to the next PBI.
Remember your DoD and work to drive your PBIs to DoD-compliance as soon as possible.
If something is DoD-done, you've already pretty much delivered something in that sprint.
The anti-pattern is being 2 days from the end of your sprint and nothing is DoD-done yet.
The Retrospectives are the curer of all ills.
Watch for unscheduled work
Do you find yourself having to balance strategic work (long term projects) against your hair being on fire this week? Are you finding that you can't deliver anything or that you always miss your forecasts?
Do you note this unplanned work somehow?
Do you discuss this unplanned work in the retrospective.
Write down what you discussed in your retrospectives.
What went right and wrong?
What *actionable* things are you going to do for your next Sprint?