Death by Dogma versus Agile Assembly
•
3 likes•3,401 views
This is the slide deck I used for the keynote at the Agile Open Holland Conference 2011, held November 3 & 4 in Dieren. Using this slide deck I explain about being dogmatic and religious about agile approaches, and how a lot of the lightweight approaches are not sufficient as such for most larger, more complex or enterprise projects.
Report
Share
Report
Share
Recommended
Agile Adoption Patterns And Antipatterns
This document discusses patterns and anti-patterns for adopting agile practices. It will cover successful approaches like training, pilot projects, and working with experienced agile consultants. It also discusses key practices for a successful adoption as well as anti-patterns that should be avoided, such as practices that could undermine becoming an agile software development organization.
Agile Patterns and Anti-Patterns
The document discusses the principles behind the Agile Manifesto and provides examples of patterns and anti-patterns related to adopting Agile practices. It begins by listing the 12 principles from the Agile Manifesto, including delivering working software frequently and valuing customer collaboration over contract negotiation. The document then analyzes scenarios to determine whether team decisions align with or contradict Agile principles, and suggests more aligned approaches when needed.
Agile Anti-Patterns. Yes your agile projects can and will fail too.
The document discusses various anti-patterns that can cause agile projects to fail. It notes that while many believe waterfall methods don't work, agile projects can fail too if not implemented properly. Some specific anti-patterns mentioned include blaming the methodology instead of the implementation, overreliance on documentation or rituals over outcomes, and treating agile as a one-size-fits-all approach. The document advocates for tailoring agile approaches to individual project and organization needs.
Introduction to Agile for Digital Stakeholders
The document provides an introduction to agile methodology. It discusses some of the key principles of agile, including welcoming change, reducing risk, and delivering value incrementally. It also compares agile to traditional waterfall methodology, noting that agile works through constant replanning and slicing work into small achievable pieces. The document suggests taking a pragmatic approach to planning by only planning for the immediate future and making decisions based on current information.
[XP Day Vietnam 2015] XP is not windows XP
This document discusses eXtreme Programming (XP), an agile software development framework. It provides definitions and explanations of key XP practices, principles, and values. The main points are:
- XP focuses on practices like pair programming, testing, code reviews, and frequent integration that are taken "to the extreme."
- The core values of XP center on individuals, interactions, working software, customer collaboration, and responding to change.
- Key practices include sit together pairing, testing, informative workspaces, user stories, test-driven development, and more.
- Principles guide the framework and include ideas like baby steps, mutual benefit, flow, reflection, and redundancy.
How to Rescue Complex Projects from Disaster
Work on big projects or product development efforts?
Then you’re familiar with that feeling — that things may get messy, disorderly, out of control, turned upside down.
It’s a terrible feeling!
Good news: There are proven ways to prevent project chaos from occurring.
With this webinar, we’ll show you:
-A framework for re-orienting your project & team toward proper planning.
-Critical differences between “complex” & “complicated” projects.
-How to set high-level project structure correctly.
-Common mistakes to avoid.
-Planning approaches that’ll get you to the finish line.
Pair Programming, TDD and other impractical things
"Why should we write our tests first? Isn't that going to slow my development?" "What? Assigning a single task to 2 developers? How is that efficient? What a waste of resources!" "Look, in the perfect world your advises are great, but I have a project to finish here." In this talk Marcello explores efficiency in contrast to effectiveness. He looks into how practices, traditionally accepted as efficient, sometimes turn out to be less effective than a few "impractical" things he has come across.
Managing projects using distributed teams with agile scrum
The document discusses managing distributed scrum projects. It outlines challenges with distributed scrum including communication issues due to different time zones and languages. It then reviews scrum basics like roles of product owner, scrum master, and development team. The document discusses agile principles and factors like continuous delivery. It also provides best practices for distributed scrum projects such as standard meetings, continuous integration, and no distinction between developers at different sites.
Recommended
Agile Adoption Patterns And Antipatterns
This document discusses patterns and anti-patterns for adopting agile practices. It will cover successful approaches like training, pilot projects, and working with experienced agile consultants. It also discusses key practices for a successful adoption as well as anti-patterns that should be avoided, such as practices that could undermine becoming an agile software development organization.
Agile Patterns and Anti-Patterns
The document discusses the principles behind the Agile Manifesto and provides examples of patterns and anti-patterns related to adopting Agile practices. It begins by listing the 12 principles from the Agile Manifesto, including delivering working software frequently and valuing customer collaboration over contract negotiation. The document then analyzes scenarios to determine whether team decisions align with or contradict Agile principles, and suggests more aligned approaches when needed.
Agile Anti-Patterns. Yes your agile projects can and will fail too.
The document discusses various anti-patterns that can cause agile projects to fail. It notes that while many believe waterfall methods don't work, agile projects can fail too if not implemented properly. Some specific anti-patterns mentioned include blaming the methodology instead of the implementation, overreliance on documentation or rituals over outcomes, and treating agile as a one-size-fits-all approach. The document advocates for tailoring agile approaches to individual project and organization needs.
Introduction to Agile for Digital Stakeholders
The document provides an introduction to agile methodology. It discusses some of the key principles of agile, including welcoming change, reducing risk, and delivering value incrementally. It also compares agile to traditional waterfall methodology, noting that agile works through constant replanning and slicing work into small achievable pieces. The document suggests taking a pragmatic approach to planning by only planning for the immediate future and making decisions based on current information.
[XP Day Vietnam 2015] XP is not windows XP
This document discusses eXtreme Programming (XP), an agile software development framework. It provides definitions and explanations of key XP practices, principles, and values. The main points are:
- XP focuses on practices like pair programming, testing, code reviews, and frequent integration that are taken "to the extreme."
- The core values of XP center on individuals, interactions, working software, customer collaboration, and responding to change.
- Key practices include sit together pairing, testing, informative workspaces, user stories, test-driven development, and more.
- Principles guide the framework and include ideas like baby steps, mutual benefit, flow, reflection, and redundancy.
How to Rescue Complex Projects from Disaster
Work on big projects or product development efforts?
Then you’re familiar with that feeling — that things may get messy, disorderly, out of control, turned upside down.
It’s a terrible feeling!
Good news: There are proven ways to prevent project chaos from occurring.
With this webinar, we’ll show you:
-A framework for re-orienting your project & team toward proper planning.
-Critical differences between “complex” & “complicated” projects.
-How to set high-level project structure correctly.
-Common mistakes to avoid.
-Planning approaches that’ll get you to the finish line.
Pair Programming, TDD and other impractical things
"Why should we write our tests first? Isn't that going to slow my development?" "What? Assigning a single task to 2 developers? How is that efficient? What a waste of resources!" "Look, in the perfect world your advises are great, but I have a project to finish here." In this talk Marcello explores efficiency in contrast to effectiveness. He looks into how practices, traditionally accepted as efficient, sometimes turn out to be less effective than a few "impractical" things he has come across.
Managing projects using distributed teams with agile scrum
The document discusses managing distributed scrum projects. It outlines challenges with distributed scrum including communication issues due to different time zones and languages. It then reviews scrum basics like roles of product owner, scrum master, and development team. The document discusses agile principles and factors like continuous delivery. It also provides best practices for distributed scrum projects such as standard meetings, continuous integration, and no distinction between developers at different sites.
Agile Is A Four-Letter Word (Jen Krieger)
Based on a wide variety of surveys taken over recent years, many companies are transitioning to something that looks more like Agile than the processes they were using in previous years. However, that transition doesn’t necessarily mean implementations have been done respectfully of the Agile Manifesto and the principles behind it. In large part, industry trends seem to indicate that the sloganization of the word has done a significant disservice to the ideas that were originally founded in 2001. To add even more pain, most people seem to be entirely unaware of the core basis of Agile which is the idea to embrace change but inspect and adapt to that change. Are we lost as an industry? Is there anyway we can recover from this problem? In this session, attendees can expect to engage in a conversation about the rise of the Agile community, the negative and positive impact it has had on the industry, and how you individually can help your organizations and teams lower the risk of encountering the negative problems, and speed your way towards the positives. Topics will include: - The intentions behind agile - Ways you can rework or improve your not so great agile situation - Things you should avoid from the start.
Want better estimation ?
The document discusses estimation techniques. It presents five estimation laws: 1) Don't estimate if you can measure, 2) compare instead of estimating units, 3) measure things that are measurable, 4) reduce precision of estimates based on knowledge, and 5) use different metrics for different estimates. Good practices discussed include using story sizing for requirements, measuring in hours for small tasks, using velocity, splitting large stories, and measuring fixed cycle times. The document provides resources for further learning about agile estimation techniques.
Stepping Outside
This document discusses techniques for improving software testing processes. It advocates for automating testing to make it faster, cheaper, and more accurate than manual testing. It also discusses experimenting with different approaches to task assignment, including assigning the least qualified person to a task. This counterintuitive strategy was found to increase overall team velocity the most over several iterations, as it promotes learning. The document emphasizes using metrics to evaluate different process experiments and adopting the approaches that work best.
Black Belt Tips for JIRA Software
JIRA Software is an extremely flexible and powerful tool, which can be used in a variety of ways. As a 9-year Atlassian veteran, Nick Pellow will outline the innovative ways JIRA Software is being used within Atlassian, and what features our teams find most useful to enhance their processes.
I'll cover practical tips, such as how we run Scrum and Kanban, and how we've customized projects and boards to best plan, track, and ship software with the precision of a black-belt judo master.
Nick Pellow, Development Manager JIRA Software, Atlassian
Agile development makes elephants dance
This document discusses agile development and how it can help address issues with traditional waterfall development approaches. It provides an overview of agile principles from the Agile Manifesto, popular agile methodologies like Scrum and XP, and how agile practices emphasize iterative development, emergent requirements, frequent inspection/adaptation, and valuing individuals/interaction over processes. A real example is given of how adopting scrum helped turn around a failing project that was over budget and delivering poor quality.
Lean and Continuous delivery
The document discusses lean software development principles for achieving continuous delivery, including eliminating waste, amplifying learning, deciding late, delivering fast, empowering teams, building integrity, and seeing the whole process. It provides examples of how following these principles can reduce wait times, unnecessary processes, and bugs by making decisions quickly with the whole team and delivering changes more rapidly based on feedback. The overall message is that lean principles can help teams optimize their processes for continuous delivery.
Are you being the right ScrumMaster?
The document provides guidance for Scrum Masters on properly fulfilling their role. It defines the Scrum Master's key responsibilities as removing impediments, serving the Product Owner and team, and facilitating collaboration. The Scrum Master should represent the team to management and management to the team. They should coach the team and protect it, listening more than directing. Several case studies are presented that illustrate how a Scrum Master can address common team issues like inefficient work, unproductive meetings, and unclear requirements. The document concludes with recommendations for Scrum Masters to ask questions rather than dictate solutions, identify root causes, use data to help teams improve, and build strong relationships with managers.
Digitial school Atlanta -Agile-marketing
The document discusses implementing an agile marketing plan for 2015. It advocates adopting agile principles like prioritization, transparency, empowerment and experimentation to increase adaptability, productivity and the ability to incorporate feedback. Marketing used to rely on annual waterfall plans but is now complex and fast-paced, requiring an iterative approach of many small sprints instead of one large project. This allows for adjustments based on learning and feedback between deliverables.
Richmond Spin - How To Sell A Traditional Client
After an introduction to the basic tenets of Agile and some Agile practices, this presentation to Richmond SPIN (Software Process Improvement Network) talks about ways to convince your organization or clients to use Agile software development practices. Based on a presentation given at Agile 2009 by Arin Sime, Senior Consultant with OpenSource Connections.
Scrum Master Lessons from my 4 Year Old Son
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
Digibury: Steve Coppin-Smith, Deeson scrum for agencies
Deeson Solutions Architect Steve Coppin-Smith focuses on scrum in an agency environment. In his talk he explaines what scrum is, why is it relevant to web development, and how can it help coders.
Agile is Dead :: Pixels Camp 2017
This document discusses how Agile has become outdated or "dead" due to misinterpretations and misapplications over time. The author argues that many companies claim to be Agile but are actually focused on processes and tools rather than outcomes. True Agility values individuals, interactions, working software, and responding to change. The author suggests companies need to refocus on delivering value to customers rather than following rigid practices. Overall, the document criticizes a "cargo cult" mentality around Agile and advocates returning to its original principles of empowering individuals, collaboration, and continuous improvement.
Resolve Incidents Faster: Transforming Your Incident Management Process
Incident response teams are evolving, thanks to DevOps, agile, and today’s demand for always-on services. But, what’s the best way to respond when you’re faced with a complex mix of systems, software, and teams? Is there a way to respond faster, collaborate better, and continuously improve your incident management process?
Join Simon Kubica, Product Manager for Opsgenie, as he uncovers best practices that’ll streamline every stage of your response effort. See how Atlassian, Amazon and Google enable collaboration between support, operations and development, and learn how to leverage automation and conduct effective postmortems. Plus, Simon will show live demos on how you can implement these tips in Opsgenie, Statuspage, and Jira Service Desk.
Henrik Kniberg - Essence of Agile
This document provides an overview of agile principles and practices such as Scrum, XP, Kanban, and the Agile Manifesto. It discusses key concepts like iterative development, self-organizing teams, frequent delivery of working software, and responding to change over following a plan. Visualizations are used to illustrate differences between the traditional predictive approach and agile approaches to managing scope, quality, costs and time.
How to Build a Healthy On-Call Culture
Raise your hand if you enjoy being buried in alerts or woken up at 2am? (Yeah... thought so.) Ever-rising customer expectations around high availability and performance put massive pressure on the teams who develop and support SaaS products. And teams are literally losing sleep over it.
Until outages and other incidents are a thing of the past, organizations need to invest in a way of dealing with them that won't lead to burn-out. In this session, you'll learn how to combine the latest tooling with DevOps practices in the pursuit of a sustainable incident response workflow. It's all about transparency, actionable alerts, resilience, and learning from each incident.
你真的搞懂了甚麼叫敏捷式開發?
This document discusses agile development and provides an introduction to key concepts. It begins by explaining common problems that agile aims to address such as unclear requirements, long tasks, lack of quality time, and lack of visibility. It then introduces agile methods like Scrum, XP, and Kanban. The document discusses how agile solves the earlier problems through practices like iterative development, frequent feedback, automation, and visibility tools. It addresses some myths about agile and emphasizes that agile is not a silver bullet and requires the right environment and culture.
Intro to Agile Practices and Values
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
Henrik Kniberg: Lean from the Trenches keynote @ AgileEE
This document summarizes a presentation about applying lean and agile principles to a large government project in Sweden called PUST. It describes how the project team used techniques like slicing work into small customer-focused stories, daily stand-ups, iterative planning and releases, continuous improvement retrospectives, and tracking metrics to successfully deliver the project on time and on budget while continuously improving their process.
Agile Myths and Legends
Have you heard any of these statements? “As a manager I will have no control or visibility into my team’s activities with Agile!” “Agile practices are unstructured, everyone is a cowboy!” “An agile development team doesn’t work from requirements, and testing goes out the window!” and my personal favorite - “Agile means no documentation!” Ahhhhhhhhh, no wonder Agile is a scary word for managers and testers. If any of the above statements are true in your organization, then someone is doing it wrong. I am here to tell you from personal experience at a number of clients, both large and small, that none of these claims are true if you are truly following the tenets of Agile. Actually, these statements reflect a situation that is really the OPPOSITE of what can happen on a mature, well-functioning agile team. In this presentation, we will discuss what Agile really IS, and debunk some of the popular myths that make organizations hesitate from adopting Agile into their organization.
The Agile Hammer
The document summarizes the author's experience with adopting Agile practices within her team. Initially, the team struggled with a partially ad-hoc Agile implementation that resulted in slow, poor quality work and budget overruns. Over time, as the team recomposed their practices to more closely align with Agile principles such as short stand-up meetings, estimating in story points, and continuous flow, they saw improvements in quality, time to market, and flexibility. Business stakeholders also reported benefits like increased visibility into work being done and opportunities to provide feedback. The author concludes by reflecting on further refinements to Agile practices in her current role, supported by a dedicated Agile center of excellence, external coaching, and executive sponsorship.
Persuasion in Design
This document discusses principles of persuasion and their application to design. It begins with an agenda that covers introduction, principles of persuasion, decision making, and examples. It then discusses six universal principles of social influence including reciprocation, authority, commitment, scarcity, liking, and social proof. The document also examines how emotions and rationality both shape decision making. It notes that users have limited attention and are paralyzed by too many choices. Finally, it provides examples of how persuasive design can be applied to online ordering and selling wine online.
Sweeping out the cobwebs: Content auditing for large websites
Large websites tend, over time, to develop gluts of out of date content and dark unvisited corners. Thanks to devolved publishing, whole sections of a site can spring up without proper planning or coordination, only to be left in place long after they have served their purpose. Using spidering technology, Justin will demonstrate techniques to get a grasp of the size and shape of your site and to begin the process of decluttering.
More Related Content
What's hot
Agile Is A Four-Letter Word (Jen Krieger)
Based on a wide variety of surveys taken over recent years, many companies are transitioning to something that looks more like Agile than the processes they were using in previous years. However, that transition doesn’t necessarily mean implementations have been done respectfully of the Agile Manifesto and the principles behind it. In large part, industry trends seem to indicate that the sloganization of the word has done a significant disservice to the ideas that were originally founded in 2001. To add even more pain, most people seem to be entirely unaware of the core basis of Agile which is the idea to embrace change but inspect and adapt to that change. Are we lost as an industry? Is there anyway we can recover from this problem? In this session, attendees can expect to engage in a conversation about the rise of the Agile community, the negative and positive impact it has had on the industry, and how you individually can help your organizations and teams lower the risk of encountering the negative problems, and speed your way towards the positives. Topics will include: - The intentions behind agile - Ways you can rework or improve your not so great agile situation - Things you should avoid from the start.
Want better estimation ?
The document discusses estimation techniques. It presents five estimation laws: 1) Don't estimate if you can measure, 2) compare instead of estimating units, 3) measure things that are measurable, 4) reduce precision of estimates based on knowledge, and 5) use different metrics for different estimates. Good practices discussed include using story sizing for requirements, measuring in hours for small tasks, using velocity, splitting large stories, and measuring fixed cycle times. The document provides resources for further learning about agile estimation techniques.
Stepping Outside
This document discusses techniques for improving software testing processes. It advocates for automating testing to make it faster, cheaper, and more accurate than manual testing. It also discusses experimenting with different approaches to task assignment, including assigning the least qualified person to a task. This counterintuitive strategy was found to increase overall team velocity the most over several iterations, as it promotes learning. The document emphasizes using metrics to evaluate different process experiments and adopting the approaches that work best.
Black Belt Tips for JIRA Software
JIRA Software is an extremely flexible and powerful tool, which can be used in a variety of ways. As a 9-year Atlassian veteran, Nick Pellow will outline the innovative ways JIRA Software is being used within Atlassian, and what features our teams find most useful to enhance their processes.
I'll cover practical tips, such as how we run Scrum and Kanban, and how we've customized projects and boards to best plan, track, and ship software with the precision of a black-belt judo master.
Nick Pellow, Development Manager JIRA Software, Atlassian
Agile development makes elephants dance
This document discusses agile development and how it can help address issues with traditional waterfall development approaches. It provides an overview of agile principles from the Agile Manifesto, popular agile methodologies like Scrum and XP, and how agile practices emphasize iterative development, emergent requirements, frequent inspection/adaptation, and valuing individuals/interaction over processes. A real example is given of how adopting scrum helped turn around a failing project that was over budget and delivering poor quality.
Lean and Continuous delivery
The document discusses lean software development principles for achieving continuous delivery, including eliminating waste, amplifying learning, deciding late, delivering fast, empowering teams, building integrity, and seeing the whole process. It provides examples of how following these principles can reduce wait times, unnecessary processes, and bugs by making decisions quickly with the whole team and delivering changes more rapidly based on feedback. The overall message is that lean principles can help teams optimize their processes for continuous delivery.
Are you being the right ScrumMaster?
The document provides guidance for Scrum Masters on properly fulfilling their role. It defines the Scrum Master's key responsibilities as removing impediments, serving the Product Owner and team, and facilitating collaboration. The Scrum Master should represent the team to management and management to the team. They should coach the team and protect it, listening more than directing. Several case studies are presented that illustrate how a Scrum Master can address common team issues like inefficient work, unproductive meetings, and unclear requirements. The document concludes with recommendations for Scrum Masters to ask questions rather than dictate solutions, identify root causes, use data to help teams improve, and build strong relationships with managers.
Digitial school Atlanta -Agile-marketing
The document discusses implementing an agile marketing plan for 2015. It advocates adopting agile principles like prioritization, transparency, empowerment and experimentation to increase adaptability, productivity and the ability to incorporate feedback. Marketing used to rely on annual waterfall plans but is now complex and fast-paced, requiring an iterative approach of many small sprints instead of one large project. This allows for adjustments based on learning and feedback between deliverables.
Richmond Spin - How To Sell A Traditional Client
After an introduction to the basic tenets of Agile and some Agile practices, this presentation to Richmond SPIN (Software Process Improvement Network) talks about ways to convince your organization or clients to use Agile software development practices. Based on a presentation given at Agile 2009 by Arin Sime, Senior Consultant with OpenSource Connections.
Scrum Master Lessons from my 4 Year Old Son
At a recent cookout, my 4 year old son, Dawson, ran for the back yard and easily joined a game of hide and seek. Watching this unfold, I realized that these kids are naturally agile. They got straight to playing (the value) and didn’t need a lot of ceremony to get there. They kids all did a quick hello, told Dawson what game they were playing, and invited him to join in (daily scrum). Then they played.
He and his friends self-organize, self-manage, and solve problems on the fly. They naturally exhibit the agile values and scrum practices that many adults struggle with daily.
For example, most parents have been bombarded with an unending stream of “Why’s?” from their child. Why does this work? Why did that happen? Why? Why? Why? While this line of questioning can be stressing, it is also invaluable to finding the root cause of an issue. Scrum teams use this approach – called The 5-Why’s – to get past technical issues and down to interpersonal issues that could be hindering the team.
This session is a fun discussion about the behaviors I’ve noticed in my son and how they translate to important lessons that all scrum master need to learn to better serve their teams.
Digibury: Steve Coppin-Smith, Deeson scrum for agencies
Deeson Solutions Architect Steve Coppin-Smith focuses on scrum in an agency environment. In his talk he explaines what scrum is, why is it relevant to web development, and how can it help coders.
Agile is Dead :: Pixels Camp 2017
This document discusses how Agile has become outdated or "dead" due to misinterpretations and misapplications over time. The author argues that many companies claim to be Agile but are actually focused on processes and tools rather than outcomes. True Agility values individuals, interactions, working software, and responding to change. The author suggests companies need to refocus on delivering value to customers rather than following rigid practices. Overall, the document criticizes a "cargo cult" mentality around Agile and advocates returning to its original principles of empowering individuals, collaboration, and continuous improvement.
Resolve Incidents Faster: Transforming Your Incident Management Process
Incident response teams are evolving, thanks to DevOps, agile, and today’s demand for always-on services. But, what’s the best way to respond when you’re faced with a complex mix of systems, software, and teams? Is there a way to respond faster, collaborate better, and continuously improve your incident management process?
Join Simon Kubica, Product Manager for Opsgenie, as he uncovers best practices that’ll streamline every stage of your response effort. See how Atlassian, Amazon and Google enable collaboration between support, operations and development, and learn how to leverage automation and conduct effective postmortems. Plus, Simon will show live demos on how you can implement these tips in Opsgenie, Statuspage, and Jira Service Desk.
Henrik Kniberg - Essence of Agile
This document provides an overview of agile principles and practices such as Scrum, XP, Kanban, and the Agile Manifesto. It discusses key concepts like iterative development, self-organizing teams, frequent delivery of working software, and responding to change over following a plan. Visualizations are used to illustrate differences between the traditional predictive approach and agile approaches to managing scope, quality, costs and time.
How to Build a Healthy On-Call Culture
Raise your hand if you enjoy being buried in alerts or woken up at 2am? (Yeah... thought so.) Ever-rising customer expectations around high availability and performance put massive pressure on the teams who develop and support SaaS products. And teams are literally losing sleep over it.
Until outages and other incidents are a thing of the past, organizations need to invest in a way of dealing with them that won't lead to burn-out. In this session, you'll learn how to combine the latest tooling with DevOps practices in the pursuit of a sustainable incident response workflow. It's all about transparency, actionable alerts, resilience, and learning from each incident.
你真的搞懂了甚麼叫敏捷式開發?
This document discusses agile development and provides an introduction to key concepts. It begins by explaining common problems that agile aims to address such as unclear requirements, long tasks, lack of quality time, and lack of visibility. It then introduces agile methods like Scrum, XP, and Kanban. The document discusses how agile solves the earlier problems through practices like iterative development, frequent feedback, automation, and visibility tools. It addresses some myths about agile and emphasizes that agile is not a silver bullet and requires the right environment and culture.
Intro to Agile Practices and Values
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
Henrik Kniberg: Lean from the Trenches keynote @ AgileEE
This document summarizes a presentation about applying lean and agile principles to a large government project in Sweden called PUST. It describes how the project team used techniques like slicing work into small customer-focused stories, daily stand-ups, iterative planning and releases, continuous improvement retrospectives, and tracking metrics to successfully deliver the project on time and on budget while continuously improving their process.
Agile Myths and Legends
Have you heard any of these statements? “As a manager I will have no control or visibility into my team’s activities with Agile!” “Agile practices are unstructured, everyone is a cowboy!” “An agile development team doesn’t work from requirements, and testing goes out the window!” and my personal favorite - “Agile means no documentation!” Ahhhhhhhhh, no wonder Agile is a scary word for managers and testers. If any of the above statements are true in your organization, then someone is doing it wrong. I am here to tell you from personal experience at a number of clients, both large and small, that none of these claims are true if you are truly following the tenets of Agile. Actually, these statements reflect a situation that is really the OPPOSITE of what can happen on a mature, well-functioning agile team. In this presentation, we will discuss what Agile really IS, and debunk some of the popular myths that make organizations hesitate from adopting Agile into their organization.
The Agile Hammer
The document summarizes the author's experience with adopting Agile practices within her team. Initially, the team struggled with a partially ad-hoc Agile implementation that resulted in slow, poor quality work and budget overruns. Over time, as the team recomposed their practices to more closely align with Agile principles such as short stand-up meetings, estimating in story points, and continuous flow, they saw improvements in quality, time to market, and flexibility. Business stakeholders also reported benefits like increased visibility into work being done and opportunities to provide feedback. The author concludes by reflecting on further refinements to Agile practices in her current role, supported by a dedicated Agile center of excellence, external coaching, and executive sponsorship.
What's hot (20)
Digibury: Steve Coppin-Smith, Deeson scrum for agencies
Digibury: Steve Coppin-Smith, Deeson scrum for agencies
Resolve Incidents Faster: Transforming Your Incident Management Process
Resolve Incidents Faster: Transforming Your Incident Management Process
Henrik Kniberg: Lean from the Trenches keynote @ AgileEE
Henrik Kniberg: Lean from the Trenches keynote @ AgileEE
Viewers also liked
Persuasion in Design
This document discusses principles of persuasion and their application to design. It begins with an agenda that covers introduction, principles of persuasion, decision making, and examples. It then discusses six universal principles of social influence including reciprocation, authority, commitment, scarcity, liking, and social proof. The document also examines how emotions and rationality both shape decision making. It notes that users have limited attention and are paralyzed by too many choices. Finally, it provides examples of how persuasive design can be applied to online ordering and selling wine online.
Sweeping out the cobwebs: Content auditing for large websites
Large websites tend, over time, to develop gluts of out of date content and dark unvisited corners. Thanks to devolved publishing, whole sections of a site can spring up without proper planning or coordination, only to be left in place long after they have served their purpose. Using spidering technology, Justin will demonstrate techniques to get a grasp of the size and shape of your site and to begin the process of decluttering.
HOW BS8878 - THE UK WEB ACCESSIBILITY STANDARDS - BRING TOGETHER ACCESSIBILIT...
The document discusses how BS 8878 helps organizations embed accessibility and digital inclusion. It presents the business case for accessibility and provides guidance on how to strategically embed accessibility within an organization. It outlines a process for identifying key decisions that impact accessibility throughout a web product's lifecycle and recommends documenting these decisions to ensure best practices. The standard helps organizations consider inclusive design, target audiences, delivery platforms, and assurance testing to launch products that meet accessibility needs.
Why Blind Users love iOS
This document discusses why blind users love iOS devices. It includes a video presentation by Robin Christopherson of AbilityNet at the launch of the Technology4Good Awards showing the accessibility of iOS. It also features a demo of the Zoom feature on iOS, a video of deaf users Facetiming each other in an Apple store, and a clip showing how an iOS device can be operated using a single switch to help those with autism or other disabilities who have difficulty speaking. The document encourages nominating technologies that help people at www.technology4goodawards.org.uk for the Technology4Good Awards.
EYE TRACKING AND BIO-METRICS TO ENHANCE USER RESEARCH
This document discusses various biometric and physiological measurement techniques that can provide hidden insights into users, including eye tracking, biometrics, electroencephalography (EEG), emotion recognition software, and measures of heart rate, galvanic skin response, respiration, and electromyography. It notes that these techniques aim to optimize user experiences and interactions while providing commercial advantages by unlocking insights from both conscious and subconscious human responses and behaviors. The document raises the question of which, if any, of these techniques should be used to test user experiences and considers what could potentially go wrong when applying these methods.
Running a Masters level study in MMU's UX lab
This document discusses a Masters level study conducted at the MMU Usability Lab on developing a methodology for measuring intention on mobile devices. The study was supervised by David Edmundson-Bird and involved working with a mobile marketing professional, Paul McManus, from Win Technologies. Paul acted as a consultant on the project to understand the experience of creating a methodology. He developed an understanding of the lab's equipment and tools. His initial results showed limitations with the mobile eye-tracking software and calibration. Reflections on supervising a professional consultant compared to a student were discussed, as was the challenges remaining in measuring intention on mobile and limitations of current technology.
BBC IPLAYER FOR TV: PUTTING IPLAYER WHERE IT BELONGS
This document discusses designing the BBC iPlayer experience for television. It notes that television is different than computers due to factors like being viewed from farther away on bigger screens, having limited remote control buttons, and variations in display qualities across devices. The author details challenges in areas like fonts, gradients, safe zones for text, and transitions. It advocates testing designs with real users and devices to account for the diversity of technologies people use to access television content. Examples are given of adapting iPlayer for platforms like Xbox to provide positive user experiences on new devices.
Applying 'Persuasion, Emotion and Trust' PET Design Theory in the Real World
Usability is great but in an age where alternative options are only a click away is it enough? From the outside, you may have designed a shop window to display your products or services in the best possible light but what makes people take that critical step and commit to a purchase? Chris will cover the principles of Persuasion Design, or “Persuasion, Emotion and Trust” as Human Factors International defines PET Theory. They will present some real world examples of how companies are getting it right, and wrong in eCommerce.
GET IN TOUCH WITH SIGMA
This presentation is from Camp Digital, a free, one-day event in Manchester exploring some of the most important and emerging themes in the digital industry. To see more presentations and videos from the day visit: http://campdigital.wearesigma.com/2013/.
Camp Digital was brought to you by Sigma. We are a leading specialist in User Experience consulting and design, information management, and web technologies. We provide research, analysis, design, development and support services, with specific expertise in usability, accessibility, content and document management, websites, intranets and online applications.
If you think we can help you call us on 01625 427718 or email hello@wearesigma.com.
How BS8878 brings together usability & accessibility
Accessibility is all about checklists, HTML and assistive technologies. Its only impact on User Experience is to stop designers from being creative.
Sometimes, you'd be forgiven for thinking that those two statements are true.
Professor Jonathan Hassell has spent much of his last three years disproving them, both at the BBC and in other organisations, and coding how accessibility should be seen in the context of user-centred design into BS 8878.
In this presentation from Camp Digital Manchester 2012 he shows how BS 8878 provides a framework for helping UX professionals embed accessibility considerations into their work, how it can empower and free them from onerous constraints, how it can challenge them to be more creative, and how the results can benefit all users, not just those with disabilities.
Viewers also liked (9)
Sweeping out the cobwebs: Content auditing for large websites
Sweeping out the cobwebs: Content auditing for large websites
HOW BS8878 - THE UK WEB ACCESSIBILITY STANDARDS - BRING TOGETHER ACCESSIBILIT...
HOW BS8878 - THE UK WEB ACCESSIBILITY STANDARDS - BRING TOGETHER ACCESSIBILIT...
EYE TRACKING AND BIO-METRICS TO ENHANCE USER RESEARCH
EYE TRACKING AND BIO-METRICS TO ENHANCE USER RESEARCH
BBC IPLAYER FOR TV: PUTTING IPLAYER WHERE IT BELONGS
BBC IPLAYER FOR TV: PUTTING IPLAYER WHERE IT BELONGS
Applying 'Persuasion, Emotion and Trust' PET Design Theory in the Real World
Applying 'Persuasion, Emotion and Trust' PET Design Theory in the Real World
How BS8878 brings together usability & accessibility
How BS8878 brings together usability & accessibility
Similar to Death by Dogma versus Agile Assembly
Chasingwindmills agile success
This document discusses how government organizations can achieve success using Agile methods. It notes that 78% of businesses feel requirements are out of sync with projects and only 20% of application features are used. Agile values individuals, working software, customer collaboration and responding to change over processes, documentation, contract negotiation and following a plan. The document outlines challenges governments face with bureaucracy, policies and complexity and suggests decomplicating processes and applying the "pants principle" of simple team-driven processes. It proposes adapting the "Iron Triangle" to prioritize epics and executing projects in small slices using a Scrum-based Earned Value Management approach.
Scrum
The document discusses the key aspects of implementing Scrum at Paylogic. It describes why Scrum works through better control, incremental delivery of business value, and empowering self-managed teams. It outlines the Scrum process, including artifacts like the product and sprint backlogs, daily standups, sprints, and retrospectives. It defines the roles of product owner and Scrum master. Sprints are proposed to last 1 week to provide fine-grained control and ensure quality through frequent deliveries. The first sprints would focus on core features and getting initial feedback to adjust subsequent sprints.
The Lean Company @ Moonpig.com
Slides for 1-day training course: "Introduction to Lean and Agile for managers and stakeholders at Moonpig.com"
The Agile PMP - Pillar Technology
The document discusses how Agile project management differs from traditional project management. It explains that Agile uses iterative planning with short timeboxes, focuses on delivering working software frequently in small batches, emphasizes individuals/interactions over processes/tools, and values customer collaboration over contract negotiation. The document outlines how Agile manages scope, time, costs, risks, and other factors using techniques like user stories, burndown charts, and frequent inspection and adaptation. It encourages the reader to start implementing Agile practices like iterative planning and daily stand-ups.
Agile?! Are You Crazy???
Presentation to Lonetree PMI Roundtable on August 27, 2008.
Abstract:
According to the Wall Street Journal agile development has "crossed the chasm." Why then are there still strong pockets of intense resistance to agile? This presentation takes a look at some of the most common misconceptions about agile development. It exposes the truth behind the myths and backs up many of the points with actual industry data. In the process, a basic business case for agility is created. The goal of this session is for all participants to leave with the knowledge necessary to answer the question "Why Agile?" In addition, participants will gain a deeper understanding of the realities of agile development and how it can help organizations.
Agile is Dead :: Aginext London 2018
This document discusses how Agile has become dead due to common misinterpretations and misapplications of its principles. While Agile and Scrum were developed decades ago, many companies have lost sight of their original purpose to deliver early value to customers. Agile is often mistakenly equated with Scrum processes and tools rather than seen as a mindset. As a result, developers, customers, and stakeholders are unhappy and value is not being delivered. The document argues that for Agile to be revived, its focus must shift back to principles of individuals, interactions, and responding to change over rigid processes and metrics.
Software and all that comes with it
Developing a software project is definitely not like building a house. If you focus on the learning aspects instead of the simple building you'll probably discover something interesting and unexpected.
Arch factory - Agile Design: Best Practices
This document provides guidance on agile architecture and design principles. It emphasizes that agile design is about responding quickly to change for customers and teams through transparency, lightweight processes, and continuous learning. Key principles discussed include designing incrementally without large upfront design; getting early and continuous feedback; delaying commitment and complexity; and maximizing evolutionary design through reversibility and packaging. The document also covers topics like testing, distributed teams, and delivering frequently.
Validation Missteps Making Us Full Time Firefighters
1) The document discusses common missteps that can turn product development teams into "firefighters", such as insufficient planning, not designing for testability, lacking feedback loops, and a lack of transparency.
2) It recommends planning testing in writing, designing products to be testable, creating adaptable feedback loops between teams, and fostering transparency to avoid surprises.
3) Following these practices can help teams avoid becoming "full time firefighters" scrambling to put out fires as deadlines approach by better anticipating and addressing issues earlier.
Agile tour 2011 ralph jocham - scrum primer
Scrum is an agile framework that can help address complex problems and develop high-value products. It consists of roles, artifacts, and events used to structure development into sprints. The roles include the product owner, development team, and scrum master. Artifacts include the product backlog, sprint backlog, and increment. Events include sprint planning, daily scrums, sprint reviews, and retrospectives. Scrum takes an empirical, transparent, inspect-and-adapt approach to product development through short iterations.
The 7 Deadly Sins Of Almost Being Agile
Agile 2009 presentation by Bob Hartman and Richard Lawrence titled "The 7 Deadly Sins of Almost Being Agile"
Scaling agile scrum practices 2.0
The document discusses scaling agile practices from Scrum to larger projects and organizations. It introduces IBM's Agile Scaling Model which includes core agile development, Disciplined Agile Delivery, and Agility@Scale. Key practices that need to be scaled include product backlogs, roles, release planning, sprint planning, and sprint demos to address factors like large team sizes, geographic distribution, and organizational complexity. Case studies are provided on how organizations have successfully scaled agile.
L'illusione dell'ortogonalità
Cosa abbiamo scoperto in questi 20 anni? Che cercare di cambiare il mondo focalizzandoci su un singolo aspetto, il processo, il TDD, il clean code, non porta da nessuna parte. I veri cambiamenti avvengono quando scopriamo le reali interazioni tra le parti, quando lasciamo la specializzazione e cominciamo a vedere il vero quadro d'insieme.
In questo talk vedremo come scelte architetturali apparentemente innocue, finiscano per impattare il processo, ed in generale di come processi, pratiche, architetture, persone e scelte di business non possano essere considerate come elementi disaccoppiati tra loro.
Screennect pitch
This document describes Screennect, an app that allows users to easily capture and catalog slides from conference presentations. The app uses location services and conference tags to catalog slides, which users can then view and share. It aims to improve on manually taking photos of slides, which can miss content and be of low quality. The app will be available initially on iOS, with future plans for other platforms. The founders aim to generate traffic through partnerships with conferences and by refining the product based on customer feedback. The first version is scheduled for release in two weeks.
Failing With Agile
Presentation for Mile High PMI Workshop on November 15, 2008
Abstract:
There are always people who want agile projects to fail. This will probably be the case until agile is the preferred process methodology used for projects. Are you one of them? In this workshop Bob Hartman will give participants a how-to guide for causing agile process failure. Attendees will learn various failure modes and how to cause them. There will be group discussions and exercises exploring how the failure modes can manifest themselves in real projects. At the end of this workshop each attendee should have the ability to cause agile project failure in a variety of ways and under a variety of conditions.
Obviously the first paragraph is a bit tongue-in-cheek. Hopefully project managers do not want agile projects to fail, but they need to know how they could fail. This knowledge will translate into an ability to recognize the failure modes and take corrective action. Interestingly, many of the agile project failure modes are also failure modes in other project process methodologies. All project managers on agile projects or in organizations that are considering using an agile process should attend this workshop. Project managers in organizations which typically struggle with projects may also gain insight into their project failure modes.
Scrum and Kanban are not enough - Agile Slovenia 2013
Scrum and Kanban are not enough to make an organization agile. Good organizations choose practices that fit their needs, like valuing individuals, working software, customer collaboration and adaptability. While common project methods focus on fixed plans, agile emphasizes adapting to changes. Scaling agile means dividing work into independent sub-products developed by autonomous teams with communication. Stickers on a wall won't help without addressing cultural and technical foundations for agility.
Agile is Dead :: Agile Connect Lisbon 2018
This document discusses how Agile has become outdated and ineffective in many organizations. It argues that while Agile and Scrum were created with good intentions, most companies have lost sight of the original purpose and focus too much on processes rather than outcomes. As a result, developers, customers, and stakeholders are often unhappy. The document suggests companies need to refocus on principles like individuals, interactions, and responding to change rather than rigidly following practices. It questions common Agile practices like overreliance on tools, certifications, and the belief that Scrum alone is enough. The goal of Agile should be happy customers and developers, not self-promotion or following trends. Companies need to experiment more and apply Agile principles rather
Agile pathologies
The document discusses various challenges that organizations, management, teams, and individuals face when adopting agile practices. It identifies strengths that sometimes become weaknesses for organizations. For management, it calls out a lack of courage and misguided command and control approaches. Teams struggle with issues that repeat in retrospectives and extending iterations. Individuals may be uninterested in understanding why agile is used or have behaviors that block acceptance. The document provides analysis of these challenges across multiple levels and suggests focusing on developing people.
Agile Pathologies: Backyards of Agile Shops
The document discusses various challenges that organizations, management, teams, and individuals face when adopting agile practices. It identifies strengths that sometimes become weaknesses for organizations. For management, it calls out a lack of courage and misguided command and control approaches. Teams struggle with issues that repeat in retrospectives and extending iterations. Individuals may be uninterested in understanding why agile is used or have behaviors that block acceptance. The document provides analysis of these challenges across multiple levels and suggests focusing on developing people.
Solving The Puzzles Of Agile Testing [V1.0 Final With Antipatterns]
The document discusses agile testing practices and provides advice for organizations transitioning to agile. It uses a Rubik's cube analogy to illustrate how an organization's testing function may be unaligned at the start of an agile transition and requires solving various "puzzles". Common anti-patterns that can derail an agile transition are identified. The presentation emphasizes determining an organization's "state of readiness" and having a transition plan to address impediments before embarking on an agile approach. Testing practices should evolve along with other agile engineering practices rather than trying to bolt on agile practices.
Similar to Death by Dogma versus Agile Assembly (20)
Validation Missteps Making Us Full Time Firefighters
Validation Missteps Making Us Full Time Firefighters
Scrum and Kanban are not enough - Agile Slovenia 2013
Scrum and Kanban are not enough - Agile Slovenia 2013
Solving The Puzzles Of Agile Testing [V1.0 Final With Antipatterns]
Solving The Puzzles Of Agile Testing [V1.0 Final With Antipatterns]
More from Sander Hoogendoorn
Flow. The official worst software development approach in history
As presented as opening keynote to SDD 2019 in London, together with Kim van Wilgen, customer director at Schuberg Philis. Ever since we started writing code in the fifties of the previous century, managers and project managers have tried to discipline and structure the way we work. However, no matter how many consultants and coaches are hired to implement increasingly complex process frameworks and methodologies, developers and testers always come up with new simplistic approaches.
During this talk, Kim and Sander will feal with Flow: the worst software development methodology in the history ever, taking inspiration from the worst principles and practices from methodologies such as waterfall, RUP, Scrum, Kanban, Lean, BDD, LeSS , SAFe, Spotify and of course everything continuous. Don't let project failure take you by surprise, be certain!
It's a small world after all. How thinking small changes software big time
Our world changes at increasing speed. Things that weren’t possible 5 years ago come into reach. Incumbents need to adapt to match start-ups. We evolve towards smaller, faster, shorter. Smaller teams or even micro-teams, flat organizations, no management, even shorter cycles, smaller components. During this inspiring talk, Sander discusses Cynefin, how development goes wrong, how to go beyond Scrum, why self-organization is hard, why continuous delivery allows you to stop doing projects.
Welcome to the world of micro-apps
Microservices have been around since a few years, and many organizations are starting to benefit from these autonomous, independently deployable and easy maintainable small blocks of code. However, if you examine some of the popular definitions of microservices, we are still building a single application as a suite of small services.
During this talk Sander Hoogendoorn will explain and demonstrate how front-end development can also benefit from building it in small autonomous, independently deployable blocks of code, instead of implementing a single monolithic web application. Of course, Sander will use many code examples in Java, Angular and Typescript (and probably some live coding) to illustrate even better how to build micro-applications similar to your microservices.
Welcome to the world of micro-applications
Microservices have been around since a few years, and many organizations are starting to benefit from these autonomous, independently deployable and easy maintainable small blocks of code. However, if you examine some of the popular definitions of microservices, we are still building a single application as a suite of small services.
During this talk Sander Hoogendoorn will explain and demonstrate how front-end development can also benefit from building it in small autonomous, independently deployable blocks of code, instead of implementing a single monolithic web application. Of course, Sander will use many code examples in Java, Angular and Typescript (and probably some live coding) to illustrate even better how to build micro-applications similar to your microservices.
Wat is agile en wat betekent het voor mij?
Slide deck bij mijn talk op het Tech Savvy Assistent Event op 14 juni 2018 in het Muntgebouw, Utrecht, waarin ik op een agile wijze agile bespreek met ongeveer honderd secretaresses en personal assistents.
20180509 - It's a small world after all. How thinking small is changing softw...
Talk for Codemotion Amsterdam 2018 conference on May 8, 2018 about the future of software development and how it needs to move beyond agile
W-JAX 2017 Keynote. It's a small world after all. How thinking small is chang...
Sander Hoogendoorn is an independent software architect, agile coach, and programmer. The document discusses trends in software development such as smaller teams, microservices, serverless computing, and continuous delivery in order to deliver value to customers more quickly. It also addresses challenges with scaling agile and ensuring autonomous teams through minimal rules and processes.
Swanseacon 2017 Keynote - It's a small world after all.
This document contains a series of slides by Sander Hoogendoorn on topics related to agile software development. Some key points discussed include:
- The benefits of smaller components like microservices over monolithic architectures.
- How teams and development cycles are trending toward being even smaller, more autonomous, and continuous.
- Why estimates and plans are giving way to minimal viable products and roadmaps in a continuous delivery model.
- How the landscape is shifting from projects to a continuous culture of learning and exploration.
Building Better Software Faster
The slide deck to my kick-off keynote at software vendor ANVA's new year on January 10, 2017. This talk covers agile, Scrum, Kanban, continuous delivery, microservices.
Geecon Prague 2016 - Thirty months of microservices
Slide deck for my talk on microservices, domain driven design and continuous delivery at the GeeCon 2016 conference in Prague, October 2016.
Thirty months of microservices. Stairway to heaven or highway to hell
This is the deck of the talks on microservices I did at both Avisi's #ASAS2016 (Arnhem, NL), Microsoft's #TechDaysNL (Amsterdam, NL) and #GeeCon (Prague, Czech Republic) conferences in September and October 2016.
Microservices are the next hype. Websites are full of introducing posts, books are being written and conferences organized. There’s big promises of scalability and flexibility. However, when you are knee deep in mud as an architect, developer or tester, it’s hard to find out how to get there. Sander Hoogendoorn, independent craftsman and CTO of Klaverblad Insurances, discusses the long and winding road his projects, both greenfield and brownfield, have travelled. Sander will e.g. address polyglot persistence, DDD, bounded contexts, modeling HTTP/REST, continuous delivery and many lessons learned, using many real-life examples.
Beyond breaking bad. The current state of agile in ten easy lessons
This document outlines Sander Hoogendoorn's lessons on the current state of agile based on his experience as a software architect, trainer, and agile thought leader. The lessons critique common agile practices and misconceptions, such as over-reliance on scrum rituals, use of manufacturing metaphors for software development, and treating agile as a one-size-fits-all approach. Hoogendoorn advocates for adapting agile principles to the specific context and allowing continuous learning. The document concludes by noting that growth and change, while painful, are necessary to avoid being stuck in an undesirable situation.
Beyond breaking bad. The current state of agile in ten easy lessons
After having coached iterative and agile projects for almost twenty years, author, craftsman and independent consultant Sander Hoogendoorn, looks back on what agile, Scrum, Kanban, XP and other agile approaches have brought us in real-life. In his well-known, high-speed style Sander will motivate why agile is dead, why you need to stay away from Scrum task-boards, how to stay away from estimates and deadlines, how to avoid red sprints, how to put your trust in metrics, how to draw owls, that projects are waste, and most of all that you are not Usain Bolt and last-but-not-least he will explain why you should stop doing projects!
Microservices. Stairway to heaven or highway to hell
The document discusses microservices and two case studies of companies adopting a microservices architecture. In the first case study, a major insurance company moved from a monolithic architecture to microservices in order to improve scalability, use multiple technologies, and develop features independently. They focused on modeling business processes and implemented services around individual processes. The second case study involved a product development company migrating an existing system to microservices. They redesigned the architecture with bounded contexts and migrated components incrementally. The document also covers microservices design principles, modeling resources as RESTful services, and challenges with testing microservices.
Microservices. The good, the bad and the ugly.
This is the slide deck for my keynote at the Software Architect conference in London, October 2015.
The development and maintenance of monoliths presents organisations with increasing challenges, resulting in high costs and a decreasing time-to-market. More and more organisations are therefore attempting to componentise their applications.
The latest and greatest paradigm “microservices” finally seems to deliver on the promises of service-oriented architecture: shortening time-to-market, scalability, autonomy, and exchangeability of technology and databases. The challenges of delivering microservices however are equally big.
In this keynote presentation, Sander will elaborate on his personal experiences with implementing microservices architectures. He’ll be certain to address the good parts, but he does not shy away from also tackling the bad and ugly parts.
Modeling Microservices
This is the slide deck from my keynote at the EA User Event in Brussels, September 2015. Micro-services and micro-services architecture are the next hype in software development. Websites and blogs are full of introducing posts, the first books are being written and the first conferences organized. There’s big promises of scalability, flexibility and replaceability of individual elements in your landscape. However, when you are knee deep in the mud as a software architect at an insurance, it is very hard to find help on how to design applications and components in a micro-services architecture. During this talk Sander will show how he used Enterprise Architect to model the micro services architecture, and will explain the difficulties and the lessons learned, using many real-life examples.
Designing and building a micro-services architecture. Stairway to heaven or a...
The document discusses designing microservices architectures and whether they represent a "stairway to heaven" or "highway to hell". It summarizes two real-world cases of companies transitioning to microservices. The first case is of a major insurance company moving from a mainframe monolith to microservices by implementing business processes as micro-applications. The second case is of a product company with no initial architecture transitioning to modular microservice components to improve development and scalability. The document advocates an evolutionary approach to microservices starting with guiding principles and business processes, and designing modular services.
Microservices. The good the bad and the ugly
Slide deck from my keynote at the Software Development 2020 Conference in Breda, The Netherlands, June 2015. Micro-services and micro-services architecture are the next hype in software development. Websites and blogs are full of introducing posts, the first books are being written and the first conferences organized. There’s big promises of scalability, flexibility and replaceability of individual elements in your landscape. However, when you are knee deep in the mud as a software architect at an insurance, it is very hard to find help on how to design applications and components in a micro-services architecture. During this talk Sander Hoogendoorn, discusses the long and winding road the insurance company where he’s acting as the lead software architect has taken to implement their business processes in a micro-landscape. Sander will show how this company is modeling requirements in a micro-landscape using smart use cases, and will explain the difficulties and the lessons learned, using many real-life examples.
Scaling agile from the ground up
After we finally seem to have settled the agile wars, between XP, Scrum and Kanban, the market
now starts to flood with enterprise agile frameworks, such as SAFe, DAD and Agility Path.
However, many organizations are still struggling with how to implement agile, even in
straightforward projects. During this vivid talk Sander Hoogendoorn, independent agile mentor,
software architect and developer, will share his years of experiences in implementing agile
principles and techniques in organizations, from the ground up, one step at the time. Sander does
not shy away from criticizing agile – especially enterprise agile – and will go through a series of
anti-patterns, pitfalls and roadblocks organizations encounter when moving towards agile, Scrum
and Kanban. He also shows how to get around them, illustrated with many real-life and examples,
and how to implement agile in baby steps.
Growing a microservices landscape (with smart use cases)
Microservices and microservices architecture are the next hype in software development. Websites and blogs are full of introducing posts, the first books are being written and the first conferences organized. There’s big promises of scalability, flexibility and replaceability of individual elements in your landscape. However, when you are knee deep in the mud as a software architect at an insurance, it is very hard to find help on how to design applications and components in a microservices architecture. During this talk Sander Hoogendoorn, discusses the long and winding road the insurance company where he’s acting as the lead software architect has taken to implement their business processes in a microservices landscape. Sander will show how this company is modeling requirements in a microservices landscape using smart use cases, and will explain the difficulties and the lessons learned, using many real-life examples.
More from Sander Hoogendoorn (20)
Flow. The official worst software development approach in history
Flow. The official worst software development approach in history
It's a small world after all. How thinking small changes software big time
It's a small world after all. How thinking small changes software big time
20180509 - It's a small world after all. How thinking small is changing softw...
20180509 - It's a small world after all. How thinking small is changing softw...
W-JAX 2017 Keynote. It's a small world after all. How thinking small is chang...
W-JAX 2017 Keynote. It's a small world after all. How thinking small is chang...
Swanseacon 2017 Keynote - It's a small world after all.
Swanseacon 2017 Keynote - It's a small world after all.
Geecon Prague 2016 - Thirty months of microservices
Geecon Prague 2016 - Thirty months of microservices
Thirty months of microservices. Stairway to heaven or highway to hell
Thirty months of microservices. Stairway to heaven or highway to hell
Beyond breaking bad. The current state of agile in ten easy lessons
Beyond breaking bad. The current state of agile in ten easy lessons
Beyond breaking bad. The current state of agile in ten easy lessons
Beyond breaking bad. The current state of agile in ten easy lessons
Microservices. Stairway to heaven or highway to hell
Microservices. Stairway to heaven or highway to hell
Designing and building a micro-services architecture. Stairway to heaven or a...
Designing and building a micro-services architecture. Stairway to heaven or a...
Growing a microservices landscape (with smart use cases)
Growing a microservices landscape (with smart use cases)
Recently uploaded
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdf
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
A Comprehensive Guide to DeFi Development Services in 2024
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Finale of the Year: Apply for Next One!
Presentation for the event called "Finale of the Year: Apply for Next One!" organized by GDSC PJATK
Recently uploaded (20)
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdf
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdf
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Deep Dive: AI-Powered Marketing to Get More Leads and Customers with HyperGro...
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Deep Dive: Getting Funded with Jason Jason Lemkin Founder & CEO @ SaaStr
Deep Dive: Getting Funded with Jason Jason Lemkin Founder & CEO @ SaaStr
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
WeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation Techniques
Death by Dogma versus Agile Assembly
- 1. Death by Dogma versus Agile Assembly Sander Hoogendoorn Principal Technology Officer & Global Agile Thoughtleader Capgemini @aahoogendoorn 1
- 2. 2
- 3. You would believe … because waterfall doesn’t work, right?
- 4. So the methodology doesn’t work @aahoogendoorn They should never have used waterfall. @aahoogendoorn Does the name of the project coincidently start with a C?
- 5. But how would you feel if …
- 6. @aahoogendoorn They didn’t apply Scrum right. @aahoogendoorn This project likely did ScrumBut, not Scrum. So it’s not the methodology, right?
- 7. 7
- 8. 8
- 9. Jack states that we have over 300 resources who are trained as SCRUM master. As it happens I’m meeting him this afternoon. I’ll ask him. 9
- 10. Dogmagile
- 11. Crusader Agile
- 12. Scrumdamentalism
- 13. Scrumdamentalism
- 14. Scrumdamentalism
- 15. Agilists against Zenifying Just write down small things on small papers. It’s your kaizen.
- 16. Agilists against Zenifying Don’t just write down small things on small papers. Write code. It’s your job.
- 17. There is no so thing as one-size-fits-all agile
- 18. The backlog Where does it come from?
- 19. And on the seventh day Ken created the backlog
- 24. Preliminary iterations Create Stabilize project software proposal Propose Scope Realize Realize Realize Realize Finalize Manage Write Deliver Maintain project working software plan software
- 26. Documentation Frenzy
- 27. But if your IT landscape looks like this …
- 28. Index cards might just not do the trick
- 29. User stories are merely meant to get the conversation going?
- 30. So what about documentation?
- 31. The agile manifesto doesn’t say no documentation (or modeling)
- 32. Eventually your software will go into maintenance (hopefully)
- 33. Will you document to maintain?
- 34. Guesstimation 34
- 35. Apples Team 1 35
- 36. Apples and oranges Team 1 Team 2 36
- 37. Apples and apples Team 1 Team 2 37
- 38. Distributed Apples Off shore Team 1 Team 2 Team 3 Team 38
- 39. Mandatory burn down chart? Bad smell: note how the same example is used in everyone’s presentations. Don’t trust a vendor’s presentation if it has this example of a burndown chart in it.
- 40. We have our ups and downs
- 41. Lightweight agile can be to enterprise projects What Monopoly is to solving the financial crisis
- 42. Agile is a sliding scale 42
- 43. Assembling Agile
- 44. Assembling Agile – The basics of agile Short Collaborative Small Iterations Teams Unit of Work Continuous Deliver Simplify Planning Early & Often Communication
- 46. Assembling Agile – Light Short Collaborative Small Iterations Teams Unit of Work Continuous Deliver Simplify Planning Early & Often Communication
- 48. Assembling Agile – Enterprise Short Collaborative Small Iterations Teams Unit of Work Continuous Deliver Simplify Planning Early & Often Communication
- 49. In retrospective
- 50. Agile is no religion So don’t be a zealot
- 51. Agile is a sliding scale 51
- 52. Value is found In all agile approaces (and yes, even in waterfall)
- 53. But please can we cut the crap And go back to work?
- 54. 54
- 55. Sander Hoogendoorn www.sanderhoogendoorn.com @aahoogendoorn 55