The document discusses adopting agile practices while still operating within a traditional waterfall development model. It begins with an anecdote about a team that was given a large project with a tight deadline and limited resources that had traditionally used waterfall. The team was able to deliver the project on time and under budget by adopting agile practices like breaking work into smaller projects, establishing team values, and securing executive support. The document advocates that agile principles can be successfully applied even within organizations still reliant on waterfall models.
Does this FizzGood? Improve velocity, predictability & agility by asking a si...Jon Terry
LeanKit's founding team had a strong Lean-Agile background from previous careers. So, in the early days of the company, we just instinctively did things in a Lean way with as few formal processes as any startup. But, like any growing company, we eventually did have to start clearly defining how we do things. And like anyone, we were tempted to become more bureaucratic - with lots of scheduling, coordination, meetings and estimates.
Instead, we developed our FSGD (Frequent Small Good Decoupled) approach. This LeanKit way of working has provided our teams with a simple yardstick for making effective decisions without a lot of cross team scheduling and coordination. It has simplified abstract Agile concepts into something everyone easily understands and cheerfully applies on a daily basis.
FSGD isn't a replacement for Kanban, Scrum, XP, etc. We strongly believe in and spend lots of time teaching our teams about the Kanban Method as well as standard Lean and Agile principles, tools, and techniques. But FSGD distills what we think are the key decision making elements of those methods into something everyone can remember.
We apply this model to all of our teams: design, development, testing, operations, sales, marketing, finance, HR. Indeed, we believe that applying it as broadly as possible makes it work most effectively.
Indeed, that's part of why the model doesn't reference software directly at all. It's meant to be generally applicable. One sub-concept included in the slides TLDR (Tested, Logged, Documented, Reviewed) is more specific to the technology context.
We have seen significant improvements in our delivery speed across multiple teams since rolling out the FSGD approach. We want to help other people gain the same benefits.
Bio:
Jon Terry is co-Chief Executive Officer of LeanKit. Before LeanKit, Jon held a number of senior IT positions with hospital-giant HCA and its logistics subsidiary, HealthTrust Purchasing Group. He was among those responsible for launching HCA’s adoption of Lean/Agile methods.
Jon earned his Global Executive MBA from Georgetown University and ESADE Business School in Barcelona, Spain, and his Masters Certificate in Project Management from George Washington University. He is a Project Management Professional, a Certified Scrum Master, a Kanban Coaching Professional, is certified in the Lean Construction Institute’s Last Planner Method, and trained in the SAFe Lean Systems Engineering method.
LeanKit Webinar: Evolving Your Daily Standup with Kanban by Brendan WovchkoLeanKit
Have your daily standups become stale? Discover how to reinvigorate the conversation by focusing on the core principles of Kanban.
Brendan Wovchko of HUGE I/O will explain how to engage teams with meaningful questions that surface problems, reduce process waste and improve the flow of work.
You'll learn how to:
- “Walk the board” with Kanban
- Experiment with fresh questions and techniques
- Decide if your daily standup really needs to be daily
Enabling your team to identify improvement opportunities on a daily basis promotes self-organization and keeps the focus on delivering value.
Lean and Kanban: An Alternative Path to Agility -Gartner PPM Summit 2014LeanKit
Chris Hefley, CEO of LeanKit, gives this presentation at the 2014 Gartner PPM & IT Governance Conference on Lean & Kanban-An Alternative Path to Agility.
Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone AgileSparks
Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone
By Hanan Alexander @ AgileIL12
http://agilesparks.com/KanbanPelephone-HananAlexander
Agile: the Good, the Bad and the Ugly - Webinar by Clarke Ching Agile - Septe...MARRIS Consulting
Webinar by Clarke Ching Agile and ToC expert. Agile: the Good, the Bad and the Ugly. If your Agile is broken then this is how to fix it!
Your Agile teams are busy. Busy delivering. Busy improving. Your quality is amazing. Rework is low. The product looks great. Your users love it. You are a high performing team!
But your internal customers say your teams are slow. This session will teach you how to use the Theory of Constraints to figure out how to speed up, by finding the one thing that’s slowing them down.
This webinar will cover how, in an Agile environment:
- to better control scope creep,
- to reinforce your relationship with the I.T. Development team’s client,
- to be able to make commitments and honour them and
- to decide where your bottleneck should be.
About the speaker
Clarke Ching is a computer scientist with an MBA who discovered Goldratt’s Theory of Constraints (ToC) in 2003 and has been using it ever since to accelerate Agile initiatives. He is fascinated by Agile and obsessed with ToC.
He wrote the amazon best-sellers Rolling Rocks Downhill and The Bottleneck Rules. Rolling Rocks Downhill teaches 3 things: the fundamentals of Agile combined with ToC; how to use those fundamentals to deliver big projects faster and on time; and how to deliver quietly huge transformations. It’s been featured in The Guardian newspaper and The Spectator magazine. It was one of Barbara Oakley’s top 10 books of 2019. It was the #2 best-selling Leadership book on amazon.com, just behind Steven Covey’s 7-habits book.
He has been Agile / Lean / ToC expert in: GE Energy, Dell, Royal London (life insurance & pensions), Gazprom and Standard Life Aberdeen among other organizations. He is the past Chairperson of Agile Scotland. He is a lecturer at Victoria University School Of Management in New Zealand where he now lives.
Today he is the founder and Chief Productivity Officer of Odd Socks Consulting
Does this FizzGood? Improve velocity, predictability & agility by asking a si...Jon Terry
LeanKit's founding team had a strong Lean-Agile background from previous careers. So, in the early days of the company, we just instinctively did things in a Lean way with as few formal processes as any startup. But, like any growing company, we eventually did have to start clearly defining how we do things. And like anyone, we were tempted to become more bureaucratic - with lots of scheduling, coordination, meetings and estimates.
Instead, we developed our FSGD (Frequent Small Good Decoupled) approach. This LeanKit way of working has provided our teams with a simple yardstick for making effective decisions without a lot of cross team scheduling and coordination. It has simplified abstract Agile concepts into something everyone easily understands and cheerfully applies on a daily basis.
FSGD isn't a replacement for Kanban, Scrum, XP, etc. We strongly believe in and spend lots of time teaching our teams about the Kanban Method as well as standard Lean and Agile principles, tools, and techniques. But FSGD distills what we think are the key decision making elements of those methods into something everyone can remember.
We apply this model to all of our teams: design, development, testing, operations, sales, marketing, finance, HR. Indeed, we believe that applying it as broadly as possible makes it work most effectively.
Indeed, that's part of why the model doesn't reference software directly at all. It's meant to be generally applicable. One sub-concept included in the slides TLDR (Tested, Logged, Documented, Reviewed) is more specific to the technology context.
We have seen significant improvements in our delivery speed across multiple teams since rolling out the FSGD approach. We want to help other people gain the same benefits.
Bio:
Jon Terry is co-Chief Executive Officer of LeanKit. Before LeanKit, Jon held a number of senior IT positions with hospital-giant HCA and its logistics subsidiary, HealthTrust Purchasing Group. He was among those responsible for launching HCA’s adoption of Lean/Agile methods.
Jon earned his Global Executive MBA from Georgetown University and ESADE Business School in Barcelona, Spain, and his Masters Certificate in Project Management from George Washington University. He is a Project Management Professional, a Certified Scrum Master, a Kanban Coaching Professional, is certified in the Lean Construction Institute’s Last Planner Method, and trained in the SAFe Lean Systems Engineering method.
LeanKit Webinar: Evolving Your Daily Standup with Kanban by Brendan WovchkoLeanKit
Have your daily standups become stale? Discover how to reinvigorate the conversation by focusing on the core principles of Kanban.
Brendan Wovchko of HUGE I/O will explain how to engage teams with meaningful questions that surface problems, reduce process waste and improve the flow of work.
You'll learn how to:
- “Walk the board” with Kanban
- Experiment with fresh questions and techniques
- Decide if your daily standup really needs to be daily
Enabling your team to identify improvement opportunities on a daily basis promotes self-organization and keeps the focus on delivering value.
Lean and Kanban: An Alternative Path to Agility -Gartner PPM Summit 2014LeanKit
Chris Hefley, CEO of LeanKit, gives this presentation at the 2014 Gartner PPM & IT Governance Conference on Lean & Kanban-An Alternative Path to Agility.
Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone AgileSparks
Beginning the Kanban journey at an Enterprise IT - Case study - Pelephone
By Hanan Alexander @ AgileIL12
http://agilesparks.com/KanbanPelephone-HananAlexander
Agile: the Good, the Bad and the Ugly - Webinar by Clarke Ching Agile - Septe...MARRIS Consulting
Webinar by Clarke Ching Agile and ToC expert. Agile: the Good, the Bad and the Ugly. If your Agile is broken then this is how to fix it!
Your Agile teams are busy. Busy delivering. Busy improving. Your quality is amazing. Rework is low. The product looks great. Your users love it. You are a high performing team!
But your internal customers say your teams are slow. This session will teach you how to use the Theory of Constraints to figure out how to speed up, by finding the one thing that’s slowing them down.
This webinar will cover how, in an Agile environment:
- to better control scope creep,
- to reinforce your relationship with the I.T. Development team’s client,
- to be able to make commitments and honour them and
- to decide where your bottleneck should be.
About the speaker
Clarke Ching is a computer scientist with an MBA who discovered Goldratt’s Theory of Constraints (ToC) in 2003 and has been using it ever since to accelerate Agile initiatives. He is fascinated by Agile and obsessed with ToC.
He wrote the amazon best-sellers Rolling Rocks Downhill and The Bottleneck Rules. Rolling Rocks Downhill teaches 3 things: the fundamentals of Agile combined with ToC; how to use those fundamentals to deliver big projects faster and on time; and how to deliver quietly huge transformations. It’s been featured in The Guardian newspaper and The Spectator magazine. It was one of Barbara Oakley’s top 10 books of 2019. It was the #2 best-selling Leadership book on amazon.com, just behind Steven Covey’s 7-habits book.
He has been Agile / Lean / ToC expert in: GE Energy, Dell, Royal London (life insurance & pensions), Gazprom and Standard Life Aberdeen among other organizations. He is the past Chairperson of Agile Scotland. He is a lecturer at Victoria University School Of Management in New Zealand where he now lives.
Today he is the founder and Chief Productivity Officer of Odd Socks Consulting
Mohammed Khalid, Senior Solutions Engineer at LeanKit, presented Using Kanban to Visualize Your Work - What it means and why its important at the Pink16 conference on February 16, 2016.
From Chaos to Confidence: DevOps at LeanKitJon Terry
As a company, LeanKit have believed in Lean, Kanban, Agile, DevOps since our founding. We've alway talked about how important these ideas are - in the community and inside our company.
But that doesn't mean that doing those things in practice has been easy. We're a very fast growing startup in a very competitive market space. We've tripled in size in less than a year and nearly came apart at the seams at times.
In fact, in the fall of 2015, our technology team were having a very hard team. We were out of synch with our sales & marketing partners and facing a lot of internal conflict.
But we came together as a team and worked hard to implement a well coordinated system of values, team structure, cadences, and standard practices. We're now in a much better place as a team and generating much better results for our company.
There are no one-size-fits-all answers for companies. I can't promise that if you copy LeanKit you'll succeed. But we do think we have some interesting lessons learned to share and that you just might be able to pick up some ideas that you can take back to your company.
Bio:
Jon Terry is co-Chief Executive Officer of LeanKit. Before LeanKit, Jon held a number of senior IT positions with hospital-giant HCA and its logistics subsidiary, HealthTrust Purchasing Group. He was among those responsible for launching HCA’s adoption of Lean/Agile methods.
Jon earned his Global Executive MBA from Georgetown University and ESADE Business School in Barcelona, Spain, and his Masters Certificate in Project Management from George Washington University. He is a Project Management Professional, a Certified Scrum Master, a Kanban Coaching Professional, is certified in the Lean Construction Institute’s Last Planner Method, and trained in the SAFe Lean Systems Engineering method.
Don't be Left Out: Tips for Working in a Remote TeamAtlassian
Working with a team on the other side of the world can be a lonely, frustrating experience. But with the right attitude, practices, and tools, it still can be an effective way to build software with others. Hear from Atlassian developer, Adam Hynes on how he moved to the other side of the world and stayed productive (and sane) without changing teams.
Learn how he uses tools such as Floobits for real-time remote pairing, Confluence for white-boarding hard problems with distant teammates, and HipChat for asynchronous stand-ups to keep the team on the same page across timezones.
You'll come away with several remote working tips that'll set you up for success.
Adam Hynes, Senior Developer, Atlassian
Austin product camp 11 Agile - doing vs beingKelly Looney
Talk about the difference between just doing a few Agile practices and pretending are are Agile and actually having the Agile mindset. In, addition we talk about guiding development with an Agile Value team.
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.
Climbing out of a Crisis Loop at the BBCRafiq Gemmail
A talk I gave with my friend and mentor Katherine Kirk, on our journey to Scrumban and a leaner workflow at the BBC. See https://www.infoq.com/presentations/bbc-agile-case-study for the full presentation.
Technical Excellence Doesn't Just Happen - AgileIndy 2016Allison 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.
As scrum masters, agile coaches and facilitators we spend a lot of time and energy to come up with new and ever-changing retrospective formats. Our goals are noble- we want to get people engaged, build trust within the team, change the perspective, reframe the conversation, and keep everyone coming back for more. What we are really trying to achieve in varied retrospective formats isn’t more data, its better data. Learn the five types of retrospective data your team needs for targeted improvements that guarantee more than a bi-weekly "airing of grievances." We will focus on how to solicit all five types of data while gathering feedback continuously so you can maximize your retrospective conversations on improving and not remembering.
In the world of agile, there is theory and then there is practice. We like to talk about self-organizing teams, asynchronous execution, BDD, TDD, and emergent architecture. We also talk about cross-functional teams: how analysts, testers, architects, technical writers, and UX designers belong on the same team, right next to programmers. It all sounds nice in theory, but how does this work in reality? What do these people actually do? How do they interact? What does it look like? Is there really a pragmatic way to make this work?
In this simulation, a cross-functional team will actually build a piece of software. Every specialist will have a hand in the process. Every specialist will also act as a generalist. Everyone will add value. And as a team, we’ll get something DONE.
This is your opportunity to see agile development in practice, and to bridge the gap between what agilists say and what teams do. And it’s not as new or as difficult as you think – affinity between testers, BA’s, coders, and other team members has really been at the root of effective development practices all along. Let’s just finally acknowledge that it works, demonstrate its capabilities, and encourage it going forward.
This IS agile development.
Games become more and more important to help people understand the underlying mindset. They help us try new things and experiment in a safe environment. The question is: what makes a good agile game and how to develop one? Before we developed the game I only knew some models about how to develop them, but it was still mostly an abstract concept for me. In this session I want to tell the story of how we developed the Kanban Pizza Game.
Presented at Agile & Beyond 2015
How do you define 'value'? What does it take for a business to shift 'Value' into high gear and create experiences leaving your customer saying "Wow"? Why does the software industry struggle to even meet expectations? If you're struggling to create valuable experiences for your customer then this session is for you.
Every team I work with talks about delivering valuable features, and yet many of their customers are dissatisfied. When I question how they define value I might get text book answers about ROI, sales, efficiencies or other quantifiable measures. Although these are important measures, I don't believe 'value' can be defined by anything you can quantify. If that's true then how do we get from "Valuable" to "Wow" without going broke?
We will start by examining two similar customer experiences. Both experiences are valuable, one met expectations but the other left the customer going 'Wow!'. Regardless of what business your in, with some awareness it's possible to start creating more 'Wow!' moments for your customers.
Mohammed Khalid, Senior Solutions Engineer at LeanKit, presented Using Kanban to Visualize Your Work - What it means and why its important at the Pink16 conference on February 16, 2016.
From Chaos to Confidence: DevOps at LeanKitJon Terry
As a company, LeanKit have believed in Lean, Kanban, Agile, DevOps since our founding. We've alway talked about how important these ideas are - in the community and inside our company.
But that doesn't mean that doing those things in practice has been easy. We're a very fast growing startup in a very competitive market space. We've tripled in size in less than a year and nearly came apart at the seams at times.
In fact, in the fall of 2015, our technology team were having a very hard team. We were out of synch with our sales & marketing partners and facing a lot of internal conflict.
But we came together as a team and worked hard to implement a well coordinated system of values, team structure, cadences, and standard practices. We're now in a much better place as a team and generating much better results for our company.
There are no one-size-fits-all answers for companies. I can't promise that if you copy LeanKit you'll succeed. But we do think we have some interesting lessons learned to share and that you just might be able to pick up some ideas that you can take back to your company.
Bio:
Jon Terry is co-Chief Executive Officer of LeanKit. Before LeanKit, Jon held a number of senior IT positions with hospital-giant HCA and its logistics subsidiary, HealthTrust Purchasing Group. He was among those responsible for launching HCA’s adoption of Lean/Agile methods.
Jon earned his Global Executive MBA from Georgetown University and ESADE Business School in Barcelona, Spain, and his Masters Certificate in Project Management from George Washington University. He is a Project Management Professional, a Certified Scrum Master, a Kanban Coaching Professional, is certified in the Lean Construction Institute’s Last Planner Method, and trained in the SAFe Lean Systems Engineering method.
Don't be Left Out: Tips for Working in a Remote TeamAtlassian
Working with a team on the other side of the world can be a lonely, frustrating experience. But with the right attitude, practices, and tools, it still can be an effective way to build software with others. Hear from Atlassian developer, Adam Hynes on how he moved to the other side of the world and stayed productive (and sane) without changing teams.
Learn how he uses tools such as Floobits for real-time remote pairing, Confluence for white-boarding hard problems with distant teammates, and HipChat for asynchronous stand-ups to keep the team on the same page across timezones.
You'll come away with several remote working tips that'll set you up for success.
Adam Hynes, Senior Developer, Atlassian
Austin product camp 11 Agile - doing vs beingKelly Looney
Talk about the difference between just doing a few Agile practices and pretending are are Agile and actually having the Agile mindset. In, addition we talk about guiding development with an Agile Value team.
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.
Climbing out of a Crisis Loop at the BBCRafiq Gemmail
A talk I gave with my friend and mentor Katherine Kirk, on our journey to Scrumban and a leaner workflow at the BBC. See https://www.infoq.com/presentations/bbc-agile-case-study for the full presentation.
Technical Excellence Doesn't Just Happen - AgileIndy 2016Allison 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.
As scrum masters, agile coaches and facilitators we spend a lot of time and energy to come up with new and ever-changing retrospective formats. Our goals are noble- we want to get people engaged, build trust within the team, change the perspective, reframe the conversation, and keep everyone coming back for more. What we are really trying to achieve in varied retrospective formats isn’t more data, its better data. Learn the five types of retrospective data your team needs for targeted improvements that guarantee more than a bi-weekly "airing of grievances." We will focus on how to solicit all five types of data while gathering feedback continuously so you can maximize your retrospective conversations on improving and not remembering.
In the world of agile, there is theory and then there is practice. We like to talk about self-organizing teams, asynchronous execution, BDD, TDD, and emergent architecture. We also talk about cross-functional teams: how analysts, testers, architects, technical writers, and UX designers belong on the same team, right next to programmers. It all sounds nice in theory, but how does this work in reality? What do these people actually do? How do they interact? What does it look like? Is there really a pragmatic way to make this work?
In this simulation, a cross-functional team will actually build a piece of software. Every specialist will have a hand in the process. Every specialist will also act as a generalist. Everyone will add value. And as a team, we’ll get something DONE.
This is your opportunity to see agile development in practice, and to bridge the gap between what agilists say and what teams do. And it’s not as new or as difficult as you think – affinity between testers, BA’s, coders, and other team members has really been at the root of effective development practices all along. Let’s just finally acknowledge that it works, demonstrate its capabilities, and encourage it going forward.
This IS agile development.
Games become more and more important to help people understand the underlying mindset. They help us try new things and experiment in a safe environment. The question is: what makes a good agile game and how to develop one? Before we developed the game I only knew some models about how to develop them, but it was still mostly an abstract concept for me. In this session I want to tell the story of how we developed the Kanban Pizza Game.
Presented at Agile & Beyond 2015
How do you define 'value'? What does it take for a business to shift 'Value' into high gear and create experiences leaving your customer saying "Wow"? Why does the software industry struggle to even meet expectations? If you're struggling to create valuable experiences for your customer then this session is for you.
Every team I work with talks about delivering valuable features, and yet many of their customers are dissatisfied. When I question how they define value I might get text book answers about ROI, sales, efficiencies or other quantifiable measures. Although these are important measures, I don't believe 'value' can be defined by anything you can quantify. If that's true then how do we get from "Valuable" to "Wow" without going broke?
We will start by examining two similar customer experiences. Both experiences are valuable, one met expectations but the other left the customer going 'Wow!'. Regardless of what business your in, with some awareness it's possible to start creating more 'Wow!' moments for your customers.
How to Pitch a Software Development Initiative and Ignite Culture ChangeRed Gate Software
You’ve got a great idea for transforming software development or IT processes in your organization, but you’re not sure how to get buy-in from key stakeholders, or how to change your company culture.
In this session, Microsoft MVP Ike Ellis will draw on his experience as a consultant and leader in software development to give you real-world tips to define, shape, and share your pitch successfully. Whether you are launching a revolutionary new initiative or expanding an existing effort to improve your software development, Ike’s tips will help you create a plan to effect change in your teams.
Using Agile Methodology to Deliver Projects That Transform Customers from Dou...Mike Harris
Examine the agile best practices currently employed by leading web hosting provider, Ecommerce Inc. to deliver best in class technology solutions. By employing these practices, any IT organization can move projects from unpredictable and frustrating to transparent, disciplined, repeatable and most important, successful. We will walk step by step through the practices that you must implement, which are optional and which you should avoid. You will leave this talk with a pragmatic set of tools and practices that you can take back and employ immediately on your own projects to transform you customers from doubters to raving fans.
Beyond the Crystal Ball –The Agile PMO - Heather Fleming and Justin RiservatoAtlassian
Perhaps we've set our project management officers (PMOs) up for failure. Without knowing it, we ask them to predict the future using a one-size-fits-all approach to best practices – and that just doesn't work. There is no magic crystal ball! Learn how an agile PMO can help your organization tackle the right work, at the right time, with the right teams using JIRA.
OK, I’m ready to DevOp. Now what?
We’ve heard a lot about the technologies behind DevOps, and even a bit on the processes that some DevOps shops employ. What we haven’t heard too much about directly is a fundamental matter of bootstrapping. If you’re a leader or influencer in a software or IT shop, you’re sold on this DevOps idea but overwhelmed by the difference between where you are now and where you need to be, you’ve come to the right place. We’ve heard all about the unicorns of the movement, and what they are doing. Much time is spent talking about their innovative technologies. But how did they get there? Moreover, how can YOU get there? We’re going to spend some time discussing how to get started and find success on the rocky road to DevOps. We’re going to talk about the roles of executives, middle managers, front line managers, and individual contributors in this transformation. We’ll talk about the layered approach to transforming your culture, and building the processes and tool chains on top of it. At the tactical level, we’re going to talk about an example team and what their first year looks like, what are the major milestones they will reach, and how to measure their success along the way.
INNOVATION ROOTS | Webinar | Three Secrets of Agile Leaders | Peter StevensInnovation Roots
Overview:
Agility as a movement started with software developers uncovering better ways of doing what they do. Today that movement is driving even business leaders to rethink how they lead their organizations. What does it mean to "be" agile? How can agility be applied to leading organizations? Where do successful agile leaders start? Three stories, three secrets, and three tips to apply agility to your life and work and unlock your potential as an executive or a manager.
Learning Objectives:
1. Connect agility at the personal, the team and the organizational level
2. Experience how the same challenges that led to poor performance in software development 30 years ago still plague the management of most organizations today.
3. Learn 3 simple techniques to unlock the potential of management.
4. Learn the key concepts and principles of Personal Agility
Switching on the agile light takes more than flickMike Burns
"There is a large difference between doing agile and being agile. Modern change management techniques suggest many ways of implementing a new organisational change such as agility. However, there are times when just doing it and making it the baseline means that you can kick-start the agile journey. This presentation will present some ideas on the things that you can enforce and the things that will take time."
Presented as part of the "Agile & DevOps Conference- LET’S SWITCH IT ON", held in Brisbane on the 31st of August 2018
https://www.knowledgehut.com/events/devops/agile-devops-conference-brisbane
Anti-patterns for not-so-smart processes: Avoiding the BPM and SOA pitfalls. A short presentation to focus your project on success - featuring the "magic progress fairy"
Practical Agile. Lessons learned the hard way on our journey building digita...TechExeter
Ian Ames - Practical agile. Lessons learned the hard way on our journey building digital products.
Slides from the TechExeter Conference, 8th October 2016.
www.techexeter.uk
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.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
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.
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/
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
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
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.
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.
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.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
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.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024
Being agile while standing in a waterfall
1. Being agile
while standing in a Waterfall
!
Mike Edwards
!
!
!
!
mike@leanintuit.com
Twitter: @mikeeedwards
Blog: www.mikeeedwards.ca
References: agilewaterfall.ca
3. Agile will fail at my workplace
because of ...
•
•
•
•
•
•
•
•
•
•
•
The concept of dedicating to one task at a time is not supported
Because of our culture
They won’t change
Of me
It’s counterintuitive and hard to practice
Too focused on mechanics
Ridiculous product owners
What we do already works
Not everyone on our team understands it
We only fund capital projects
My boss who manages with fear
( Taken from Agile 2013 )
6. I
SYSTE
M
I
ANALYSIS
PROGRAM
DESIGN
I
coo,.o
TESTING
I OPERATIONS
Figure 2. Implementation steps to develop a large computer program for delivery to a customer.
I believe in this concept, but the implementation described above is risky and invites failure. The
“I believe in this concept, but the implementation
described above is risky and invites failures” -Winston Royce (August 1970)
problem is illustrated in Figure 4. The testing phase which occurs at the end of the development cycle is the
first event for which timing, storage, input/output transfers, etc., are experienced as distinguished from
analyzed. These phenomena are not precisely analyzable. They are not the solutions to the standard partial
differential equations of mathematical physics for instance. Yet if these phenomena fail to satisfy the various
external constraints, then invariably a major redesign is required. A simple octal patch or redo of some isolated
code will not fix these kinds of difficulties. The required design changes are likely to be so disruptive that the
software requirements upon which the design is based and which provides the rationale for everything are
7. Computing: Then & Now
IBM System/360
.034 MIPS
max 16MB memory
225MB Disk
$50k/month to lease
$15mm to buy
12. The situation
• Towards end of a larger troubled project
(we kept dropping scope)
• Team only available for 3 more months
• Budget defined by available people and time
• Low key enhancement project
• Waterfall was best described as a religion
13. Go!
• Secured a war ‘area’
• Given free reign to ‘try something different’
• Simple one sentence scope statement
• No authority to NOT do something in the
department’s process
• Executive sponsorship watched closely
14. The Result!
• Finished early
• Finished slightly under budget
• Features delivered exceeded customer
expectation
• No quality issues after go-live
• Happy customer!
17. Agile Manifesto
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
!
That is, while there is value in the items on
the right, we value the items on the left more.
19. Learning vs. Improving
We can learn the mechanic
didn’t latch the cowling
Feel better?
What does it mean
to improve?
20. Improve how you Improve
•
Conduct regular retrospectives
throughout the project
•
•
Empower teams to improve
•
Make improvement an objective
for teams
Make room for ongoing
improvements
22. People
• Support those who deliver value
• Motivate them
• Trust them
• Create sustainable pace
• Foster responsibility
• Have fun!
23. Collaborate!
•
•
•
•
•
•
Examine the value of your weekly status meetings
Tear down the walls
Eliminate the hierarchy
Make information visible
Build a cross functional team
Build a high performing team
24. Ideas
Make it about principles
Conduct regular Retrospectives & Improve
Create a high performance team
26. Why do we need
Change Management?
Decisions are made prematurely!
Our customers cannot possibly know what they
want in detail at the start of a project
31. What can you do about
change?
Embrace it!
Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
(Agile Manifesto - Principle #2)
!
!
!
!
!
Create an environment
allowing everyone to learn
32. Ideas
Make it about principles
Conduct regular Retrospectives & Improve
Create a high performance team
Defer decisions until the last responsible
moment
36. Ideas
Make it about principles
Conduct regular Retrospectives & Improve
Create a high performance team
Defer decisions until the last responsible
moment
‘Deliver’ frequently
Simplicity
37. Status Reporting
• Start ALL projects red
• Check the politics at the door
• Honesty & Transparency
• Put your status on the wall
• Build plans allowing for clearer
reporting
38. Ideas
Make it about principles
Conduct regular Retrospectives & Improve
Create a high performance team
Defer decisions until the last responsible
moment
‘Deliver’ frequently
Simplicity
Start ALL projects red!
42. Some words of wisdom
!
a.k.a. Things I’ve learned the hard way
43. Things I’ve learned
•
Culture cannot be changed - change how the work
is done and culture will follow
•
Start from where you are today and never be
satisfied
•
•
•
•
Improve the whole
Improve one step at a time
Iterate (Build Measure Learn)
Have fun!
49. Once upon a time ...
• Final component of a larger program
• Estimated at 1200 days
• Drop dead date of 3.5 months
• Highly visible if we failed
• Core team assigned of 5 IT people
• Waterfall was all we knew
50. Go!
• 15 contractors in the door within 2 weeks
• Secured a team room
• Broke the work out into projects
• Published a team manifesto
• Developed a mantra: “Failure is not an
option”
• Strong executive sponsorship
51. The Result!
• Delivered on the date we said we would
• Actuals came in $8000 under budget
• Delivered all key scope items
• No significant quality issues after go-live
• Happy customer!
