A presentation give at Agile Carolinas on some things that I think are needed to build quality software.
The content of the presentation is in the presenter notes.
The A3 Agile Business: An Agile Alignment ApproachKarl Scotland
As scale and distribution set in at organisations that have strong growth, spreading the lean and agile culture becomes even more important to keep teams aligned and motivated. At Rally, we have fallen in love with A3 Thinking and templates to address this challenge. We do new hire bootcamps, employee trainings and walk the talk, but A3’s seem to be the most effective tool for helping us spread lean thinking and empower teams to share their problems and strategies. This talk will tell our story, challenge the audience and provide some education on these powerful tools for enabling teams to collaborate, steer and take action.
In this Testing newsletter edition of Marlabs, have detailed about one of the most popular Test Management tool for agile methodology. Know the advantages of Rally over Traditional Test Management Tools, Rally editions and Rally Integration with other test management tools, CRM and IDE.
Also, Marlabs detailed how their clients were benefited in the in the test sprint cycles & different activities that were performed using Rally tool.
Download their next Testing newsletter edition on Security Testing at http://www.marlabs.com/services/testing/case-studies
How is Agile working for you? In the journey of adopting agile practices there might be challenges you face. Learn some of the common failure symptoms to look out for and get a look into what high performing agile looks like.. Lastly to learn what steps you can take to realize the full potential of Agile practices in your organization.
Are you ready to ignite business agility? Download the Business Agility Survival Guide.
http://2ral.ly/ZqE
The next level of agile will take you through how agile at scale is different then the team level agile. Strong agile basics are always key to a successful business and why connecting delivery to strategy is essential in realizing the promise of agile. This will help you understand where you are in your agile journey, how to identify trouble spots, and how to fix them.
The right management approach will always differ between
companies. lean has recently been breaking down barriers
in its application to a range of industries stemming from its
strong manufacturing background. But how does it compete
against similar, yet slightly different management practices
such as agile? and more so, can the two happily co-exist?
agile coach karl scotland, explains how cloud-based
solutions provider, Rally Software, used both lean and agile practices
together to best meet its customer’s needs.
The Impact of Agile Quantified - Agile Australia 2014Rally Software
Larry Maccherone, Director of Analytics for Rally Software, presents: The Impact of Agile Quantified. The tools to find the real-world numbers that can help you make the economic case to get the resources you need and get your people to commit to change. Learn more: http://www.rallydev.com/insights
Think Differently: Re-imagining Resource Management in a Disruptive AgeRally Software
by Catherine Connor
Think differently! Re-imagine your resource management.
Product manager role
Allow for thinking time
Stop starting and start finishing
Agile project management
Stable teams
Cross-functional teams
Limit Work in Process
Limit multitasking
Be team-driven in capacity planning
The A3 Agile Business: An Agile Alignment ApproachKarl Scotland
As scale and distribution set in at organisations that have strong growth, spreading the lean and agile culture becomes even more important to keep teams aligned and motivated. At Rally, we have fallen in love with A3 Thinking and templates to address this challenge. We do new hire bootcamps, employee trainings and walk the talk, but A3’s seem to be the most effective tool for helping us spread lean thinking and empower teams to share their problems and strategies. This talk will tell our story, challenge the audience and provide some education on these powerful tools for enabling teams to collaborate, steer and take action.
In this Testing newsletter edition of Marlabs, have detailed about one of the most popular Test Management tool for agile methodology. Know the advantages of Rally over Traditional Test Management Tools, Rally editions and Rally Integration with other test management tools, CRM and IDE.
Also, Marlabs detailed how their clients were benefited in the in the test sprint cycles & different activities that were performed using Rally tool.
Download their next Testing newsletter edition on Security Testing at http://www.marlabs.com/services/testing/case-studies
How is Agile working for you? In the journey of adopting agile practices there might be challenges you face. Learn some of the common failure symptoms to look out for and get a look into what high performing agile looks like.. Lastly to learn what steps you can take to realize the full potential of Agile practices in your organization.
Are you ready to ignite business agility? Download the Business Agility Survival Guide.
http://2ral.ly/ZqE
The next level of agile will take you through how agile at scale is different then the team level agile. Strong agile basics are always key to a successful business and why connecting delivery to strategy is essential in realizing the promise of agile. This will help you understand where you are in your agile journey, how to identify trouble spots, and how to fix them.
The right management approach will always differ between
companies. lean has recently been breaking down barriers
in its application to a range of industries stemming from its
strong manufacturing background. But how does it compete
against similar, yet slightly different management practices
such as agile? and more so, can the two happily co-exist?
agile coach karl scotland, explains how cloud-based
solutions provider, Rally Software, used both lean and agile practices
together to best meet its customer’s needs.
The Impact of Agile Quantified - Agile Australia 2014Rally Software
Larry Maccherone, Director of Analytics for Rally Software, presents: The Impact of Agile Quantified. The tools to find the real-world numbers that can help you make the economic case to get the resources you need and get your people to commit to change. Learn more: http://www.rallydev.com/insights
Think Differently: Re-imagining Resource Management in a Disruptive AgeRally Software
by Catherine Connor
Think differently! Re-imagine your resource management.
Product manager role
Allow for thinking time
Stop starting and start finishing
Agile project management
Stable teams
Cross-functional teams
Limit Work in Process
Limit multitasking
Be team-driven in capacity planning
How to make SAFe really SAFE Scaling Agile using Pull/Invite rather than Push...Yuval Yeret
https://agile2016.sched.org/event/6ecx/how-to-make-safe-really-safe-scaling-agile-using-pullinvite-rather-than-pushmandate-yuval-yeret
Abstract:
The Scaled Agile Framework (SAFe(tm)) is a powerful and popular framework for implementing agile at large scale across the enterprise.
In this talk we will examine some dangerous Agile at Scale implementation anti-patterns from real-world cases I've been involved in such as:
Planned/Mandate-based implementation across the enterprise - Pushing implementations onto people regardless of their interest/motivation to change.
Prescribed-based implementation - Either by the book or as designed by a central committee or an external consultant.
Total focus on practices starting from training all the way through assessment/metrics and lack of attention to spirit/principles.
Expecting every group in the organization to work the same way and implement change the same way.
We will then look at some healthier alternatives I used to drive more successful & sustainable change in several organizations. You will learn some concrete techniques that help live up to the Lean/Agile principles of respecting and engaging people.
Using SAFe as the specific backdrop for discussion, we will review field-proven ideas such as pull-based crossing the chasm approach to implementation, use of open space as part of the different SAFe ceremonies, and how Open Space Agility can combine with SAFe.
Note that the ideas and practices have also been tried with other Scaled Agile approaches such as Enterprise Kanban, LeSS.
Learning Outcomes:
Get familiar with some scaled agile implementation anti-patterns related to push/mandate.
Understand when to choose pull/invitation as a healthier more sustainable and successful alternative.
Get some concrete techniques to bring pull/invitation into a scaled agile implementation approach - focusing on SAFe 1-2-3 implementation approach specifically.
Have a high-level understanding of how to implement SAFe using "Open Space Technology".
Understand how to apply these ideas to any Scaled Agile approach (not just SAFe)
Agile ME Meetup: Agile A-Z - Chapter 1: The Product OwnerRasmus Runberg
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organisations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
In the first chapter, we had a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? - In this chapter we will go more into the details with the Product Owner.
As a Product Owner you’re responsible for your product, together with your team and the client setting the direction of the product, making sure everyone is happy with the outcome. In this chapter, we will cover the following topics:
• Vision
• Backlog
• Epic and User Stories
• Agile Planning
Impact of agile quantified: 2014 edition - A de-mystery thrillerLarry Maccherone
For the first time in Agile history, there is solid research backed by hard numbers of tens of thousands of teams and hundreds of thousands of projects about the efficacy of Agile practices. This session introduces the first-ever quantified decision framework for targeting improvement and making Agile practice decisions.
Attendees will:
- Identify which Agile practices are based on Agile folklore, and which are based on quantifiable evidence
- How to use this information to target your improvement efforts
- What metrics to use for your context
How to use these metrics and apply these techniques
Presentation at Mastering SAP 21st May 2017
Struggling with agile at scale? Thinking about scaling agile beyond the team? Want to learn from others’ mistakes? There is a lot to be learnt from those who have successfully hitchhiked their way through the galaxy of scaled agile. This session celebrates the scaled agile hitchhiker, the people who bravely tried ideas that were occasionally brilliant but often plain stupid. You will laugh, you will cry but you will also walk away with a nice long list of ideas not to try when scaling agile!
• Seven failure patterns in scaling agile
• An understanding of why these patterns lead to less than optimal results
• Tips on how to avoid falling into these failure patterns
Анна Мамаєва: When SAFe is safe. Agile для дорослих компанійLviv Startup Club
Kyiv Project Management Day 2016 Анна Мамаєва: When SAFe is safe. Agile для дорослих компаній
Сайт конференції: http://pmday.org/
Спільнота в мережі Linkedin: http://bit.ly/PMDayLin
Спільнота в мережі facebook: http://bit.ly/PMDayKyivFB
Twitter конференції: https://twitter.com/LvivPMDay
SAFe – A dangerous weapon. Techniques to implementing a lasting adoption of t...Yuval Yeret
Please join us on Wednesday January 27 in Burlington MA starting at 6:30 pm as senior enterprise agility coach Yuval Yeret describes several techniques that can be used to produce a lasting and productive adoption of the Scaled Agile Framework.
The Scaled Agile Framework (SAFe) is a powerful and popular framework for implementing agile at large scale across the enterprise. However many organizations see their implementation of SAFe stall and even backfire since the adoption is mandated from its organizational leaders, instead of engaged teams participating and choosing their SAFe.
In this talk we will examine some dangerous implementation anti-patterns as well as healthier alternatives. You will learn some concrete techniques that help live up to the Lean/SAFe principles of respecting and engaging people. We will discuss field-proven ideas such as pull-based crossing the chasm approach to implementation, use of open space as part of the different SAFe ceremonies, and how Open Space Agility can combine with SAFe.
Agile ME Meetup: Agile A-Z - Chapter 4: The Feedback LoopRasmus Runberg
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organisations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
In the first chapter, we had a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? - In the second chapter we looked into the Product Owner role and the many expectations and responsibilities that comes along with the "titel" - and in the third chapter we turned our focus towards the Scrum Master, his role, responsibilities and the ceremonies in SCRUM.
In the fourth chapter - the last this year - we will focus on the feedback loop. In order to be agile, to inspect and adapt and to learn fast you need to get feedback, so a strong and quick feedback loop is essential for succes with Agile. In the chapter we will be covering the following topics:
• Failing is learning
• Feedback loop
• DevOps
Abstract:
More and more organizations are realizing that in order to achieve business agility they need to go beyond implementing agile in specific teams/projects. Real agility requires scaling agile to the program/portfolio/enterprise level. In this session we will explore the options organizations have when looking to scale agile, with an emphasis on SAFe(tm) - the Scaled Agile Framework - one of the most popular options these days.
Learning Objectives:
• When does it make sense to Scale Agile
• What are the leading scaling approaches
• An introduction to SAFe's Big Picture and implementation configurations
• How to implement SAFe - The Implementation Roadmap
• Typical Results of implementing SAFe
• Key risks/red flags to be aware of when implementing SAFe
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
Agile ME Meetup: Agile A-Z - Chapter 1: AgileRasmus Runberg
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organisations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
This Chapter (1/6): Agile
In this first chapter, we will have a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? We will cover the following topics:
• The Agile Manifesto and it's principles
• Agile Methodology vs. Mindset and Culture
• The value of Agile
• SCRUM
• Kanban
A common practice among teams in IT companies adopting the latest trends, Agile can be scaled to enterprise level once applied properly. In this Innovation Session, Maduri Senadheera from the Project Management team talks about the Agile mindset, the need for scaling and the benefits of a Scaled Agile Framework for better aligning business processes.
In the last 24 months, we've transformed the way we work using the Scaled Agile Framework. To help with the transformation, we are also using UX practices, design thinking and lean startup methods.
By the end of this presentation, you will understand how we have leveraged UX practices, innovation games and design sprints to improve the maturation of the business needs and their prioritisation to best fit what our users want and deliver value in a continuous flow.
Sa fe 4.0 implementing Enterprise Agile using the Scaled Agile Frameworkevatjohnson
The adoption of Agile is spreading across various industries, in organizations of all sizes. However, most experts agree that scaling Agile for enterprise use is a challenge. SAFe®, the Scaled Agile Framework, was created to resolve this problem. SAFe® provides a fully controlled way to adopt and scale Agile across large companies, and to align Agile processes to business strategy.
The Scaled Agile Framework's latest edition 4.0 introduces the optional Value Stream level to synchronize all the Agile Release Trains, as well as other updates compared to SAFe® 3.0. Our webinar helps you to learn more about implementing enterprise Agile with the Scaled Agile Framework, and the differences between SAFe®'s previous versions and its recently released 4.0.
Deconstructing the scaled agile framework - Lunch and Learn seriesAngela Dugan
Deconstructing the Scaled Agile Framework - boiling down the "big diagram" and talking about when and how SAFe *might* be an appropriate direction for you or your team. Also covers practices from SAFe that could be useful regardless of the size and complexity of your organization
SAFe (Scaled Agile Framework) 5 mins overview - Roni TamariAgileSparks
Why Scale? When choose each scaling approach? SAFe? LeSS? Enterprise Kanban? Other? Scaling experts will compare the different approaches, share from their experience and answer questions from the audience
This is the SAFe section presented by Roni Tamari
A talk I gave internally at Wotif about using Rally, from RallyDev, for managing iterations. Generally good advice on how to run a team using Rally as a project-management tool (at least I think so)
How to make SAFe really SAFE Scaling Agile using Pull/Invite rather than Push...Yuval Yeret
https://agile2016.sched.org/event/6ecx/how-to-make-safe-really-safe-scaling-agile-using-pullinvite-rather-than-pushmandate-yuval-yeret
Abstract:
The Scaled Agile Framework (SAFe(tm)) is a powerful and popular framework for implementing agile at large scale across the enterprise.
In this talk we will examine some dangerous Agile at Scale implementation anti-patterns from real-world cases I've been involved in such as:
Planned/Mandate-based implementation across the enterprise - Pushing implementations onto people regardless of their interest/motivation to change.
Prescribed-based implementation - Either by the book or as designed by a central committee or an external consultant.
Total focus on practices starting from training all the way through assessment/metrics and lack of attention to spirit/principles.
Expecting every group in the organization to work the same way and implement change the same way.
We will then look at some healthier alternatives I used to drive more successful & sustainable change in several organizations. You will learn some concrete techniques that help live up to the Lean/Agile principles of respecting and engaging people.
Using SAFe as the specific backdrop for discussion, we will review field-proven ideas such as pull-based crossing the chasm approach to implementation, use of open space as part of the different SAFe ceremonies, and how Open Space Agility can combine with SAFe.
Note that the ideas and practices have also been tried with other Scaled Agile approaches such as Enterprise Kanban, LeSS.
Learning Outcomes:
Get familiar with some scaled agile implementation anti-patterns related to push/mandate.
Understand when to choose pull/invitation as a healthier more sustainable and successful alternative.
Get some concrete techniques to bring pull/invitation into a scaled agile implementation approach - focusing on SAFe 1-2-3 implementation approach specifically.
Have a high-level understanding of how to implement SAFe using "Open Space Technology".
Understand how to apply these ideas to any Scaled Agile approach (not just SAFe)
Agile ME Meetup: Agile A-Z - Chapter 1: The Product OwnerRasmus Runberg
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organisations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
In the first chapter, we had a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? - In this chapter we will go more into the details with the Product Owner.
As a Product Owner you’re responsible for your product, together with your team and the client setting the direction of the product, making sure everyone is happy with the outcome. In this chapter, we will cover the following topics:
• Vision
• Backlog
• Epic and User Stories
• Agile Planning
Impact of agile quantified: 2014 edition - A de-mystery thrillerLarry Maccherone
For the first time in Agile history, there is solid research backed by hard numbers of tens of thousands of teams and hundreds of thousands of projects about the efficacy of Agile practices. This session introduces the first-ever quantified decision framework for targeting improvement and making Agile practice decisions.
Attendees will:
- Identify which Agile practices are based on Agile folklore, and which are based on quantifiable evidence
- How to use this information to target your improvement efforts
- What metrics to use for your context
How to use these metrics and apply these techniques
Presentation at Mastering SAP 21st May 2017
Struggling with agile at scale? Thinking about scaling agile beyond the team? Want to learn from others’ mistakes? There is a lot to be learnt from those who have successfully hitchhiked their way through the galaxy of scaled agile. This session celebrates the scaled agile hitchhiker, the people who bravely tried ideas that were occasionally brilliant but often plain stupid. You will laugh, you will cry but you will also walk away with a nice long list of ideas not to try when scaling agile!
• Seven failure patterns in scaling agile
• An understanding of why these patterns lead to less than optimal results
• Tips on how to avoid falling into these failure patterns
Анна Мамаєва: When SAFe is safe. Agile для дорослих компанійLviv Startup Club
Kyiv Project Management Day 2016 Анна Мамаєва: When SAFe is safe. Agile для дорослих компаній
Сайт конференції: http://pmday.org/
Спільнота в мережі Linkedin: http://bit.ly/PMDayLin
Спільнота в мережі facebook: http://bit.ly/PMDayKyivFB
Twitter конференції: https://twitter.com/LvivPMDay
SAFe – A dangerous weapon. Techniques to implementing a lasting adoption of t...Yuval Yeret
Please join us on Wednesday January 27 in Burlington MA starting at 6:30 pm as senior enterprise agility coach Yuval Yeret describes several techniques that can be used to produce a lasting and productive adoption of the Scaled Agile Framework.
The Scaled Agile Framework (SAFe) is a powerful and popular framework for implementing agile at large scale across the enterprise. However many organizations see their implementation of SAFe stall and even backfire since the adoption is mandated from its organizational leaders, instead of engaged teams participating and choosing their SAFe.
In this talk we will examine some dangerous implementation anti-patterns as well as healthier alternatives. You will learn some concrete techniques that help live up to the Lean/SAFe principles of respecting and engaging people. We will discuss field-proven ideas such as pull-based crossing the chasm approach to implementation, use of open space as part of the different SAFe ceremonies, and how Open Space Agility can combine with SAFe.
Agile ME Meetup: Agile A-Z - Chapter 4: The Feedback LoopRasmus Runberg
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organisations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
In the first chapter, we had a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? - In the second chapter we looked into the Product Owner role and the many expectations and responsibilities that comes along with the "titel" - and in the third chapter we turned our focus towards the Scrum Master, his role, responsibilities and the ceremonies in SCRUM.
In the fourth chapter - the last this year - we will focus on the feedback loop. In order to be agile, to inspect and adapt and to learn fast you need to get feedback, so a strong and quick feedback loop is essential for succes with Agile. In the chapter we will be covering the following topics:
• Failing is learning
• Feedback loop
• DevOps
Abstract:
More and more organizations are realizing that in order to achieve business agility they need to go beyond implementing agile in specific teams/projects. Real agility requires scaling agile to the program/portfolio/enterprise level. In this session we will explore the options organizations have when looking to scale agile, with an emphasis on SAFe(tm) - the Scaled Agile Framework - one of the most popular options these days.
Learning Objectives:
• When does it make sense to Scale Agile
• What are the leading scaling approaches
• An introduction to SAFe's Big Picture and implementation configurations
• How to implement SAFe - The Implementation Roadmap
• Typical Results of implementing SAFe
• Key risks/red flags to be aware of when implementing SAFe
Learn more about the scaled Agile Framework + scaling Agile. After a short introduction to several frameworks that aim to support the scaling of Agile (DAD, LeSS, SAFe®), this power point presentation from our webinar dives deeper into the details of the Scaled Agile Framework (SAFe®). Find the truth behind the often cited sentence “As Scrum is to the Agile team, SAFe® is to the Agile enterprise.”
Agile ME Meetup: Agile A-Z - Chapter 1: AgileRasmus Runberg
What is Agile? - What are the roles in Agile development? How do we implement or scale with Agile? Which Agile processes should I use in my case?
There are so many questions about Agile, so in a series of Meetups, we will try to uncover as many aspects of Agile as possible, in order to provide the full overview of Agility in organisations. The form will be a combination of presentations and discussions, so everyone has a chance to address their thoughts on the matter.
This Chapter (1/6): Agile
In this first chapter, we will have a more "general" talk about what Agile software development is, and the value behind it. What does it mean to be Agile? We will cover the following topics:
• The Agile Manifesto and it's principles
• Agile Methodology vs. Mindset and Culture
• The value of Agile
• SCRUM
• Kanban
A common practice among teams in IT companies adopting the latest trends, Agile can be scaled to enterprise level once applied properly. In this Innovation Session, Maduri Senadheera from the Project Management team talks about the Agile mindset, the need for scaling and the benefits of a Scaled Agile Framework for better aligning business processes.
In the last 24 months, we've transformed the way we work using the Scaled Agile Framework. To help with the transformation, we are also using UX practices, design thinking and lean startup methods.
By the end of this presentation, you will understand how we have leveraged UX practices, innovation games and design sprints to improve the maturation of the business needs and their prioritisation to best fit what our users want and deliver value in a continuous flow.
Sa fe 4.0 implementing Enterprise Agile using the Scaled Agile Frameworkevatjohnson
The adoption of Agile is spreading across various industries, in organizations of all sizes. However, most experts agree that scaling Agile for enterprise use is a challenge. SAFe®, the Scaled Agile Framework, was created to resolve this problem. SAFe® provides a fully controlled way to adopt and scale Agile across large companies, and to align Agile processes to business strategy.
The Scaled Agile Framework's latest edition 4.0 introduces the optional Value Stream level to synchronize all the Agile Release Trains, as well as other updates compared to SAFe® 3.0. Our webinar helps you to learn more about implementing enterprise Agile with the Scaled Agile Framework, and the differences between SAFe®'s previous versions and its recently released 4.0.
Deconstructing the scaled agile framework - Lunch and Learn seriesAngela Dugan
Deconstructing the Scaled Agile Framework - boiling down the "big diagram" and talking about when and how SAFe *might* be an appropriate direction for you or your team. Also covers practices from SAFe that could be useful regardless of the size and complexity of your organization
SAFe (Scaled Agile Framework) 5 mins overview - Roni TamariAgileSparks
Why Scale? When choose each scaling approach? SAFe? LeSS? Enterprise Kanban? Other? Scaling experts will compare the different approaches, share from their experience and answer questions from the audience
This is the SAFe section presented by Roni Tamari
A talk I gave internally at Wotif about using Rally, from RallyDev, for managing iterations. Generally good advice on how to run a team using Rally as a project-management tool (at least I think so)
Learn about the importance of measuring the right things and how to use metrics and data to improve performance. Get the right metrics and KPIs to improve performance so you can deliver on your organization’s most important initiatives.
Read The Seven Deadly Sins of Agile Measurement http://2ral.ly/Zqa to make sure you’re measuring performance in a way that actually improves results.
How can a team of 65 developers build and rapidly ship a high-quality product with only six QA engineers? At Atlassian, we’ve introduced the Quality Assistance model that changes the developer QA mindset, and engages developers in exploratory testing so software is developed right the first time. After all, the cheapest time to fix a bug is before it's written. Join us as we walk through the theory, history, and practice of the model, while busting some of the myths about developers and QA. Reject the tradeoff of time, scope, and quality, and finally have your cake and eat it too.
CA Agile Central (formerly Rally) Inside DevOpsCA Technologies
So you just got CA Agile Central. Now what? How does this fit into your organization’s development workflow and delivery pipeline? Come hear about how CA Agile Central provides transparency into your engineering organization.
For more information, please visit http://cainc.to/Nv2VOe
Creating a culture that provokes failure and boosts improvementBen Dressler
Everyone fails - but not everyone uses failed attempts as a source of learning and improvement. This talk outlines a framework to turn failure into gaining knowledge by understanding IF, HOW and WHY something fails.
This presentation is part of a Citrix Labs workshop introducing the concepts of rapid prototyping for developers. It focuses on the creation of early samples, models, or releases of a product built to test a concept or process or to act as a thing to be replicated or learned from.
Lean Software Development by DeKnowledge.net
-----------------------------------------------------------------------------
DeKnowledge is the leading provider of project management certifications training workshops and consultancy. In addition to our open enrollment certifications training workshops, we also offer a wide range of management, leadership and technical based courses that can be tailored to fit your organization's needs.
With offices in the USA, The Netherlands and India, we work with clients in USA, Europe, South Africa and Asia. Our mission is to help companies manage their projects/programs more effortlessly and efficiently. We do this by collaborating with our clients in the areas of portfolio/program and project management training workshops and consultancy.
Enhancing the user experience in our Web ApplicationsChrisCariglia
Summary of the UIE conference. I used this presentation to communicatet what changes we could bring to our own site / tools to enhance the user experience.
'Hold my beer.' Those three words have preceded some of the greatest moments in history. But who would’ve thought they’d pave the way for an epic user testing session? In this talk, Austin will discuss a drunken usability experiment and the unexpected influence that it had on the way that user research is conducted. Learn about new and unconventional methods for overcoming the struggles and pitfalls of traditional user testing, obtaining true and honest user feedback, and verifying the usability and simplicity of a design. Discover the resulting impact on bottom-line metrics like conversion rate, retention, engagement, and revenue. Walk away with a list of tools that you can use to conduct similar research and experiments on your own projects. Finally, learn about what it means to have a Culture of UX and gain actionable advice on how you can create it within your own company.
CdCon + GitOpsCon 2023 in Vancouver Canada. Slidedeck for the talk on Scaling Software Delivery: A framework for developer enablement through devRel and outreach.
Behaviour-driven development (BDD) started as an improved variation on test-driven development, but has evolved to become a formidable tool that helps teams communicate more effectively about requirements, using conversation and concrete examples to discover what features really matter to the business. BDD helps teams focus not only on building features that work, but on ensuring that the features they deliver are the ones that the client actually needs.
In this talk, we will discuss what BDD is about, its benefits, and how it affects teams and processes. We will discuss two case studies where BDD practices have been successfully introduced, including the benefits gained and challenges met. We will see how much benefit was gained when BDD was integrated into the broader development infrastructure, including issue tracking systems, requirements management, and project reporting.
We will also see how BDD can be applied to all levels of the development process, from requirements down to low-level coding. We will also look at the principle BDD tools available that can help teams implement executable specifications, BDD-style test automation, and living documentation effectively. Some of the tools discussed will include JBehave, Cucumber, Specflow, Jasmine and Spock.
We will also look at two case studies where BDD practices have been successfully integrated into several projects in large government and financial organizations. Teams that adopted BDD effectively benefited from significantly lower defect rates, much earlier discovery of errors and inconsistencies in the requirements, and better overall communication and collaboration within the team. However, practicing BDD does involve a significant change in mind-set compared to more traditional approaches, a different collaboration model between team members, and a high degree of stakeholder by-in and engagement, all of which should not be underestimated. We will discuss how the teams managed these various challenges during their BDD adoption story.
Andrew Gassen, CEO | Pivotal Software
0 for 3: Edtech Startup Lessons Learned
I’ve been a part of 3 different education technology companies, all focused on the K-12 market. Each of these companies failed, but each for different reasons and in spectacularly different ways. This talk is a bit of a public post-mortem that focuses on 3 key lessons from each company, including a brief discussion on how we might have done things a different way if I knew then what I know now.
Presented by the
Serious Play Conference
seriousplayconf.com
at
Orlando,
University of Central Florida,
UCF,
July 24-26, 2019
Slides from "Taking an Holistic Approach to Product Quality"Peter Marshall
This is the base material used during a half day workshop at expoQA 17 June 2019. Peter Marshall runs over the necessary technical, organisational, and improvement practices required to deliver high quality software. Deep dives into Continuous delivery, devops, organisational structures, agile and digital transformation.
Similar to Adopting A Whole Team Approach To Quality (20)
Discount Usability Testing for Agile TeamsBen Carey
A talk from Agile Roots in 2010. You can't get the whole picture or much context from the slides.
The last part of the talk was referring to how you'll be remembered and your legacy in a social-media-based world.
It would be unfortunate if your last status update was the one that you see in the facebook wall post.
Video from the talk will be posted later.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
43. Start With No
“ Make features work hard to be implemented. The secret
to building half a product instead of a half-ass product is
saying no.
- 37Signals (from Getting Real)
52. We Get There Through…
Acceptance Criteria
Automated Acceptance Testing
Test-Driven Design
Automated Unit Testing
Continuous Integration
Continuous Governance
54. Sit together Have acceptance criteria
See the whole Automated acceptance testing
Have a vision Test-drive design
Find “true north” Automate unit testing
Know (really know) your users Continuous integration
Practice empathy Continuous governance
Avoid local efficiencies
Use systems thinking
Build the right things
Focus on the 20%
Hang out with users
Use Contextual Inquiry
Lo-fi usability testing
Paper prototypes
Leverage your feedback loops
Build communities
Listen to your users
Start with “no”
Build in quality
Mistake-proof
Thanks for coming out to the meetup.I want to start out the talk by telling you a short story to let you know what inspired me to put together this talk.
My story begins here, in an Agile team room.I was working with a team that had previously gone from a waterfall methodology and a team of 350 to using agile with a team of about 50.The team that I was working with was developing software for…
… doctors. Well, not just doctors – but specifically for physician’s offices.This includes the physicians, the front office staff, the nurses, and the back office staff.The software was widely used with about 125k physicians using the software and around 500k total users in the US.
Well, one day, someone on our team came to the realization that if we were developing software for physician’s practices, it might be a good idea to go visit one.I thought this sounded like a great idea, so I signed up. I was randomly assigned a few physician practices to visit and I ended up (of all places) in Corbin, Kentucky.This is Corbin.
In Corbin, I visited a fairly typical small practice. There were a husband and wife physician team and a handful of other employees like front office schedulers, a few nurses, and a person responsible for billing.
It was great getting to see how all of those different individuals in the office used our software in a real work environment.It always blew my mind that around half a million people were using our software on any given day.
I had a great time hanging out with the staff during my time that I was there……well, until the last day, when I noticed this…
I was observing Amy doing the end of the week billing cycle. This is where all of the bills are sent out to the insurance companies and the doctors office submit the charges that pay the bills for the practice.Amy was getting noticeably upset while she was using our software. She was trying to do a few routine things – but the software just wasn’t allowing her to get her work done in a way that made sense with how she typically worked. All Amy could tell was that the software wasn’t allowing her to close out the week. She wasn’t sure where she went wrong in aggregating the billings and the end of the day was quickly approaching.Amy usually leaves work at around 4:00 so that she can go and pick up her daughter at school.
Morgan is Amy’s daughter and she had just recently started attending school. She was only a couple of weeks into the school year and although she was having a good time at school, she enjoyed being picked up at the end of the day by her Mom.
As Amy tried and tried to do everything that she could think of to get the billing batch submitted, all she could think of was how lost she was and how she needed to get to school to pick up her daughter.As 4:00 quickly approached, Amy broke down and started crying. She had the pressure of making sure the practice got paid as well as the pressure of getting out of the office to make sure that she was there to pick up her daughter on time.Interestingly, Amy blamed herself for her lack of knowledge of the system.
As 4:00 passed and Amy was working frantically, all she could think of was how upset her daughter was going to be when she wasn’t there to pick her up as class let out.Amy ended up calling a friend to pick up Morgan.
When I went back to the hotel and thought about that day I ended up getting mad and frustrated that this software, the software that we were spending so much money to build, the software that this physician’s practice had spent so much money to buy, let Amy down.This wasn’t Amy’s fault.This was our teams fault.This was my fault.
Our users deserve more than this.Quality shouldn’t be something that we measure at the end. It needs to be continuous. It needs to be baked into everything that we do.To get to the level that quality is a given – everyone needs to be responsible.
If everyone is responsible for quality, then everyone needs to do their part to provide quality software and a quality experience. Your job on your team affects your users in one way or another.In this talk, I want to help you think about things that you can do to improve that quality.
When we focus on building quality software then we end up making everyone happy.Fewer defects, better usability, great experiences, happy users, and (last but not least) – smiling children.
I believe that there are three parts to adopting a whole-team approach quality that will result in building better software.
Let’s talk a bit about Seeing The Whole
There are a few different topics to touch on when I refer to Seeing The Whole.The first topic that I want to discuss is knowing your goal or the product vision.Almost without fail, when I visit any team and I ask them why they are building what they are building, I can never get a consistent answer. Most of the time, the answers have a common basis, but very rarely is there a shared and focused vision for the product that is being created.
At its very essence, the goal or the vision of your product is the answer to “Why are you building this?”Can you answer this question?If you asked everyone on your team, everyone who is involved with your product or service, or everyone throughout the company this question – would they answer it the same?If you feel like you can answer this question, do you really believe in the answer? Is everyone on your team focused on the same answer?Do you have a true understanding of what “this” really is, or is meant to be?
If you have a shared world-view of your answer to this question, then you have established a “True North”The concept of a True North is imperative to building quality software.True North is a contract, a bond, and not merely a wish list.It’s not a marketing slogan. Who are we? What do we believe in? Where are we going? What have we learned?The True North focuses on what is important and keeps us grounded in our decision making. We should constantly be putting our work and making our decisions based on an anchoring to our True North.
The next question that you need to ask yourself is “Who are we building this for?”Do you feel like you really know your users?Do you understand the value that your product or service is delivering through their eyes?
I’m not talking about “understanding your customers” – I’m talking about truly, authentically, deeply understanding your customers.Do you know why they can’t sleep at night? Do you know what they think when they wake up? Do you know their true intentions? Do you know what their desks look like?Do you know what they eat for lunch?Do you know what they think about when they’re driving home from the office?
Saying “As a (role)…” does not mean that you have a true understanding of your customers. I’m not talking about demographics either, 20 – 30yr. old asian female isn’t enough.Who are your users *really*, and what motivates them?In my case - Amy felt an obligation to do the billing. Her true goal wasn’t to do the billing – it was to pick up Morgan from school on time.
Knowing these things about your users lets you practice empathy in it’s purist sense.Your job is to build things that help your users achieve their objectives and accomplish their goals. To be able to do that effectively, you need to know what those things really are.You are viewing the result of your work through the eyes of your customer. When you do this, it’s a very eye-opening experience.
The last element of Seeing the Whole is to understand that it’s not (just) about you. It’s not (just) about your team. There are a variety of other roles, activities, and functions (or dysfunctions) that play into delivering a product or service and you need to understand the elements that allow for your product to go from an idea to generating revenue for your company.
It’s easy to forget the training, the pricing models, the marketing, the maintenance, and the ongoing use of the software when you’re laser-focused on the creation. The truth of the matter is that it is easy to produce sub-optimizations or local efficiencies when your effort and thoughts could be more effective elsewhere. Many local efficiencies result in user nightmares – so understand the overall picture – how the product delivery system functions as a whole – before wasting your thought and effort in places where they might not be needed.
Let’s talk a bit about building the right things
This is the distribution of used features in a typical application.What insights can we draw from this?
Let’s think about this in terms of your backlog.What if you only built the things that were frequently used?
To start with, you can try hanging out with your customers….The best way that I know to do this is to put your users in the center of your process.You can do this by practicing Contextual Inquiry.A customer-centered process requires making an explicit step of understanding who the customers really are and how they work on a day-to-day basis.CI allows you to observe your users in action in their natural environment. I’ve been involved in dozens of visits and I promise you that every single one was worth the time and effort.
Feedback is another huge way that we can build the right things.This thing we have called Scrum does a wonderful job of providing feedback loops and inspect and adapt cycles everywhere. How about we use that
You can integrate your users easily by doing paper prototypes and other quick and focused testing.
You can build community.Let your users get as close to you as possible and help drive your priorities.Listen to what they have to say (although you might not want to do what they suggest).Listen to understand.
You should also change direction when it’s justified.If the feedback is radically different than what we expected, we might even completely change our service, product, or business model.
Start with no, you don’t want to be a yes-man.Listen to your customers – but make conscious decisions. You don’t always need to make a faster horse.
Let’s talk a bit about building things right
To build things right, we need to build quality into the software.How can we do that?
For us to truly take a quality-focus, we have to unlearn the assumptions that we have about testing practices.
We have to rethink our approaches to building software.
A great area to start is to focus on the TPS concept of poka-yoke.
Poka-yoke means mistake proofing.
Example of Poka-yoke.
We should start by pulling testing fully forward.We need to move into a prevention mindset, instead of a fix mindset.
Take a bit and talk about each of these.
POVIt is my job, it is your job, it is our job –to deliver quality software and a quality experience.Do it for yourself, do it for your users, do it for Amy, do it for Morgan.
These are the majority of the things that I talked about tonight.You don’t need all of these to build better software and there are many more that you might use that weren’t talked about tonight.If you implement just one or two of these items then you’ll be on the right path to building better products and providing better experiences.
Take 3 minutes.Think about your product or service.Think about your role on your team.Think about your users or your customers.Think of one thing that you can commit to doing – that you aren’t doing – that would make your users smile.Take an index card and a sharpie and write that one thing down.Share (ask for volunteers). Fold them up and put them somewhere safe. Work on your item and inspire others to do the same.