Want to move to Continuous Delivery? Keep these things in mind. It's a mind-set shift. Take a holistic view. Don't presume Automation is the silver bullet.
This document summarizes Tom Walsham's lessons learned from scaling an agency from 15 to 60 employees. Some key points:
1) As the agency grew, it faced challenges around predictability, quality, productivity and other areas that process was meant to address.
2) Early on, the agency did not have formal processes around areas like estimation, quality assurance, toolchain standardization. This led to problems.
3) As the agency developed processes, it focused on aspects like implementing QA systems, formalizing discovery documents, standardizing tools, and improving resourcing and resource planning.
4) Walsham emphasizes that process needs to evolve as the business grows and that measuring metrics is key to continuous
The prototype is all done and it seems to work well. Now, how do you get the prototype manufactured reliably and at a reasonable cost? If you're like a lot of small companies, this is not something you do all the time. Finish Line has done more than one thousand projects for more than 250 small companies and we have learned a few things in the process.
Get into bed with qa and keep testing agileAgileCymru
If you’re in bed with your partner but you’re not collaborating, then nothing good is going to come of it. You don’t have the same vision, you lose sight of what needs to be done and the end result is likely to be poor quality and, of course, disappointing.
The same can be said for Quality Assurance (QA), and testing in development projects.
Fully incorporating testing into your project from the start is essential to cross-team collaboration - after all, only by maintaining interaction between development and testing can you ensure a quality and secure end-product. So rather than leave testing to the end, we say get into bed with QA from the beginning - for a lasting relationship that keeps both you, and your client, smiling.
This document discusses various myths, truths, and areas of chaos related to quality assurance (QA). It addresses myths such as testing being a fading job, QA not coding, and artifacts only being for QA. It also discusses truths around QA involvement in refinement, stakeholders not understanding QA's value, and testing not starting after development. Finally, it examines areas of chaos around differences between iterative and incremental development and attributing bugs to individuals.
The document discusses common reasons why Agile adoptions often "fail" and provides recommendations for a successful Agile transition. It notes that Agile adoptions typically fail because they ignore organizational culture and constraints, underestimate the importance of mindset change, over-rely on tools instead of principles, and lack sufficient training and coaching. The document recommends focusing on organizational systems and culture, emphasizing principles over practices, training all levels of the organization, taking an empirical rather than predictive approach, and continuously improving through experimentation and questioning assumptions.
This document summarizes Tom Walsham's lessons learned from scaling an agency from 15 to 60 employees. Some key points:
1) As the agency grew, it faced challenges around predictability, quality, productivity and other areas that process was meant to address.
2) Early on, the agency did not have formal processes around areas like estimation, quality assurance, toolchain standardization. This led to problems.
3) As the agency developed processes, it focused on aspects like implementing QA systems, formalizing discovery documents, standardizing tools, and improving resourcing and resource planning.
4) Walsham emphasizes that process needs to evolve as the business grows and that measuring metrics is key to continuous
The prototype is all done and it seems to work well. Now, how do you get the prototype manufactured reliably and at a reasonable cost? If you're like a lot of small companies, this is not something you do all the time. Finish Line has done more than one thousand projects for more than 250 small companies and we have learned a few things in the process.
Get into bed with qa and keep testing agileAgileCymru
If you’re in bed with your partner but you’re not collaborating, then nothing good is going to come of it. You don’t have the same vision, you lose sight of what needs to be done and the end result is likely to be poor quality and, of course, disappointing.
The same can be said for Quality Assurance (QA), and testing in development projects.
Fully incorporating testing into your project from the start is essential to cross-team collaboration - after all, only by maintaining interaction between development and testing can you ensure a quality and secure end-product. So rather than leave testing to the end, we say get into bed with QA from the beginning - for a lasting relationship that keeps both you, and your client, smiling.
This document discusses various myths, truths, and areas of chaos related to quality assurance (QA). It addresses myths such as testing being a fading job, QA not coding, and artifacts only being for QA. It also discusses truths around QA involvement in refinement, stakeholders not understanding QA's value, and testing not starting after development. Finally, it examines areas of chaos around differences between iterative and incremental development and attributing bugs to individuals.
The document discusses common reasons why Agile adoptions often "fail" and provides recommendations for a successful Agile transition. It notes that Agile adoptions typically fail because they ignore organizational culture and constraints, underestimate the importance of mindset change, over-rely on tools instead of principles, and lack sufficient training and coaching. The document recommends focusing on organizational systems and culture, emphasizing principles over practices, training all levels of the organization, taking an empirical rather than predictive approach, and continuously improving through experimentation and questioning assumptions.
Performance and Metrics at Lonely PlanetMark Jennings
Lonely Planet worked to improve the performance of their website to increase conversion rates and revenue. They found removing third-party content sped up page loads but hurt engagement. Experiments showed performance improvements between 100-200ms increased conversion. Cultural change was needed to prioritize performance, with expanded engineer roles and comprehensive, visible metrics. Tools like Fozzie and Flamsteed helped measure performance and capture real user monitoring data. Continuous experimentation and collaboration keep Lonely Planet staying fast.
A look at using the spirit of agile software development practices to deliver projects in the Ugandan context.
This presentation was delivered to a startups based out of Hive Colab a co-working and incubation hup in Kampala as one of the TGIF evenings on Friday February 3, 2017
What is DevOps and how do SysAdmins participate in it? Explains what DevOps is and is not and provides tools, tips, and tricks for SysAdmins to participate and find value. Presented at Indianapolis VMUG's November 2014 meeting.
The document discusses bringing Lean principles to office environments. It notes that culture change is the most difficult part of any Lean implementation. The document then provides an example of ineffective marketing material that did not understand customer needs in a rural area. Finally, it offers suggestions for applying Lean tools like 5S, standardization, kanban, and visual management boards to office processes to reduce waste and improve communication and problem solving.
Quality is not the responsibility of testers alone, but of the whole agile team. It should be a shared mindset and definition agreed upon by the team. Several techniques can help build quality in, including defining acceptance criteria through conversations between product owners, developers and testers; practicing test-driven development; and ensuring story kick-offs and "shoulder taps" between team members to facilitate collaboration and catch issues early. The document discusses the importance of collaboration, automation, and not trading off quality to deliver features quickly.
I found the book was an easy to read, was entertaining and surprisingly compelling and informative. and therefore I do not hesitate in recommending this to you, even if you may not be working directly in technology.
CEOs best practices to win time back & focus on what mattersTheFamily
30% of executives' time is spent on low-value or delegable tasks. The document provides tips for remote CEOs to save time, including setting focus time with notifications turned off, communicating asynchronously through organized tools, limiting distractions from emails and notifications, establishing routines, planning the week in advance, and regularly reviewing time spent. The overall message is that working remotely requires being intentional with how time is spent each day and week.
A talk first given at DevOpsDays in Stockholm.
The way we approach automation is riddled with misconceptions. This talks goes through a bunch of those and addresses how to think of them.
Kanban Methodologist Certification at XebiaPooja Gulati
Kanban is a Lean-agile method also referred to as a second-generation agile methodology. It adapts to your organization and project needs very rapidly and allows your team to operate at a very high level of productivity due to its evolutionary approach to manage change in the organization. It has proven to accelerate maturity through high visualization, control over the amount of work being done, acknowledgement and effective handling of the diversity of activities in your project, and root cause analysis through quantification.
From Design Thinking to DevOps and Back Again: Unifying Design and OperationsJeff Sussna
The document discusses the relationship between design and operations. It argues that design has traditionally been about figuring out what comes next while operations focuses on taking care of what's happening now. However, it says that in today's world where IT is continuously evolving, the boundaries between design and operations are blurring. Design is becoming more about continuous iteration and improvement while operations involves more upfront problem solving. The document advocates for an approach where design and operations work together in a continuous feedback loop to best meet customer needs.
Salesforce, Google, Facebook, NimbleUser -- To be sure all of our customers are using all of our best work, software as a service peeps rollout software fixes continuously, and major versions several times a year.
Learn what best practices we use to ensure each release is better than the last, with take-away pointers as to how you can use similar techniques in your own organization.
The document discusses how to successfully implement agile and Scrum methodologies on projects, highlighting the importance of managing expectations, using the right tools like Jira and Greenhopper to plan sprints and track progress, and identifying the right projects and knowing when to walk away from projects that are not a good fit for an agile approach.
by Alan Taylor (Innodev)
Test Driven Development is an engineering concept with practices that has great benefit to business. For example, if your business wants to have idealised and revered products, you will have:
- an ability to deliver high quality products which keep up with the latest customer wishes;
- products which are constantly updated with the latest cool features; and
- ability to very quickly resolve any issues that do occur – and they do for even the best organisation
We will share with you why Test Driven Development is a pivotal tool in the fight to be one of those inspiring organisations. We will cover the practices at a high level and go into the outcomes of those practices. We will include not only how the business should benefit directly from them, but also how they provide indirect benefits for the team and the organisation. Every positive has some negatives, whether they are perceived or actual, long term or short term). We will touch on how they are like any form of exercise – they will be hard work at times, but afterwards the results will include fitter, stronger and faster teams able to delivery consistently better results.
As a manager or leader, you will be able to walk away with insight that will enable you to determine how TDD is worth following up in your domain.
As someone within the delivery team, you will leave with deeper understanding of how you, your team and your company can effectively benefit from Test Driven Development.
Changing business of testing - Testing Assembly Helsinki 2014Vasco Duarte
Testing jobs will move to cheaper countries unless the role of testing changes. This is a trend that is happening already, we see large teams of testers being moved to other countries, simply because it is cheaper to do bad testing there!
Testing is a critical part of the product and software development process, and if we don't change its role it will slowly become obsolete. The fact is, that the traditional view of testing endangers testing jobs: now here, and later also in cheaper countries.
I propose a different view of testing. I propose that testing is about enabling business results, not just technical quality. I propose that the tester's job goes far beyond finding issues to track, but also finding users to acquire, finding methods to succeed in the software business. Testing in my view is about making businesses succeed, not about avoid failures in software.
In this presentation I'll describe how a very simple change can profoundly transform the role of testing in a way that it directly enables and supports our businesses! Testing is about making our businesses succeed!
The road ahead is not easy, and not every tester is ready to embrace this view of testing. But the road ahead is inevitable. And we have to start on that journey now!
The team found a bug in their code related to parsing datetime values. They thanked the developer who reported the bug and worked to reproduce and understand the root cause. They added a failing test case, fixed the code, and reran all tests to confirm the fix worked. Based on their analysis, they identified ways to improve testing practices and prevent similar bugs. They searched the code for other similar datetime parsing issues, finding two additional bugs. The team is committed to continuously improving their processes to deliver high quality code.
Whether you’re a manager, product manager, designer or engineer, at some point during the product lifecycle you will have to deal with legacy. During this talk, I will explain how to tackle product legacy by understanding what it is, evaluating the gravity of it, defining and applying the right techniques and most importantly what you should learn from it. All of this without having to start coding from scratch and without impacting your existing users.
Uswitch.com transitioned from a traditional waterfall development process to agile practices like Scrum and XP over three years. While this improved speed, they still found planning overhead and low velocity. They then evolved to a fully lean approach, removing roles like QA and PM, limiting work-in-progress, releasing on demand, and building quality in rather than inspecting. This led to quicker time to market, reduced waste, safer and more frequent releases, and quality built-in rather than inspected. Measuring value is difficult but they focus on revenue, customer experience, innovation, and efficiency gains.
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
The PEX event discussed why BPM so often fails. This presentation reveals why that is so, and then demonstrates how, by following a well trodden path we can all get it right.
It is BPM Jim but not as we know it!
gineering teams. This workshop will cover everything you need to know to work seamlessly with engineering teams that use agile principles and practices.
What you will learn:
• Basics of the agile methods.
• Tips you can apply the very next day at work.
• Actionable tools and tactics to handle different product team scenarios that a product manager face.
Who is this workshop for:
• Software engineers who want to transition to Product Management
• MBAs with a finance/consulting background who want to work in high-tech companies as a Product Manager
• Project Managers, Marketers, Designers who are seeking for new opportunities in Product Management
The document discusses how to evolve corporate culture for long term success through continuous improvement. It advocates adopting systems to control products and equipment to achieve evolutionary benefits like lower costs and higher quality over time rather than periodic revolutionary changes. This approach leads to less variability, better process control, and business sustainability through changing cycles.
Always ready for release by Bogdan CosteaBosnia Agile
Agility is not about following a process, it's about delivering on expectations and that's way easier when you have a good release pipeline that automates as much of the process as possible.
Being able to release and deploy to production at any time doesn't imply that you're going to do it, it just means you are ready to do it at any time, and who doesn't want that right?
The talk goes through the evolution of release automation starting with automated builds, unit testing, CI, continuous delivery and continuous deployment with lots of examples and a couple of demos (a setup for a complex Java enterprise app and a simple ruby Sinatra web app).
Performance and Metrics at Lonely PlanetMark Jennings
Lonely Planet worked to improve the performance of their website to increase conversion rates and revenue. They found removing third-party content sped up page loads but hurt engagement. Experiments showed performance improvements between 100-200ms increased conversion. Cultural change was needed to prioritize performance, with expanded engineer roles and comprehensive, visible metrics. Tools like Fozzie and Flamsteed helped measure performance and capture real user monitoring data. Continuous experimentation and collaboration keep Lonely Planet staying fast.
A look at using the spirit of agile software development practices to deliver projects in the Ugandan context.
This presentation was delivered to a startups based out of Hive Colab a co-working and incubation hup in Kampala as one of the TGIF evenings on Friday February 3, 2017
What is DevOps and how do SysAdmins participate in it? Explains what DevOps is and is not and provides tools, tips, and tricks for SysAdmins to participate and find value. Presented at Indianapolis VMUG's November 2014 meeting.
The document discusses bringing Lean principles to office environments. It notes that culture change is the most difficult part of any Lean implementation. The document then provides an example of ineffective marketing material that did not understand customer needs in a rural area. Finally, it offers suggestions for applying Lean tools like 5S, standardization, kanban, and visual management boards to office processes to reduce waste and improve communication and problem solving.
Quality is not the responsibility of testers alone, but of the whole agile team. It should be a shared mindset and definition agreed upon by the team. Several techniques can help build quality in, including defining acceptance criteria through conversations between product owners, developers and testers; practicing test-driven development; and ensuring story kick-offs and "shoulder taps" between team members to facilitate collaboration and catch issues early. The document discusses the importance of collaboration, automation, and not trading off quality to deliver features quickly.
I found the book was an easy to read, was entertaining and surprisingly compelling and informative. and therefore I do not hesitate in recommending this to you, even if you may not be working directly in technology.
CEOs best practices to win time back & focus on what mattersTheFamily
30% of executives' time is spent on low-value or delegable tasks. The document provides tips for remote CEOs to save time, including setting focus time with notifications turned off, communicating asynchronously through organized tools, limiting distractions from emails and notifications, establishing routines, planning the week in advance, and regularly reviewing time spent. The overall message is that working remotely requires being intentional with how time is spent each day and week.
A talk first given at DevOpsDays in Stockholm.
The way we approach automation is riddled with misconceptions. This talks goes through a bunch of those and addresses how to think of them.
Kanban Methodologist Certification at XebiaPooja Gulati
Kanban is a Lean-agile method also referred to as a second-generation agile methodology. It adapts to your organization and project needs very rapidly and allows your team to operate at a very high level of productivity due to its evolutionary approach to manage change in the organization. It has proven to accelerate maturity through high visualization, control over the amount of work being done, acknowledgement and effective handling of the diversity of activities in your project, and root cause analysis through quantification.
From Design Thinking to DevOps and Back Again: Unifying Design and OperationsJeff Sussna
The document discusses the relationship between design and operations. It argues that design has traditionally been about figuring out what comes next while operations focuses on taking care of what's happening now. However, it says that in today's world where IT is continuously evolving, the boundaries between design and operations are blurring. Design is becoming more about continuous iteration and improvement while operations involves more upfront problem solving. The document advocates for an approach where design and operations work together in a continuous feedback loop to best meet customer needs.
Salesforce, Google, Facebook, NimbleUser -- To be sure all of our customers are using all of our best work, software as a service peeps rollout software fixes continuously, and major versions several times a year.
Learn what best practices we use to ensure each release is better than the last, with take-away pointers as to how you can use similar techniques in your own organization.
The document discusses how to successfully implement agile and Scrum methodologies on projects, highlighting the importance of managing expectations, using the right tools like Jira and Greenhopper to plan sprints and track progress, and identifying the right projects and knowing when to walk away from projects that are not a good fit for an agile approach.
by Alan Taylor (Innodev)
Test Driven Development is an engineering concept with practices that has great benefit to business. For example, if your business wants to have idealised and revered products, you will have:
- an ability to deliver high quality products which keep up with the latest customer wishes;
- products which are constantly updated with the latest cool features; and
- ability to very quickly resolve any issues that do occur – and they do for even the best organisation
We will share with you why Test Driven Development is a pivotal tool in the fight to be one of those inspiring organisations. We will cover the practices at a high level and go into the outcomes of those practices. We will include not only how the business should benefit directly from them, but also how they provide indirect benefits for the team and the organisation. Every positive has some negatives, whether they are perceived or actual, long term or short term). We will touch on how they are like any form of exercise – they will be hard work at times, but afterwards the results will include fitter, stronger and faster teams able to delivery consistently better results.
As a manager or leader, you will be able to walk away with insight that will enable you to determine how TDD is worth following up in your domain.
As someone within the delivery team, you will leave with deeper understanding of how you, your team and your company can effectively benefit from Test Driven Development.
Changing business of testing - Testing Assembly Helsinki 2014Vasco Duarte
Testing jobs will move to cheaper countries unless the role of testing changes. This is a trend that is happening already, we see large teams of testers being moved to other countries, simply because it is cheaper to do bad testing there!
Testing is a critical part of the product and software development process, and if we don't change its role it will slowly become obsolete. The fact is, that the traditional view of testing endangers testing jobs: now here, and later also in cheaper countries.
I propose a different view of testing. I propose that testing is about enabling business results, not just technical quality. I propose that the tester's job goes far beyond finding issues to track, but also finding users to acquire, finding methods to succeed in the software business. Testing in my view is about making businesses succeed, not about avoid failures in software.
In this presentation I'll describe how a very simple change can profoundly transform the role of testing in a way that it directly enables and supports our businesses! Testing is about making our businesses succeed!
The road ahead is not easy, and not every tester is ready to embrace this view of testing. But the road ahead is inevitable. And we have to start on that journey now!
The team found a bug in their code related to parsing datetime values. They thanked the developer who reported the bug and worked to reproduce and understand the root cause. They added a failing test case, fixed the code, and reran all tests to confirm the fix worked. Based on their analysis, they identified ways to improve testing practices and prevent similar bugs. They searched the code for other similar datetime parsing issues, finding two additional bugs. The team is committed to continuously improving their processes to deliver high quality code.
Whether you’re a manager, product manager, designer or engineer, at some point during the product lifecycle you will have to deal with legacy. During this talk, I will explain how to tackle product legacy by understanding what it is, evaluating the gravity of it, defining and applying the right techniques and most importantly what you should learn from it. All of this without having to start coding from scratch and without impacting your existing users.
Uswitch.com transitioned from a traditional waterfall development process to agile practices like Scrum and XP over three years. While this improved speed, they still found planning overhead and low velocity. They then evolved to a fully lean approach, removing roles like QA and PM, limiting work-in-progress, releasing on demand, and building quality in rather than inspecting. This led to quicker time to market, reduced waste, safer and more frequent releases, and quality built-in rather than inspected. Measuring value is difficult but they focus on revenue, customer experience, innovation, and efficiency gains.
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
The PEX event discussed why BPM so often fails. This presentation reveals why that is so, and then demonstrates how, by following a well trodden path we can all get it right.
It is BPM Jim but not as we know it!
gineering teams. This workshop will cover everything you need to know to work seamlessly with engineering teams that use agile principles and practices.
What you will learn:
• Basics of the agile methods.
• Tips you can apply the very next day at work.
• Actionable tools and tactics to handle different product team scenarios that a product manager face.
Who is this workshop for:
• Software engineers who want to transition to Product Management
• MBAs with a finance/consulting background who want to work in high-tech companies as a Product Manager
• Project Managers, Marketers, Designers who are seeking for new opportunities in Product Management
The document discusses how to evolve corporate culture for long term success through continuous improvement. It advocates adopting systems to control products and equipment to achieve evolutionary benefits like lower costs and higher quality over time rather than periodic revolutionary changes. This approach leads to less variability, better process control, and business sustainability through changing cycles.
Always ready for release by Bogdan CosteaBosnia Agile
Agility is not about following a process, it's about delivering on expectations and that's way easier when you have a good release pipeline that automates as much of the process as possible.
Being able to release and deploy to production at any time doesn't imply that you're going to do it, it just means you are ready to do it at any time, and who doesn't want that right?
The talk goes through the evolution of release automation starting with automated builds, unit testing, CI, continuous delivery and continuous deployment with lots of examples and a couple of demos (a setup for a complex Java enterprise app and a simple ruby Sinatra web app).
Traversing hyper driven developpement to do great technical choices and make ...Quentin Adam
On this era of industrial changes, we all know that software is eating the world, and the world is small, or at least, not so big. So how to manage to make great technical choices on this era where giants apply the marketing of the Shame on us? How do we keep best developper in our organisation when it's a furious competition on hiring out there? More important, how do we make sure people we work with are both happy and productive? Beyond marketing, we will try to figure out how we do to compete and create value for us and our users.
HOW Design Conference 2010 Process Imporvementdbholston
HOW Design Conference 2010:Design Process Improvement Workshop
If you are interested in refining your design process, aligning your staff, and fixing your most frustrating problems, send me an email at dave@the-strategic-designer.com.
Kanban India 2023 | Sudipta Lahiri | Deliver MVV from your Kanban System.ppsm...LeanKanbanIndia
This document provides tips for delivering value from a Kanban system, beginning with the basics. It recommends using the STATIK method to structure the Kanban system and define the workflow. It suggests distinguishing between upstream and downstream work, with upstream focused on clarifying work and removing impediments. Tips include enforcing user work-in-progress limits to improve flow, monitoring card aging to address slippage, conducting meaningful retrospectives, and humanizing work by celebrating individuals and milestones. For software development teams, it recommends following INVEST principles for user stories, automating where possible, and stopping estimating in favor of prioritizing completed work. The overall message is to start with the basics of Kanban and focus on continuous improvement over
Jan de Vries - How to convince your boss that it is DevOps that he wantsAgile Lietuva
- We all know that we could implement DevOps a lot faster if we only would have commitment from our boss. We all know that there is a shiny business case for almost every DevOps implementation
- And we all know that the whole company will reap the benefits regarding speed, agility and stability once we implemented DevOps. Actually, it provides good, fast and cheap at the same time. So, what are we waiting for? What is your boss waiting for? What is C-level waiting for?
- That’s something we will do research on in this workshop. We will also share our research on this from the recent past.
- The workshop starts with a presentation about 7 practices that a company should adopt to be able to apply DevOps.
- The technique that we use is called Appreciative Inquiry. To tackle a problem, it discovers the best practices that work, the reason they work and how these combined practices can be used to avoid the problem ahead and create a strategic change. The aim is to build – or even rebuild – organizations around what works, rather than trying to fix what doesn’t.
- So we want to know what your boss is afraid of and what you have already tried to convince him that he is better off with DevOps. You will leave the workshop with the combined Appreciative Inquiry insights of all the attendees
The document discusses continuous integration and incremental development. It defines continuous integration as a pipeline with jobs that can run in parallel and produce artifacts that other jobs depend on. Incremental development involves implementing features in a way that maintains the integrity of the existing system and enables easy deployment. It is driven by requirements and tests, uses source control management, and aims for the system to be releasable at any time. Continuous integration helps achieve many of the goals of incremental development through automated testing, monitoring, and deployment pipelines.
Дмитро Бузоверя
Директор Cloud Computing департаменту в компанії AMC Bridge
Agile підхід до управління проектами існує вже більше 15 років, він досі є об’єктом багатьох дискусій та вважається інноваційним у деяких областях.
Дмитро Бузоверя, зробить огляд методології Agile у розробці програмного забезпечення. Він розкаже про історію Agile, його принципи та більш детально зупиниться на різних методиках: Extreme Programming (XP), Scrum, Lean та Kanban.
Ця лекція допоможе зібрати пазл з Agile термінології в єдину картинку.
Codemash 2.0.1.4: Tech Trends and Pwning Your Pwn CareerKevin Davis
The document discusses various tech trends including the future of C# programming language, Hadoop and big data solutions, JavaScript frameworks, software architecture principles, and work independence and remote work. The key points are that C# will continue to be supported and updated, Hadoop is useful for large data problems, JavaScript remains popular for client-side development, simplicity and iteration are important to architecture, and remote work is increasingly common and possible for tech careers.
✊ Join the DEV-olution: A culture of empowered developersSven Peters
Engineering leaders say their organizations struggle with productivity, collaboration, and tracking progress against goals. Some try to fix it by adding more dashboards, making strict rules, and asking for more reports. But just doing more doesn't solve the real issues developers face.
Let’s build a culture that empowers developers to do the right things and starts a dev-olution. Join Sven and hear how empowered teams build trustful relationships, work asynchronously and synchronously, use data smartly, care about outcomes, stay curious, and always try new things. More importantly, you will learn how to establish such a culture evolutionarily.
Empowering your engineers will amplify developer joy and supercharge your development effectiveness.
Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...Agile Montréal
Agile Project Management: From Agile Teams to Agile Organizations
We will present the tools and strategies for adopting agile project management practices that connect business, management and delivery teams. We propose a framework that maintains an executive focus on managing investment and risk, introduces enterprise-level agile product development lifecycle and separates project governance from operational delivery while loosely coupling these activities.
À propos de Steve Mercier
Steve est un professionnel du développement de produits logiciels, comptant plus de 20 ans d’expérience. Il a développé et mis en place des lignes de production logicielles assurant une meilleure efficacité de livraison, une adhésion croissante aux meilleures pratiques définies et une qualité accrue des produits entraînant la satisfaction des clients. Il applique les méthodes de travail Agile au quotidien depuis bientôt 10 ans. Il aime les défis techniques, apprécie être responsable de livrer, avec des gens de talents, en équipe, des produits qui comptent vraiment. Au fil des années il s'est spécialisé dans les champs suivants: Bonnes pratiques de développement de logiciel, Intégration et livraison continue, Lignes de production logicielles, Infrastructure gérée comme du code, Méthodes Agile et amélioration continue. Il oeuvre en ce moment comme gestionnaire d’une équipe de 15 DevOps bourrés de talent chez Lightspeed.
À propos de Jean-Paul Chauvet
President, Lightspeed
With over 20 years' experience as a marketing and sales executive in the technology sector, JP has been a key element in the continued growth of Lightspeed. By developing and leading Lightspeed's product strategy, go-to-market direction and taking a direct approach to engaging independent businesses, he has helped Lightspeed increase revenue, strengthen partner relations and achieve success month over month.
Kaizen refers to continuous improvement. It involves applying lean thinking principles like reducing waste, improving flow, and empowering employees. The goal is to continuously make small improvements to get closer to zero waste, defects, inventory, and process times. Establishing flow by removing bottlenecks and batch processing is important to improve efficiency, quality, lead times and employee morale. However, when processes include large, shared equipment, inventory may need to be reduced slowly to first address quality issues.
The document discusses continuous integration and incremental development. It defines continuous integration as a pipeline with jobs that can run in parallel and produce artifacts that other jobs depend on. Incremental development involves requirement-driven development, integrity of changes not harming other parts of the system, ability to deploy changes, isolation of changes, and being ready for release at any time. The document provides examples of tools that can be used for continuous integration, such as Jenkins, Travis CI, and Bamboo. It also discusses risks of relying on CI infrastructure and people not writing tests.
The document discusses deploying code changes quickly through continuous integration, delivery, and deployment practices. It advocates for having a single code repository ("one trunk"), automated builds and testing on every commit, deploying to staging frequently, and aiming to deploy changes within hours or less. This allows for early feedback, catching issues early, and responding quickly to change requests from customers through incremental and frequent deliveries.
The document discusses software craftsmanship and test-driven development (TDD). It notes that software craftsmanship is about raising the bar, taking pride in work, discipline, continuous learning, and deliberate practice. TDD's goal is to write clean code that works, following the Red-Green-Refactor mantra of writing a failing test, making it pass quickly, and refactoring code. The document promotes writing clean code because it is less expensive to maintain and leads to better programmers and productivity.
Why don't small companies do big a agile?activelylazy
Why don't small companies do big-A-Agile? Are they agile by default? Is Agile just a way for a large company to behave more like a small one? In this retrospective on agile adoption in companies large and small we'll look at what drives adoption, how effective it is at meeting those goals and whether software craftsmanship could teach us more.
Webinar: Demonstrating Business Value for DevOps & Continuous DeliveryXebiaLabs
The document discusses DevOps and continuous delivery. It begins with an introduction and agenda. It then discusses transforming IT operations for greater business value, challenges for businesses and IT that DevOps addresses, what DevOps is in terms of people, processes, and tools. It discusses continuous delivery and provides examples of goals and metrics for DevOps initiatives like release frequency, throughput time, and idle time. Finally, it discusses how DevOps tools can work with other tools and processes.
Finish Line Product Development Services offers product development services to help small companies reliably manufacture prototypes at a reasonable cost. They recommend: 1) conducting design verification testing with an independent engineering team to identify issues; 2) ensuring documentation is complete for manufacturing; and 3) doing field testing with customers to identify early issues that can be addressed before large-scale production. Finish Line has experience helping over 300 small companies through the prototype to production process.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
2. It’s a journey
“It isn’t the mountains ahead to climb that wear you out, it’s
the pebble in your shoe”- Muhammad Ali
3. Beware of the Blind spots
Most companies struggle to get to CD because they don’t take a holistic view of the
subject
DevOps “experts” and Delivery Managers are not talking the same lingo or have the
same set of priorities
amrish deshpande
4. Tools
Every chef needs right ingredients and tools before she starts cooking a new recipe
It’s one thing to have a desire to move to a fully mature CD model, it's quite another
thing to be ready for that.
So first right step is to take stock of your current tools used for Operations and
Release process. Don’t jump right into CD without accounting for tech-debt
Git, Ansible, Chef,Jenkins, Sonar, Selenium, TestNG, Gradle… are you there yet?
amrish deshpande
5. Test Pyramid
How big is your Automation footprint?
Automation is a big investment of time and resources
Remember : Automation is a necessary condition, but not a sufficient condition for
CD’s success
Make an honest assessment of your test suites across the board.
AND FIX IT FIRST!
amrish deshpande
6. Number of Steps to Production
The journey of a code change from developer’s desk to the Production server is a
long one. The length of this journey is crucial.
If your release process is over-engineered and top heavy, its a red-flag.
Write down all steps in the process. Make it transparent and visible to your
organization.
Which is the longest pole? In other words, what’s the biggest hump to cross before
code reaches production server? You have to shrink that step. And shrink it big
amrish deshpande
7. Code Review
Take a deep hard look at your Code Review process
Has it become a mere formality? Is it being done as one checkbox to cross-off?
Is it pragmatic and quick and not tied up into red-tape?
Fix it. Fix it now.
amrish deshpande
8. CI before CD
First ensure CI. Don’t jump to CD
Let CI bake-in with your organization’s overall roadmap
Agree to what’s the definition of “Done” in your story. But don’t ‘game it’
Are you there yet with frequent small batches of code mergers? Implement that first
amrish deshpande
9. Find those Unicorns
Check this video : https://www.youtube.com/watch?v=fW8amMCVAJQ
It's about “First Follower”
Identify those unicorns in your organization.
Back them and create a movement.
Help them turn the sail in direction of the wind.
It’s a leap of faith. People who don’t jump will be left behind.
amrish deshpande
10. Decentralize Quality Teams
Many organizations still have a central QE team that acts as a horizontal team
Thats a big No-No
Quality cannot be a bottleneck. Quality is individual team’s responsibility.
Small batches of code delivery, means less Quality overhead.
amrish deshpande
11. Work on getting a buy-in
Maybe this should come first. But it’s easier said than done.
Most folks across the technology and business will come on board slowly. Once they
start seeing results.
You cannot brute force your way to CD. You have to influence the change
Faster feedback loop is the single biggest advantage of CD.
Sell this in terms of Economics.
amrish deshpande
12. Culture
At the end it's a cultural shift, that does not happen overnight.
It has to be a combination of informal and formal conversations.
Make sure you have data points ready to produce when challenged.
Document wins. Document failures. Be honest.
Learn from missteps. Take small decisions. Take many decisions. Don’t go big bang.
This will take a while. Culture-shift happens at it’s own pace.
amrish deshpande
13. Summary
CD is a mindset and not a process itself. Like Agile.
There’s no silver bullet to “turn it ON”.
Prepare groundwork, make honest assessment of tools and process.
Automation is *a* necessary condition. But not *the* sufficient condition.
Identify Unicorns and build a movement
Get a buy-in from Stakeholders.
amrish deshpande