Presentation I created to coach teams on importance of keeping Sprint Retrospective in their cadence. Includes techniques for more effective and uplifting retrospectives.
Will your team be faced with big problems, time limitations, stuck with same old ideas, or all three? Great, you're the perfect candidate for a design sprint. They deliver low risk high reward solutions to the biggest problems in a short amount of time. Learn how starting at the end gives you reliable customer signal before committing to the expense of developing and launching of a product. This session covers key concepts and actionable take-a-ways to empower teams from start-up size to enterprise.
Become a Confluence Whiz Kid: Organized Spaces and Beautiful PagesAtlassian
Many great achievements started with a page in Confluence. Still, users always ask us how to get started creating and organizing content. How you choose to organize content in Spaces and what your pages look like determines how effective your content is.
John Wetenhall, Confluence Whiz, is sharing top tips for Space organization and page creation from his 4 years working on Confluence and speaking to scores of users. He'll focus on Confluence's top use cases: project collaboration and knowledge bases, with hands on examples from Atlassian's own internal Confluence instances, so you know what great spaces and pages can look like, and how to actually create them.
Fast then Faster - a Retrospective on RetrospectivesAtlassian
So, you’re agile. You’ve got a healthy backlog, you understand your team’s velocity, and you’re holding retrospectives. You’re in a good place – right? Maybe not. You may have a handle on the quality of your stories & their output, but what about that of your team and those around you? Or your agile processes themselves?
Retrospectives are a great way to get feedback, but they are often both undervalued and underutilized as a tool for improvement. Agile gets you fast, but retrospectives get you faster.
We’ll walk you through what good and bad retrospectives look like, how to tell when they’re failing, and (more importantly) how to uncover what's lurking behind bias, ego, and protocol.
If you’re in doubt if this session is for you, suggest a team under pressure skips the retrospective this week, and see just how quickly they drop the most important part of the agile cycle!
Products covered:
JIRA Software, Confluence, Bitbucket, Bamboo, Fisheye / Crucible
Hit Your Stride: Designing Real-time Collaboration for TeamsAtlassian
Teamwork makes the dream work - but what if your dream is to help your team work better? What does working better even mean when teams are more digital, distributed, dynamic and diverse than ever before? In the Summer of 2017 Atlassian tasked a cross-functional research team with unlocking the potential of Atlassian tools to better support modern teams. In this talk, Sara Dubuque, Senior Designer, will share our research into team dynamics and our resulting design explorations in team communication.
Mindset: the biggest barrier to agilityFlavius Stef
Presentation from Optional Conference (Budapest).
Some agile transitions fail due to the mindset of the people affected by the change. Your mindset is characterized by how you answer these three questions: 1) What do you believe about people?; 2) How should social systems be organized?; 3) Who is our customer?
See more at: http://flaviusstef.wordpress.com/2014/04/07/is-your-mindset-blocking-your-agile-transformation/
The document provides tips for product managers to get engineers to build what they want in 3 main points:
1. Involve engineers as early as possible to develop a shared understanding of the problem and build relationships.
2. Work asynchronously and use tools like asynchronous messaging to discuss ideas and make decisions without blocking work.
3. Tell stories and provide context about user needs through techniques like customer interviews, but avoid giving too many implementation details, focusing on the what rather than the why.
Perhaps the most under-utilized assets in most companies are the ideas in employees’ heads. For that reason, this session aims to help attendees learn three key things:
How to tap into employees' passions to drive growth
A useful model for assessing whether your innovation programs are effective
How to use our “recipe book” to build a cohesive innovation program that drives growth
This session is meant to cover the case for employee-driven innovation – including success stories and data points. We'll also provide access to the tools, playbooks, and templates that can accelerate innovation programs in your company.
Atlassian User Group Insights: AUGment your Teams and CultureAtlassian
The Atlassian User Group (AUG) program built a culture of community that includes over 130 groups around the world and continues to grow 60% YoY, thanks to a team of passionate volunteer leaders and members. Building a focused and motivated team across the globe isn't easy, but we'll share the foundation to the user group community's success along with take-aways for attendees looking to build successful teams of their own. In this unique session, we will highlight the Atlassian User Group culture by presenting elements of a real user group event and provide meaningful information for attendees, including the opportunity to sign up and experience the user group team culture themselves.
Will your team be faced with big problems, time limitations, stuck with same old ideas, or all three? Great, you're the perfect candidate for a design sprint. They deliver low risk high reward solutions to the biggest problems in a short amount of time. Learn how starting at the end gives you reliable customer signal before committing to the expense of developing and launching of a product. This session covers key concepts and actionable take-a-ways to empower teams from start-up size to enterprise.
Become a Confluence Whiz Kid: Organized Spaces and Beautiful PagesAtlassian
Many great achievements started with a page in Confluence. Still, users always ask us how to get started creating and organizing content. How you choose to organize content in Spaces and what your pages look like determines how effective your content is.
John Wetenhall, Confluence Whiz, is sharing top tips for Space organization and page creation from his 4 years working on Confluence and speaking to scores of users. He'll focus on Confluence's top use cases: project collaboration and knowledge bases, with hands on examples from Atlassian's own internal Confluence instances, so you know what great spaces and pages can look like, and how to actually create them.
Fast then Faster - a Retrospective on RetrospectivesAtlassian
So, you’re agile. You’ve got a healthy backlog, you understand your team’s velocity, and you’re holding retrospectives. You’re in a good place – right? Maybe not. You may have a handle on the quality of your stories & their output, but what about that of your team and those around you? Or your agile processes themselves?
Retrospectives are a great way to get feedback, but they are often both undervalued and underutilized as a tool for improvement. Agile gets you fast, but retrospectives get you faster.
We’ll walk you through what good and bad retrospectives look like, how to tell when they’re failing, and (more importantly) how to uncover what's lurking behind bias, ego, and protocol.
If you’re in doubt if this session is for you, suggest a team under pressure skips the retrospective this week, and see just how quickly they drop the most important part of the agile cycle!
Products covered:
JIRA Software, Confluence, Bitbucket, Bamboo, Fisheye / Crucible
Hit Your Stride: Designing Real-time Collaboration for TeamsAtlassian
Teamwork makes the dream work - but what if your dream is to help your team work better? What does working better even mean when teams are more digital, distributed, dynamic and diverse than ever before? In the Summer of 2017 Atlassian tasked a cross-functional research team with unlocking the potential of Atlassian tools to better support modern teams. In this talk, Sara Dubuque, Senior Designer, will share our research into team dynamics and our resulting design explorations in team communication.
Mindset: the biggest barrier to agilityFlavius Stef
Presentation from Optional Conference (Budapest).
Some agile transitions fail due to the mindset of the people affected by the change. Your mindset is characterized by how you answer these three questions: 1) What do you believe about people?; 2) How should social systems be organized?; 3) Who is our customer?
See more at: http://flaviusstef.wordpress.com/2014/04/07/is-your-mindset-blocking-your-agile-transformation/
The document provides tips for product managers to get engineers to build what they want in 3 main points:
1. Involve engineers as early as possible to develop a shared understanding of the problem and build relationships.
2. Work asynchronously and use tools like asynchronous messaging to discuss ideas and make decisions without blocking work.
3. Tell stories and provide context about user needs through techniques like customer interviews, but avoid giving too many implementation details, focusing on the what rather than the why.
Perhaps the most under-utilized assets in most companies are the ideas in employees’ heads. For that reason, this session aims to help attendees learn three key things:
How to tap into employees' passions to drive growth
A useful model for assessing whether your innovation programs are effective
How to use our “recipe book” to build a cohesive innovation program that drives growth
This session is meant to cover the case for employee-driven innovation – including success stories and data points. We'll also provide access to the tools, playbooks, and templates that can accelerate innovation programs in your company.
Atlassian User Group Insights: AUGment your Teams and CultureAtlassian
The Atlassian User Group (AUG) program built a culture of community that includes over 130 groups around the world and continues to grow 60% YoY, thanks to a team of passionate volunteer leaders and members. Building a focused and motivated team across the globe isn't easy, but we'll share the foundation to the user group community's success along with take-aways for attendees looking to build successful teams of their own. In this unique session, we will highlight the Atlassian User Group culture by presenting elements of a real user group event and provide meaningful information for attendees, including the opportunity to sign up and experience the user group team culture themselves.
Early Signal Testing: Designing Atlassian’s New LookAtlassian
You probably have noticed the new look of Atlassian's Cloud products. Our new Design Guidelines took many months to create, and our team had many tough decisions to make. Luckily, we incorporated customer research along the way to guide us.
One of our most valuable research tools is called “early signal testing”, and we think it can help you too. Early signal testing can help you gain confidence in a direction, rather than being paralyzed by a choice. It can help assess your design's usability, clarity, comprehension, and more. This talk explains how your team can gather measurable user feedback in as little as a week, for even the very biggest of problems.
[Quiz] Do you work at a high-trust company?Atlassian
The document discusses 10 signs that indicate whether a company has a high-trust culture or not. These include leaders using inclusive language like "we" instead of "I", sharing failures and lessons learned across the company, leaders living the company values, information being open and easy to find, everyone knowing the business focus and performance, executives crowdsourcing strategies, and people feeling comfortable saying "no" to leaders. Exhibiting most or all of these signs suggests a collaborative, creative environment where people can comfortably share ideas, learn from mistakes, and make faster decisions.
The document discusses techniques for minimizing waste when developing products. It recommends using lean startup principles like building minimum viable products and getting early customer feedback through techniques like interviews and A/B testing. This allows businesses to learn quickly what customers want rather than wasting money on unnecessary features. Examples are given of how these principles were applied to develop an email digest product and plan a leadership workshop. The key is to start with the customer's problem, make assumptions explicit, and continually refine the product based on what is learned from real users.
How Atlassian's User Research Went Agile (and So Can Yours)Atlassian
In late 2015, we set up Atlassian Atlab: a low-budget customer research space that tightly integrates into the Agile sprint process. What began as an experiment quickly became an indispensable part of our company’s design process. Atlab is now international, run in all of our offices, gathering input from about 200 customers every month.
In this talk, we will teach you why agile research is a crucial part of building great customer experiences, how to create stakeholder buy-in for your efforts, best practices for conducting research, and what to do with your findings. We will also teach you how to set up your very own Atlab. Warning: it’s very cheap, and easier than you may expect!
Products covered:
JIRA Software, JIRA Core, JIRA Service Desk, Confluence, HipChat, Bitbucket, Bamboo, Fisheye / Crucible, Portfolio for JIRA
The document discusses web usability and usability testing. It recommends testing with 3-4 users to identify most significant problems. Usability testing involves having users try to accomplish tasks on a website while observers watch, listen and record results. The goal is to inform design improvements and test iteratively. Experts Steve Krug advises that even testing one user early is better than testing many users late in the process.
(Re)Discover JIRA Core: Tricks that Make a BIG DifferenceAtlassian
What do nontechnical teams, such as marketing, operations, HR, finance and legal have in common? Even though their processes might be different they can all use JIRA Core to track contracts, candidates, campaigns, approvals, and much more. But there are so many things you can tweak when setting up your team process: workflows, permissions, projects, issue types, etc.
Whether you’re new to JIRA Core, or a power user, we’ll share the best practices for business teams, and give examples of how teams use JIRA Core effectively. You'll learn how to:
Set up JIRA Core to match your business team's process
Set up user permissions for approval processes
Manage issues across different projects
Handle multiple milestone due dates
Expect tons of examples and aha moments when diving deep into the core of JIRA.
Products covered:
JIRA Core
Do Agile Right - Lessons Learned from an Atlassian Product Manager - Sherif M...Atlassian
Great products start with great planning. At Atlassian we take a multitude of approaches to plan our feature releases. Learn how you can take some of the practices the Confluence Product Management Team makes use of – such as product requirements, prototypes, customer interviews, and user journeys – to deliver great solutions for your customers.
The Experience Canvas: How to Use a Core Tool from the Experience-Driven Play...colleenfry
The document introduces the Experience Canvas, a tool used by teams at Atlassian to facilitate design thinking and collaboration. The Experience Canvas provides a framework to outline hypotheses, problems, ideas, prototypes, testing and more for any given project. An example is provided showing how a team used the Experience Canvas to address the "blank page problem" users encounter when first opening Confluence. The document encourages readers to use the Experience Canvas playfully with their own teams to drive innovation.
AcceleratorFest 2017: What startups really thinkStartupfest
Raymond Luk (Hockeystick.co)
Douglas Soltys (BetaKit)
Come hear the results of Startupfest's exclusive accelerator survey, compiled with Betakit's Douglas Soltys, and find out what accelerator alumni think of the programs they participated in.
In 2015, I ran a workshop at TestBash Brighton entitled "Supercharging Your Bug Reports" (also available in webinar format on the Ministry of Testing Dojo). In that class, I outlined some of the key components of an effective bug report, with the goal of helping testers to become better advocates for problems in their workplace. Fast-forward to 2017, and my world (and beliefs) have changed. I've been working in some fast-paced environments with highly-productive teams, where life moves at a pace which is largely incompatible with "traditional" bug reporting processes.
How do you effectively act as a champion for quality when one of your most visible forms of communication is taken away? In this talk, I'll share stories of my transition: how I had to adapt, the approaches that I chose to take, and evaluate how my 2017 outlook on bug reporting compares to my previous vision.
The document contains quotes and citations from various authors on topics related to design such as communication, problem solving, aesthetics, simplicity, and usability. It discusses how aesthetically pleasing designs can improve productivity and creativity. It also emphasizes that design is about solving problems and that simplicity through removing unnecessary features can lead to innovation. Well-designed products and systems should have intuitive functions and be easy to understand. Usability testing, even with one user, is important for improving websites.
This document discusses empowerment through collaboration in Agile teams. It describes how empowerment was lacking in traditional practices like stand-ups, retrospectives, and sprint reviews due to silos, lack of respect, and a blame culture. The author's team became more empowered by removing silos, valuing opinions, collaborating with customers, and trusting self-organizing teams. Practices like story mapping, 3 Amigos meetings, developer pairing, and collaborative retrospectives helped build relationships and a common understanding within the smaller team.
“Quality at Speed” is Atlassian’s approach to QA, and we are constantly evolving what that means and how it translates to actual dev team processes. Our developers can confidently take on testing activities, while our QA Engineers tackle larger, harder, and bolder challenges. Teams can ship better features, faster, and reach ambitious quality improvement goals.
We'll talk about how our team has embraced this mindset, how this changes our role in dev teams, and the results we want to achieve. We'll cover the different ways that quality can be defined, the importance of fast deployments, and how we work with teams like DevOps, Growth and Customer Insights to help our dev teams and ultimately benefit our users.
Products covered:
JIRA Software, Bitbucket, Bamboo
Developers can't focus only on the details of their code – they have to look at the application from a user's perspective, too. Join Maria Heij from RefinedWiki AB for a journey into the tester's (and user's) mindset. She'll cover knowing how and why your product is used, understanding the intent behind requirements, and product implementations – all aimed at extending your skills and making your add-ons even better.
Maria Heij, Support & Test Manager, RefinedWiki
This document provides guidance on conducting a usability study. It outlines the schedule, expectations for participants, and guidelines for running test sessions. Participants will be divided into groups of 3, with one person acting as the user and two observing. As a user, they will complete tasks while thinking aloud, and observers will take notes on successes, obstacles, and areas of confusion. After each task the group will switch roles. The goal is to evaluate the design and identify ways to improve the user experience.
Couples Counseling for Software Development by Joe StageGROWtalks
This document provides advice for software development teams on improving their product development process through better collaboration between different roles. It recommends that engineers be involved early in the design process to address technical constraints. It also advocates for an iterative process of building minimal prototypes and getting early user feedback, rather than long development cycles. Teams are advised to focus on solving user problems rather than getting attached to specific technical solutions. Overall, the document emphasizes shortening feedback loops through practices like continuous deployment and automated testing.
Collaboration is More Than Communication – JIRA Agile - Xavier MoreraAtlassian
Collaboration is defined as "the action of working with someone to produce or create something." Yet, many confuse communicating with collaborating. True collaboration gives you and your project an edge by aligning efforts towards a clear objective. I'll show how teams can achieve true collaboration with JIRA Agile.
The document discusses several common challenges organizations face when adopting agile and Scrum methodologies. Some of the key challenges mentioned include:
1) Organizational culture and structures not being ready for agile, such as "silos of knowledge" where expertise is concentrated in a few individuals rather than shared across teams.
2) Managers having a "command and control" mindset that does not trust employees and teams to plan and manage their own work.
3) Lacking an overall "agile culture" where goals are shared across the organization and there is transparency and collaboration between teams.
4) The initial adoption of Scrum being difficult, as it requires changes in roles like product owners
Compilation of the common challenges which experts have faced in the real agile environment. Ebook originally published in https://www.knowledgetrain.co.uk/agile/agile-challenges
Early Signal Testing: Designing Atlassian’s New LookAtlassian
You probably have noticed the new look of Atlassian's Cloud products. Our new Design Guidelines took many months to create, and our team had many tough decisions to make. Luckily, we incorporated customer research along the way to guide us.
One of our most valuable research tools is called “early signal testing”, and we think it can help you too. Early signal testing can help you gain confidence in a direction, rather than being paralyzed by a choice. It can help assess your design's usability, clarity, comprehension, and more. This talk explains how your team can gather measurable user feedback in as little as a week, for even the very biggest of problems.
[Quiz] Do you work at a high-trust company?Atlassian
The document discusses 10 signs that indicate whether a company has a high-trust culture or not. These include leaders using inclusive language like "we" instead of "I", sharing failures and lessons learned across the company, leaders living the company values, information being open and easy to find, everyone knowing the business focus and performance, executives crowdsourcing strategies, and people feeling comfortable saying "no" to leaders. Exhibiting most or all of these signs suggests a collaborative, creative environment where people can comfortably share ideas, learn from mistakes, and make faster decisions.
The document discusses techniques for minimizing waste when developing products. It recommends using lean startup principles like building minimum viable products and getting early customer feedback through techniques like interviews and A/B testing. This allows businesses to learn quickly what customers want rather than wasting money on unnecessary features. Examples are given of how these principles were applied to develop an email digest product and plan a leadership workshop. The key is to start with the customer's problem, make assumptions explicit, and continually refine the product based on what is learned from real users.
How Atlassian's User Research Went Agile (and So Can Yours)Atlassian
In late 2015, we set up Atlassian Atlab: a low-budget customer research space that tightly integrates into the Agile sprint process. What began as an experiment quickly became an indispensable part of our company’s design process. Atlab is now international, run in all of our offices, gathering input from about 200 customers every month.
In this talk, we will teach you why agile research is a crucial part of building great customer experiences, how to create stakeholder buy-in for your efforts, best practices for conducting research, and what to do with your findings. We will also teach you how to set up your very own Atlab. Warning: it’s very cheap, and easier than you may expect!
Products covered:
JIRA Software, JIRA Core, JIRA Service Desk, Confluence, HipChat, Bitbucket, Bamboo, Fisheye / Crucible, Portfolio for JIRA
The document discusses web usability and usability testing. It recommends testing with 3-4 users to identify most significant problems. Usability testing involves having users try to accomplish tasks on a website while observers watch, listen and record results. The goal is to inform design improvements and test iteratively. Experts Steve Krug advises that even testing one user early is better than testing many users late in the process.
(Re)Discover JIRA Core: Tricks that Make a BIG DifferenceAtlassian
What do nontechnical teams, such as marketing, operations, HR, finance and legal have in common? Even though their processes might be different they can all use JIRA Core to track contracts, candidates, campaigns, approvals, and much more. But there are so many things you can tweak when setting up your team process: workflows, permissions, projects, issue types, etc.
Whether you’re new to JIRA Core, or a power user, we’ll share the best practices for business teams, and give examples of how teams use JIRA Core effectively. You'll learn how to:
Set up JIRA Core to match your business team's process
Set up user permissions for approval processes
Manage issues across different projects
Handle multiple milestone due dates
Expect tons of examples and aha moments when diving deep into the core of JIRA.
Products covered:
JIRA Core
Do Agile Right - Lessons Learned from an Atlassian Product Manager - Sherif M...Atlassian
Great products start with great planning. At Atlassian we take a multitude of approaches to plan our feature releases. Learn how you can take some of the practices the Confluence Product Management Team makes use of – such as product requirements, prototypes, customer interviews, and user journeys – to deliver great solutions for your customers.
The Experience Canvas: How to Use a Core Tool from the Experience-Driven Play...colleenfry
The document introduces the Experience Canvas, a tool used by teams at Atlassian to facilitate design thinking and collaboration. The Experience Canvas provides a framework to outline hypotheses, problems, ideas, prototypes, testing and more for any given project. An example is provided showing how a team used the Experience Canvas to address the "blank page problem" users encounter when first opening Confluence. The document encourages readers to use the Experience Canvas playfully with their own teams to drive innovation.
AcceleratorFest 2017: What startups really thinkStartupfest
Raymond Luk (Hockeystick.co)
Douglas Soltys (BetaKit)
Come hear the results of Startupfest's exclusive accelerator survey, compiled with Betakit's Douglas Soltys, and find out what accelerator alumni think of the programs they participated in.
In 2015, I ran a workshop at TestBash Brighton entitled "Supercharging Your Bug Reports" (also available in webinar format on the Ministry of Testing Dojo). In that class, I outlined some of the key components of an effective bug report, with the goal of helping testers to become better advocates for problems in their workplace. Fast-forward to 2017, and my world (and beliefs) have changed. I've been working in some fast-paced environments with highly-productive teams, where life moves at a pace which is largely incompatible with "traditional" bug reporting processes.
How do you effectively act as a champion for quality when one of your most visible forms of communication is taken away? In this talk, I'll share stories of my transition: how I had to adapt, the approaches that I chose to take, and evaluate how my 2017 outlook on bug reporting compares to my previous vision.
The document contains quotes and citations from various authors on topics related to design such as communication, problem solving, aesthetics, simplicity, and usability. It discusses how aesthetically pleasing designs can improve productivity and creativity. It also emphasizes that design is about solving problems and that simplicity through removing unnecessary features can lead to innovation. Well-designed products and systems should have intuitive functions and be easy to understand. Usability testing, even with one user, is important for improving websites.
This document discusses empowerment through collaboration in Agile teams. It describes how empowerment was lacking in traditional practices like stand-ups, retrospectives, and sprint reviews due to silos, lack of respect, and a blame culture. The author's team became more empowered by removing silos, valuing opinions, collaborating with customers, and trusting self-organizing teams. Practices like story mapping, 3 Amigos meetings, developer pairing, and collaborative retrospectives helped build relationships and a common understanding within the smaller team.
“Quality at Speed” is Atlassian’s approach to QA, and we are constantly evolving what that means and how it translates to actual dev team processes. Our developers can confidently take on testing activities, while our QA Engineers tackle larger, harder, and bolder challenges. Teams can ship better features, faster, and reach ambitious quality improvement goals.
We'll talk about how our team has embraced this mindset, how this changes our role in dev teams, and the results we want to achieve. We'll cover the different ways that quality can be defined, the importance of fast deployments, and how we work with teams like DevOps, Growth and Customer Insights to help our dev teams and ultimately benefit our users.
Products covered:
JIRA Software, Bitbucket, Bamboo
Developers can't focus only on the details of their code – they have to look at the application from a user's perspective, too. Join Maria Heij from RefinedWiki AB for a journey into the tester's (and user's) mindset. She'll cover knowing how and why your product is used, understanding the intent behind requirements, and product implementations – all aimed at extending your skills and making your add-ons even better.
Maria Heij, Support & Test Manager, RefinedWiki
This document provides guidance on conducting a usability study. It outlines the schedule, expectations for participants, and guidelines for running test sessions. Participants will be divided into groups of 3, with one person acting as the user and two observing. As a user, they will complete tasks while thinking aloud, and observers will take notes on successes, obstacles, and areas of confusion. After each task the group will switch roles. The goal is to evaluate the design and identify ways to improve the user experience.
Couples Counseling for Software Development by Joe StageGROWtalks
This document provides advice for software development teams on improving their product development process through better collaboration between different roles. It recommends that engineers be involved early in the design process to address technical constraints. It also advocates for an iterative process of building minimal prototypes and getting early user feedback, rather than long development cycles. Teams are advised to focus on solving user problems rather than getting attached to specific technical solutions. Overall, the document emphasizes shortening feedback loops through practices like continuous deployment and automated testing.
Collaboration is More Than Communication – JIRA Agile - Xavier MoreraAtlassian
Collaboration is defined as "the action of working with someone to produce or create something." Yet, many confuse communicating with collaborating. True collaboration gives you and your project an edge by aligning efforts towards a clear objective. I'll show how teams can achieve true collaboration with JIRA Agile.
The document discusses several common challenges organizations face when adopting agile and Scrum methodologies. Some of the key challenges mentioned include:
1) Organizational culture and structures not being ready for agile, such as "silos of knowledge" where expertise is concentrated in a few individuals rather than shared across teams.
2) Managers having a "command and control" mindset that does not trust employees and teams to plan and manage their own work.
3) Lacking an overall "agile culture" where goals are shared across the organization and there is transparency and collaboration between teams.
4) The initial adoption of Scrum being difficult, as it requires changes in roles like product owners
Compilation of the common challenges which experts have faced in the real agile environment. Ebook originally published in https://www.knowledgetrain.co.uk/agile/agile-challenges
Code Reviews: the Good, the Bad, and the UglyAmanda Sopkin
Code reviews are an amazing opportunity for teams to help one another grow and maintain a high bar of quality for their code bases overall. Unfortunately this opportunity is often squandered and both giving and receiving these reviews can easily become one of the most frustrating parts of our jobs. Come learn about tactics for improving the process on your team.
This presentation goes into details about impediments, how to identify them, how to create a strategy for, escalate, and ultimately - if not removing them entirely - moving the needle to improve the situation. Apologies for the outdated styling - it's on my backlog to improve it!
The Portal Builder Story: From Hell to Lean, from Zero to Cloud - part 2SOFTENG
Christian Rodriguez gave a presentation on avoiding pitfalls when using Scrum. He discussed how Scrum initially helped his team with steady development and working software, but they later struggled with internal quality issues causing many bugs. He emphasized the importance of internal quality and technical practices to support Scrum. The presentation also covered detecting impediments, improving estimation practices, and adapting to finding more valuable work during a sprint.
A workshop I gave at the South African Scrum Gathering on 9 Sep 2011 (#SGZA) in Johannesburg. It examines why sprint reviews are so often awful and how we need to follow some of the rules of a retrospective if we are to achieve value from the review process
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
Scrum is an agile framework that emphasizes incremental deliveries, quality, continuous improvement, and discovering potential. It consists of sprints, roles like the product owner, scrum master, and cross-functional team. Sprint reviews provide visibility, feedback, and an opportunity for demos. Retrospectives are meetings at the end of each sprint to learn and improve for the next sprint through structured activities like gathering data, generating insights, and deciding on actions. They aim to continuously improve the development process.
The document discusses considering Scrum as a collection of working agreements rather than rigid rules. It suggests identifying patterns from successful past projects and agreeing as a team to implement those patterns. Examples of patterns include short feedback loops, clear priorities and responsibilities, and empowered team members. The document proposes treating Scrum as opportunities to ask powerful questions at each event, such as setting reasonable sprint goals and ensuring work quality.
The document discusses various anti-patterns related to Scrum and Agile practices. It covers anti-patterns for Scrum Masters, Product Owners, specific Scrum events like daily standups, sprint planning, retrospectives, and artifacts like product backlogs. Some of the anti-patterns described include a Scrum Master that acts like a "powerful clerk", a Product Owner that doesn't understand the role and just passes on client words, and teams that treat daily standups as status reporting meetings rather than opportunities for collaboration.
Habits of Highly Successful Agile OrganizationsSelena Delesie
Transitioning to Agile can be challenging. You have probably been told what you're supposed to do and the process everyone will follow. But that's easier said then done, isn't it? You're left wondering how people are supposed to interact and how the organizational culture is going to change.
Do you speak up and help define requirements, or do you sit back and do what you're told?
Do you leave programmers alone so they can get stories completed faster, or do you work closely with them to understand defects?
How do our interactions change with managers and executives?
... and what does it all really look like?
Having been through Agile transitions that have succeeded and failed, Selena will examine the trends that led to different outcomes. You'll be surprised to discover that a successful Agile transition is more than process, techniques and collaboration alone. Join this session to learn the key habits that will transform you and your organization into an Agile success story.
You Cant Be Agile If Your Code Sucks (with 9 Tips For Dev Teams)Peter Gfader
Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers.
Great software engineering teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live.
I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions.
* Why would a company like to be "agile"?
* How can a company achieve that?
* How can you achieve Technical Excellence in your software teams?
* What developer skills are more important than languages, methods or frameworks?
----
What is the difference between Agile and Business Agility? I will use this as an intro exercise.
---
What is "Business Agility"? Why is Agility important? What is Software Craftsmanship?
What can we do to improve our Technical Excellence?
https://beyond-agility.com
At one time or another, every tester hears the dreaded question, “Why didn’t you guys catch these bugs?” We all have some standard responses, and they are most likely true). But what can we learn about our testing when we look beyond the easy answers? Pamela Gillaspie proposes that the key to improving your testing is determining the areas where bugs are slipping past your defenses. For her team, the practice is a lot like basketball. If you group the bugs into zones, you can devise a strategy to cover those zones more effectively. Some zones need a different testing approach than you’ve used; others might reveal a need for closer communication. Join Pamela as she shares her experience as defensive coordinator, addressing the developers’ playbook (What kinds of recurring problems do we see?), trick plays (The user is doing what?), and penalties (That wasn’t in the requirements!).
This document discusses the role of quality assurance (QA) professionals and how they can help organizations build quality into their products and processes. It begins by introducing the speaker, Gabe Garagliano, who has over 20 years of experience in QA roles. It then outlines common QA job roles and asks "Who are we?". The core responsibilities of QA, such as testing at different levels, is then discussed in the section "What do we do?". The document considers how others often view QA and stresses that the value QA provides is finding bugs before customers. It argues that quality should be a habit for the entire organization, not just QA. It provides examples of how tracing bugs back to root causes can help identify process improvements
The document provides information about Richard Cheng and his company NextUp Solutions which offers agile training and coaching. It discusses situational retrospectives and how Richard would facilitate a retrospective for a team that met their goals versus a team that did not complete any work last sprint. It also outlines various retrospective techniques like pluses/deltas, silent writing and dot voting. Finally, it shares tips on evaluating the effectiveness of retrospectives and resources for additional information.
How to survive the zombie scrum apocalypse Mia Horrigan
A couple of years ago Christiaan Verwijs and Johannes Schartau coined the term ‘Zombie-Scrum’. What's it all about?
Well, at first sight Zombie Scrum seems to be normal Scrum. But it lacks a beating heart. The Scrum teams do all the Scrum events but a potential releasable increment is rarely the result of a Sprint. Zombie Scrum teams have a very unambitious definition of what ‘done’ means, and no drive to extend it. They see themselves as a cog in the wheel, unable and unwilling to change anything and have a real impact: I’m only here to code! Zombie Scrum teams show no response to a failed or successful Sprint and also don’t have any intention to improve their situation. Actually nobody cares about this team. The stakeholders have forgotten the existence of this team long time ago.
Zombie Scrum is Scrum, but without the beating heart of working software and its on the rise. This workshop will help you understand how to recognise the symptoms and cuases of Zombie Scrum and what you can do to get started to combat and treat Zombie-Scrum. Knowing what causes Zombie Scrum might help prevent a further outbreak and prevent the apocalypse
Seth Okai - Proving the Benefits of Beta Testing, To B or Not To B - EuroSTAR...TEST Huddle
EuroSTAR Software Testing Conference 2013 presentation on Proving the Benefits of Beta Testing, To B or Not To B by Seth Okai.
See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Craftsmanship is an attitude, not a skillarmincoralic
Craftsmanship is an attitude, not a skill. It takes 10,000 hours to master something, and a craftsman puts their heart into their work. For the author, personal mindset, work ethic, and vision matter more than processes because life is too short for negativity, politics, and overkill of processes. Therefore, the author pledges to do as little as necessary to achieve as much as possible and make work simple, while experimenting with new technologies and techniques to improve skills and make a positive impact.
This document introduces agile automated unit testing. It discusses problems that can occur without testing, such as interruptions, concentration loss, and estimation failures for users, developers, and managers. Manual testing is time-consuming and inaccurate. Agile practices like breaking work into smaller testable units and test-driving development help address these issues by allowing for more accurate estimations, focus, early problem detection, and feedback. Automated unit testing with practices like test-first development and BDD make software development more enjoyable, productive and ensure requirements are met.
Specific ServPoints should be tailored for restaurants in all food service segments. Your ServPoints should be the centerpiece of brand delivery training (guest service) and align with your brand position and marketing initiatives, especially in high-labor-cost conditions.
408-784-7371
Foodservice Consulting + Design
Employment PracticesRegulation and Multinational CorporationsRoopaTemkar
Employment PracticesRegulation and Multinational Corporations
Strategic decision making within MNCs constrained or determined by the implementation of laws and codes of practice and by pressure from political actors. Managers in MNCs have to make choices that are shaped by gvmt. intervention and the local economy.
Org Design is a core skill to be mastered by management for any successful org change.
Org Topologies™ in its essence is a two-dimensional space with 16 distinctive boxes - atomic organizational archetypes. That space helps you to plot your current operating model by positioning individuals, departments, and teams on the map. This will give a profound understanding of the performance of your value-creating organizational ecosystem.
Integrity in leadership builds trust by ensuring consistency between words an...Ram V Chary
Integrity in leadership builds trust by ensuring consistency between words and actions, making leaders reliable and credible. It also ensures ethical decision-making, which fosters a positive organizational culture and promotes long-term success. #RamVChary
Enriching engagement with ethical review processesstrikingabalance
New ethics review processes at the University of Bath. Presented at the 8th World Conference on Research Integrity by Filipa Vance, Head of Research Governance and Compliance at the University of Bath. June 2024, Athens
Sethurathnam Ravi: A Legacy in Finance and LeadershipAnjana Josie
Sethurathnam Ravi, also known as S Ravi, is a distinguished Chartered Accountant and former Chairman of the Bombay Stock Exchange (BSE). As the Founder and Managing Partner of Ravi Rajan & Co. LLP, he has made significant contributions to the fields of finance, banking, and corporate governance. His extensive career includes directorships in over 45 major organizations, including LIC, BHEL, and ONGC. With a passion for financial consulting and social issues, S Ravi continues to influence the industry and inspire future leaders.
A presentation on mastering key management concepts across projects, products, programs, and portfolios. Whether you're an aspiring manager or looking to enhance your skills, this session will provide you with the knowledge and tools to succeed in various management roles. Learn about the distinct lifecycles, methodologies, and essential skillsets needed to thrive in today's dynamic business environment.
Colby Hobson: Residential Construction Leader Building a Solid Reputation Thr...dsnow9802
Colby Hobson stands out as a dynamic leader in the residential construction industry. With a solid reputation built on his exceptional communication and presentation skills, Colby has proven himself to be an excellent team player, fostering a collaborative and efficient work environment.
Ganpati Kumar Choudhary Indian Ethos PPT.pptx, The Dilemma of Green Energy Corporation
Green Energy Corporation, a leading renewable energy company, faces a dilemma: balancing profitability and sustainability. Pressure to scale rapidly has led to ethical concerns, as the company's commitment to sustainable practices is tested by the need to satisfy shareholders and maintain a competitive edge.
1. Too much time spent in these silly “Scrum” meetings
Developers not getting enough work done
Can’t find people at their desks
Productivity is abysmal
Get rid of one Scrum meeting NOW!
10. What went well?
What didn’t go well?
The one best improvement we can
make for next time?
11.
12.
13. Process Product Team
To improve our product and process we must first improve ourselves
Plan, Do, Check, Adjust
Where do we implement the outcome of our retro?
14.
15.
16. This Photo by Unknown Author is licensed under CC BY-SA
17.
18.
19. This Photo by Unknown Author is licensed under CC BY-SA
20.
21.
22. Absence of
trust
Fear of conflict Lack of
commitment
Avoidance of
Accountability
Inattention to
results
23. This Photo by Unknown Author is licensed under CC BY-NC