A Story’s Journey
•Download as PPTX, PDF•
4 likes•1,490 views
A simple demonstration of the journey a User Story takes from idea to production, highlighting the amount of attention it gets ensuring quality and business value.
Report
Share
Report
Share
Recommended
Treinamento TDD
This document discusses test-driven development (TDD) and different types of software testing. It covers the usual TDD workflow of building code and apps, then testing manually. Over time, as changes become painful, testing is integrated earlier in the process. The document discusses unit testing, the test pyramid with more unit tests than other types of tests, and using TDD to influence class design in object-oriented systems. It provides examples of the Jasmine testing framework and recommends mocking roles rather than objects to isolate dependencies when testing.
Commitment or Sheer Madness: How we're Pushing Weekly App Updates to Millions...
Commitment or Sheer Madness: How we're Pushing Weekly App Updates to Millions of Users | Oliver Loeffler, Julian Erhardt
Invite the tester to the party
This slide deck was used at the Global Scrum Gathering in Prague in 2015. The deck provides inspiration on:
* How to make the tester part of the Development Team
* How to eliminate the need for "Quality Control"
* Foster collaboration within the team.
Agile Simplified
The document discusses traditional software development versus agile software development. Traditional development involves distinct sequential stages planned upfront, while agile development is iterative, incremental and collaborative. Agile values individuals, working software, customer collaboration and responding to change over processes, documentation, contracts and plans. Common agile methodologies mentioned include eXtreme Programming, Scrum, Feature Driven Development and Test Driven Development.
Stc chandan patary_ua_testing _ stc
This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.
Scrum for Video Game Development
This document provides an overview of using Scrum for video game development. It discusses how Agile and Scrum practices can help video game teams iterate quickly to find the fun, deliver working features frequently, and get early feedback. The key aspects of Scrum covered include sprint planning, daily standups, sprint reviews, retrospectives, and managing product and sprint backlogs. The document advocates adopting Scrum to improve quality, engage the team, and better address uncertainty compared to traditional "waterfall" development.
Inspecting and adapting your product
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 model in game development
The document discusses how the Scrum framework can be applied to game development. It explains that Scrum is an agile development process where self-organizing teams work in sprints to deliver working software every 2-4 weeks based on priorities set by business stakeholders. It then outlines the typical Scrum ceremonies like sprint planning, daily stand-ups, and retrospectives. Finally, it poses several questions about how requirements, roadmaps, designers, testers, bugs, changes to requirements, and large team sizes are handled when using Scrum for game development projects.
Recommended
Treinamento TDD
This document discusses test-driven development (TDD) and different types of software testing. It covers the usual TDD workflow of building code and apps, then testing manually. Over time, as changes become painful, testing is integrated earlier in the process. The document discusses unit testing, the test pyramid with more unit tests than other types of tests, and using TDD to influence class design in object-oriented systems. It provides examples of the Jasmine testing framework and recommends mocking roles rather than objects to isolate dependencies when testing.
Commitment or Sheer Madness: How we're Pushing Weekly App Updates to Millions...
Commitment or Sheer Madness: How we're Pushing Weekly App Updates to Millions of Users | Oliver Loeffler, Julian Erhardt
Invite the tester to the party
This slide deck was used at the Global Scrum Gathering in Prague in 2015. The deck provides inspiration on:
* How to make the tester part of the Development Team
* How to eliminate the need for "Quality Control"
* Foster collaboration within the team.
Agile Simplified
The document discusses traditional software development versus agile software development. Traditional development involves distinct sequential stages planned upfront, while agile development is iterative, incremental and collaborative. Agile values individuals, working software, customer collaboration and responding to change over processes, documentation, contracts and plans. Common agile methodologies mentioned include eXtreme Programming, Scrum, Feature Driven Development and Test Driven Development.
Stc chandan patary_ua_testing _ stc
This document discusses ways to improve product development cycles through effective user acceptance testing and engagement. It describes how one organization achieved targets like reducing production to release cycles from 15 to 10 months by having product owners actively participate in validation testing. Stories from the trenches are shared about having product engineers directly involved in validation testing to better represent customer needs. Exploratory "monkey" testing of system boundaries is also discussed. The key takeaway is how design thinking principles were applied, like creating focus groups, prototyping solutions, and getting faster customer feedback through various iterative testing approaches.
Scrum for Video Game Development
This document provides an overview of using Scrum for video game development. It discusses how Agile and Scrum practices can help video game teams iterate quickly to find the fun, deliver working features frequently, and get early feedback. The key aspects of Scrum covered include sprint planning, daily standups, sprint reviews, retrospectives, and managing product and sprint backlogs. The document advocates adopting Scrum to improve quality, engage the team, and better address uncertainty compared to traditional "waterfall" development.
Inspecting and adapting your product
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 model in game development
The document discusses how the Scrum framework can be applied to game development. It explains that Scrum is an agile development process where self-organizing teams work in sprints to deliver working software every 2-4 weeks based on priorities set by business stakeholders. It then outlines the typical Scrum ceremonies like sprint planning, daily stand-ups, and retrospectives. Finally, it poses several questions about how requirements, roadmaps, designers, testers, bugs, changes to requirements, and large team sizes are handled when using Scrum for game development projects.
Scrum Quick Overview
The document describes the Scrum process for developing software using roles like Product Owner, Scrum Master, Developers, and Testers. It outlines how the Product Owner prioritizes a backlog of features, Developers work in sprints to complete the highest priority tasks, and there are daily stand-ups and sprint demos to track progress and provide feedback.
“High performance teams" - Marco Cecconi
This document discusses high performance teams and provides tips for building them. It notes that the best programmers can be 10 times more productive than the worst. Highly successful companies like Instagram and Stack Overflow started small but grew rapidly by focusing on optimization and continual improvement. Negative feedback should be about ideas and code, not people, and delivered privately. Teams perform best when they work together toward shared goals, embrace change, and celebrate each other's successes. Simplicity is important to minimize work.
The perfect PR
This document provides tips for creating effective pull requests. It recommends that submitters review their own code, write clear titles and descriptions, use good commit messages, and keep code changes short. Reviewers should provide constructive feedback, ask questions, and review in short sessions. Tools like code analysis and checklists can help reviewers. Pair programming and early feedback can improve code quality before a pull request. The goal is for teams to work collaboratively through the pull request process.
Become a Quality Enabler
Instead of being just another cost center for a customer where you develop what you're told, how can you become proactive by understanding the business requirement and truly being a Quality Enabler? Xian Tharindra shares some great insights on this
Tips n' Tricks - Sprint Review
Tips and tricks for doing effective sprint reviews for any application of an agile or scrum framework.
Developer 2.0 - Redefine the Role of Developer to Achieve Success for All : P...
Gone are the days where developer was responsible for just writing clean code. Traditional definition of developer affects the individual developers more than it affects the organization. The developer tends to concentrate on getting better at just the area of coding and ends up not learning the nuances of building a successful product. As a Developer 2.0, the developer performs all of the following roles.
1. Coder
2. Devil's advocate
3. Code Reviewer
A developer can work in multiple stories but cannot do more than one of the above tasks for the same story. For example, the same person cannot be both the coder and Devil's advocate. A team at Gainsight worked with this improved definition of developers and saw higher product velocity, better awareness about product and increased responsiveness to issues. This session will take the audience through the improved definition of the role of developer and present some thought-provoking questions to the audience to make them realize that the traditional definition of role of developer is just not enough.
Developer 2.0 redefine the role of developer to achieve success for all
The document proposes redefining the role of developers to Developer 2.0, which involves developers taking on responsibilities beyond just coding such as authoring test cases, reviewing solutions, and acting as a devil's advocate. This new model aims to achieve success for all by having developers ensure solutions meet requirements and end users' needs through additional quality checks. The document asks how organizations can implement this new developer role and shares learnings from having developers take on more accountability.
A Test Manifesto 2014.03.26
Last year we were challenged to build an agile test team to work in different products and technologies for 8 distributed teams from 3 to 7 people. We had to break with legacy assumptions on how testing should be enacted while keeping company policies. And most of all, we had to make sure everyone is enabled to do the best possible job.
Enabling a team is about motivation, trust and simplifying decision making processes. The test team as a whole has to scale and fit for multiple scenarios and projects. Every team member had a different background and needs so no policies would really apply to all. Or worst, we would be spending time twisting the rules to fit each case.
First, we decided to coordinate as a guild. Second, we issued this Test Manifest as a declaration of purpose and discipline.
Sprint Review and Planning Template
The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.
Big feature - small sprint
My talk presentation from SQA Days 21 conference.
During last two years I've been working in Agile teams and quite often have come across the situation when the feature is pretty big, but they still want to release it at the end of the sprint. That is in spite of the fact, that there is a great risk of violation of the timing and poor product quality.
So what should we, quality guards, do when eventually everything depends on us?
My report presents the analysis of the development stages from the testing point of view in such a difficult situation and provides tips for success.
Use Scrum and Continuous Delivery to innovate like crazy!
How often do you release your product to your end users?
How often do your end users see and use your product?
Why is Continuous Delivery helping us to focus on business value?
How can Scrum help us to be innovative?
These and more questions are going to be answered in this talk about Scrum with Continuous Delivery.
Companies and organizations struggle with bureaucracy, dependencies, silo thinking, human behavior and technical problems and loose the real goal. Continuous Delivery being more than a technical practice can work with Scrum and changes the way we write software completely.
Let’s see how we can combine those and delight our customers with a constant flow of features and happiness.
Target audience: Experienced Scrum Practitioners that would like to take the next step to delight their customers
3. Armine - retrospective and grooming
This document summarizes an Agile meeting that included a sprint retrospective and backlog refinement. The sprint retrospective allowed the team to reflect on what went well and could be improved in the previous sprint. They created an action plan for improvements. The backlog refinement involved prioritizing product backlog items, estimating work, and decomposing epics into user stories to prepare for future sprints. The goal was to continuously improve processes and have the product backlog ready for upcoming sprint planning meetings.
Developer testing webinar
Why can't programmers test and what can you do about it?
Do your developers take part in testing tasks?
Fact! [Most] developers are not good testers.
So how can we help then out?
Full webinar recording here:
https://www.practitest.com/qa-learningcenter/webinars/developer-testing-webinar/
Project Management Growth Practices
This document discusses project management growth practices and contains recommendations in several areas:
1) Be available to your team to reduce dependencies, optimize around available resources which may be constrained by project management, engineering or the team itself.
2) Improve processes by setting up project management software, using demos to drive progress, and dedicating special days to areas like bugs, polish or internal tools.
3) Anticipate risks and have mitigation plans to determine if risks are real problems, and have rollout or other plans to address risks like stability issues.
Testing & Scrum
The document discusses organizing testing within the Scrum framework. It provides key messages: 1) everyone is a tester, 2) testing is infused into everything, not isolated, 3) some testing can be placed outside the Scrum team if multiple teams exist, and 4) complexity determines who performs different types of testing. It also discusses test ownership, automation, regression testing, and defines types of testing like isolated, contract, and integration testing. The overall message is that testing is integral to Scrum and should involve the whole team, while allowing for specialized testing roles.
Dedicated QA person in scrum team
A dedicated QA person in a Scrum team can help achieve quality by focusing solely on quality assurance tasks. The document describes a scenario where one Scrum team with a dedicated QA person delivered a higher quality product than other teams without dedicated QA. Having a QA specialist allows the person to fully concentrate on test case development, automation, and testing without also having development responsibilities. This dedicated role is needed because quality assurance requires significant mental effort that may not get fully addressed if distributed among generalist team members with other priorities.
The New Agile
We know that agile methodologies work at the team level, and there is now even an effort to scale into whole organizations.
There is a clear reason behind this: we found ways to improve performance, by analyzing situations better, and making better decision. Every organization wants to apply this in every level. Like in the late 90s, new ideas are coming out that challenge the way we think, and this time they don't just answer development. Ideas like Beyond Budgeting, Lean Startup, Cynefin, Real Options, Feature Injection, SAFe, Design Thinking, #NoEstimates, Cost of Delay and others are spreading out, and while we know not all will last, you never know which might fit your situation. In this session, I'll give a summary of what's hot around the agile world, with some criticism and application in the real world. 13 years after the original manifesto, organizations start to experiment again. I always wished I was there when the first conversations took place. I encourage you to join in on current conversations. Let's start.
QA and scrum
Recently I was asked to to a presentation presentation at University of Cape Town entitled QA and SCRUM. This made very little sense to me but it did substantiate my belief that the understanding of agile development is generally very superficial ...
Move test planning before implementation
This document discusses improving the software development workflow by moving test planning earlier. It proposes defining acceptance criteria during feature planning to help test cases be "born" earlier. This would help avoid misunderstandings later on. It also advocates for more collaboration through daily stand-ups to catch issues early and learn from failures. The goal is to reduce bottlenecks and workload by improving planning, collaboration, and shifting left testing activities.
Agile Testing
This document discusses how testers can contribute in an agile environment. It begins by defining agile testing as testing done incrementally and in parallel with development. Testers should have a mindset of collaboration, communication, ongoing planning, and viewing failures as opportunities to learn.
Testers can contribute in agile events like planning, refinement, and retrospectives. They can help write user stories and acceptance criteria. They also help determine if work is done by demonstrating increments and providing feedback. Defects are viewed as unfinished work rather than managed in a separate phase.
The document discusses metrics that matter like working software, velocity trends, and release burndowns. It emphasizes documentation should be "just enough" and
Ditch Scrum Talk at Agile Prague 2019
This document discusses the key elements of Scrum, including roles, artifacts, and events. It emphasizes that the main purposes of Scrum are to maximize value, make Scrum work for the organization, and help teams collaborate effectively. It stresses the importance of empirical process control and learning cycles in Scrum, with transparency, inspection, and adaptation at different levels. The document concludes that the biggest enemy of Scrum is not using it properly and failing to accept and apply lessons learned.
[Webinar] Introducing Feature Management
Launching a new feature is a risky proposition. Even the most well designed and researched features can initially tank your applications' performance and business metrics. Rolling back a poor performing feature can be time consuming and costly. However, it doesn't have to be. Implementing feature management and experimentation into your development lifecycle can help your team reduce risk when launching new features. Feature management isn't just for developers. Product managers can attend this webinar to discover how implementing feature management and experimentation can help prove impact across the product cycle.
Attend this webinar to learn:
- Best practices for launching products with velocity and quality using feature management
- Guidelines for limiting your blast radius when rolling out new or redesigned features
- How using experimentation and feature management in tandem enable you to iterate faster and ship better performing products
More Related Content
What's hot
Scrum Quick Overview
The document describes the Scrum process for developing software using roles like Product Owner, Scrum Master, Developers, and Testers. It outlines how the Product Owner prioritizes a backlog of features, Developers work in sprints to complete the highest priority tasks, and there are daily stand-ups and sprint demos to track progress and provide feedback.
“High performance teams" - Marco Cecconi
This document discusses high performance teams and provides tips for building them. It notes that the best programmers can be 10 times more productive than the worst. Highly successful companies like Instagram and Stack Overflow started small but grew rapidly by focusing on optimization and continual improvement. Negative feedback should be about ideas and code, not people, and delivered privately. Teams perform best when they work together toward shared goals, embrace change, and celebrate each other's successes. Simplicity is important to minimize work.
The perfect PR
This document provides tips for creating effective pull requests. It recommends that submitters review their own code, write clear titles and descriptions, use good commit messages, and keep code changes short. Reviewers should provide constructive feedback, ask questions, and review in short sessions. Tools like code analysis and checklists can help reviewers. Pair programming and early feedback can improve code quality before a pull request. The goal is for teams to work collaboratively through the pull request process.
Become a Quality Enabler
Instead of being just another cost center for a customer where you develop what you're told, how can you become proactive by understanding the business requirement and truly being a Quality Enabler? Xian Tharindra shares some great insights on this
Tips n' Tricks - Sprint Review
Tips and tricks for doing effective sprint reviews for any application of an agile or scrum framework.
Developer 2.0 - Redefine the Role of Developer to Achieve Success for All : P...
Gone are the days where developer was responsible for just writing clean code. Traditional definition of developer affects the individual developers more than it affects the organization. The developer tends to concentrate on getting better at just the area of coding and ends up not learning the nuances of building a successful product. As a Developer 2.0, the developer performs all of the following roles.
1. Coder
2. Devil's advocate
3. Code Reviewer
A developer can work in multiple stories but cannot do more than one of the above tasks for the same story. For example, the same person cannot be both the coder and Devil's advocate. A team at Gainsight worked with this improved definition of developers and saw higher product velocity, better awareness about product and increased responsiveness to issues. This session will take the audience through the improved definition of the role of developer and present some thought-provoking questions to the audience to make them realize that the traditional definition of role of developer is just not enough.
Developer 2.0 redefine the role of developer to achieve success for all
The document proposes redefining the role of developers to Developer 2.0, which involves developers taking on responsibilities beyond just coding such as authoring test cases, reviewing solutions, and acting as a devil's advocate. This new model aims to achieve success for all by having developers ensure solutions meet requirements and end users' needs through additional quality checks. The document asks how organizations can implement this new developer role and shares learnings from having developers take on more accountability.
A Test Manifesto 2014.03.26
Last year we were challenged to build an agile test team to work in different products and technologies for 8 distributed teams from 3 to 7 people. We had to break with legacy assumptions on how testing should be enacted while keeping company policies. And most of all, we had to make sure everyone is enabled to do the best possible job.
Enabling a team is about motivation, trust and simplifying decision making processes. The test team as a whole has to scale and fit for multiple scenarios and projects. Every team member had a different background and needs so no policies would really apply to all. Or worst, we would be spending time twisting the rules to fit each case.
First, we decided to coordinate as a guild. Second, we issued this Test Manifest as a declaration of purpose and discipline.
Sprint Review and Planning Template
The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.
Big feature - small sprint
My talk presentation from SQA Days 21 conference.
During last two years I've been working in Agile teams and quite often have come across the situation when the feature is pretty big, but they still want to release it at the end of the sprint. That is in spite of the fact, that there is a great risk of violation of the timing and poor product quality.
So what should we, quality guards, do when eventually everything depends on us?
My report presents the analysis of the development stages from the testing point of view in such a difficult situation and provides tips for success.
Use Scrum and Continuous Delivery to innovate like crazy!
How often do you release your product to your end users?
How often do your end users see and use your product?
Why is Continuous Delivery helping us to focus on business value?
How can Scrum help us to be innovative?
These and more questions are going to be answered in this talk about Scrum with Continuous Delivery.
Companies and organizations struggle with bureaucracy, dependencies, silo thinking, human behavior and technical problems and loose the real goal. Continuous Delivery being more than a technical practice can work with Scrum and changes the way we write software completely.
Let’s see how we can combine those and delight our customers with a constant flow of features and happiness.
Target audience: Experienced Scrum Practitioners that would like to take the next step to delight their customers
3. Armine - retrospective and grooming
This document summarizes an Agile meeting that included a sprint retrospective and backlog refinement. The sprint retrospective allowed the team to reflect on what went well and could be improved in the previous sprint. They created an action plan for improvements. The backlog refinement involved prioritizing product backlog items, estimating work, and decomposing epics into user stories to prepare for future sprints. The goal was to continuously improve processes and have the product backlog ready for upcoming sprint planning meetings.
Developer testing webinar
Why can't programmers test and what can you do about it?
Do your developers take part in testing tasks?
Fact! [Most] developers are not good testers.
So how can we help then out?
Full webinar recording here:
https://www.practitest.com/qa-learningcenter/webinars/developer-testing-webinar/
Project Management Growth Practices
This document discusses project management growth practices and contains recommendations in several areas:
1) Be available to your team to reduce dependencies, optimize around available resources which may be constrained by project management, engineering or the team itself.
2) Improve processes by setting up project management software, using demos to drive progress, and dedicating special days to areas like bugs, polish or internal tools.
3) Anticipate risks and have mitigation plans to determine if risks are real problems, and have rollout or other plans to address risks like stability issues.
Testing & Scrum
The document discusses organizing testing within the Scrum framework. It provides key messages: 1) everyone is a tester, 2) testing is infused into everything, not isolated, 3) some testing can be placed outside the Scrum team if multiple teams exist, and 4) complexity determines who performs different types of testing. It also discusses test ownership, automation, regression testing, and defines types of testing like isolated, contract, and integration testing. The overall message is that testing is integral to Scrum and should involve the whole team, while allowing for specialized testing roles.
Dedicated QA person in scrum team
A dedicated QA person in a Scrum team can help achieve quality by focusing solely on quality assurance tasks. The document describes a scenario where one Scrum team with a dedicated QA person delivered a higher quality product than other teams without dedicated QA. Having a QA specialist allows the person to fully concentrate on test case development, automation, and testing without also having development responsibilities. This dedicated role is needed because quality assurance requires significant mental effort that may not get fully addressed if distributed among generalist team members with other priorities.
The New Agile
We know that agile methodologies work at the team level, and there is now even an effort to scale into whole organizations.
There is a clear reason behind this: we found ways to improve performance, by analyzing situations better, and making better decision. Every organization wants to apply this in every level. Like in the late 90s, new ideas are coming out that challenge the way we think, and this time they don't just answer development. Ideas like Beyond Budgeting, Lean Startup, Cynefin, Real Options, Feature Injection, SAFe, Design Thinking, #NoEstimates, Cost of Delay and others are spreading out, and while we know not all will last, you never know which might fit your situation. In this session, I'll give a summary of what's hot around the agile world, with some criticism and application in the real world. 13 years after the original manifesto, organizations start to experiment again. I always wished I was there when the first conversations took place. I encourage you to join in on current conversations. Let's start.
QA and scrum
Recently I was asked to to a presentation presentation at University of Cape Town entitled QA and SCRUM. This made very little sense to me but it did substantiate my belief that the understanding of agile development is generally very superficial ...
Move test planning before implementation
This document discusses improving the software development workflow by moving test planning earlier. It proposes defining acceptance criteria during feature planning to help test cases be "born" earlier. This would help avoid misunderstandings later on. It also advocates for more collaboration through daily stand-ups to catch issues early and learn from failures. The goal is to reduce bottlenecks and workload by improving planning, collaboration, and shifting left testing activities.
Agile Testing
This document discusses how testers can contribute in an agile environment. It begins by defining agile testing as testing done incrementally and in parallel with development. Testers should have a mindset of collaboration, communication, ongoing planning, and viewing failures as opportunities to learn.
Testers can contribute in agile events like planning, refinement, and retrospectives. They can help write user stories and acceptance criteria. They also help determine if work is done by demonstrating increments and providing feedback. Defects are viewed as unfinished work rather than managed in a separate phase.
The document discusses metrics that matter like working software, velocity trends, and release burndowns. It emphasizes documentation should be "just enough" and
What's hot (20)
Developer 2.0 - Redefine the Role of Developer to Achieve Success for All : P...
Developer 2.0 - Redefine the Role of Developer to Achieve Success for All : P...
Developer 2.0 redefine the role of developer to achieve success for all
Developer 2.0 redefine the role of developer to achieve success for all
Use Scrum and Continuous Delivery to innovate like crazy!
Use Scrum and Continuous Delivery to innovate like crazy!
Similar to A Story’s Journey
Ditch Scrum Talk at Agile Prague 2019
This document discusses the key elements of Scrum, including roles, artifacts, and events. It emphasizes that the main purposes of Scrum are to maximize value, make Scrum work for the organization, and help teams collaborate effectively. It stresses the importance of empirical process control and learning cycles in Scrum, with transparency, inspection, and adaptation at different levels. The document concludes that the biggest enemy of Scrum is not using it properly and failing to accept and apply lessons learned.
[Webinar] Introducing Feature Management
Launching a new feature is a risky proposition. Even the most well designed and researched features can initially tank your applications' performance and business metrics. Rolling back a poor performing feature can be time consuming and costly. However, it doesn't have to be. Implementing feature management and experimentation into your development lifecycle can help your team reduce risk when launching new features. Feature management isn't just for developers. Product managers can attend this webinar to discover how implementing feature management and experimentation can help prove impact across the product cycle.
Attend this webinar to learn:
- Best practices for launching products with velocity and quality using feature management
- Guidelines for limiting your blast radius when rolling out new or redesigned features
- How using experimentation and feature management in tandem enable you to iterate faster and ship better performing products
Scrum or Not? Presentation
This slide deck is used for my "Scrum or Not?" talk I have been doing at global agile communities and conferenes
201811 agile slovenia talk ditch scrum
Thanks to HBR, McKinsey and more of those, Agile has become mainstream but is it Agile? I see Agile being used as a synonym of Scrum even though Agile is more of an umbrella where Scrum is just one flavour of getting there. Many inquiries show that Scrum is the most used Agile flavour in the world and I’m here to tell you to stop that movement unless you truly mean it.
Let me guide you through some basic elements and help you evaluate if you and your organisation should ditch Scrum or not. Help you recognise if you are truly a Scrum Master or rather a Scrum Novice. And much more.
How to Get a Product Manager Job: January 28, 2014
This document provides information on how to get a job as a product manager. It discusses the typical responsibilities of a product manager, which include understanding customers, developing requirements, prioritizing resources, serving as the launch lead, and collecting feedback. The hiring process is outlined, emphasizing the importance of a relevant resume. Interview preparation is advised, including practicing situational and behavioral questions. Common reasons for failing an interview like lacking structure or analytical skills are also presented. The document concludes by discussing career progression as a product manager.
How to Get a Product Manager Job
This document provides an overview of how to get a job as a product manager. It discusses the typical responsibilities of a PM, which include understanding customers, developing requirements, prioritizing resources, serving as the launch lead, and collecting feedback. The hiring process is explained, with advice about optimizing resumes and interviews. Key interview skills are emphasized, such as using the CIRCLES method to structure responses. Different career paths for PMs are also outlined.
Scrum/XP using Team System (devLink & Agile 2009)
This is the slide deck from my devLink 09 and Agile 2009 conference presentations. I skipped the Scrum intro slides at Agile 2009 since most of the crowd already had the basics down. This was nainly a demo so for over half the presentation I was not using slides.
Product Development using Agile Teams: What? Why? How?
The document discusses an agile training presentation about empowering product development teams through agile principles and practices. It covers:
1. The 3 main roles in agile - product manager, scrum master, and self-organizing cross-functional team.
2. The 4 core agile ceremonies - planning, daily stand-ups, sprint reviews, and retrospectives.
3. The 3 primary artifacts - product backlog, sprint backlog, and burn-down charts.
The presentation provides details on each of the roles, ceremonies, and artifacts to help explain how agile practices can help teams deliver customer value through collaboration, frequent delivery, and adapting to change.
Scrum Foundations
The document provides information on agile frameworks like Scrum. It discusses why agile is useful for IT projects, highlighting problems with traditional approaches like high failure rates. Scrum is presented as a lightweight agile framework with core elements like transparency, collaboration and simplicity. An overview of Scrum roles, events, artifacts and principles is given. The document also covers topics like iterative development, value-based prioritization and timeboxing. Visuals of a Scrum board and diagrams are included to illustrate Scrum processes and frameworks.
How I see the role of Product Management
The document discusses the role of the product manager in Scrum product development. It describes the product manager as the product owner responsible for articulating the product vision. Key activities of the product manager in Scrum include maintaining the product backlog and requirements, collaborating with the development team in sprint planning and reviews, and balancing strategic and tactical tasks. The document presents benefits of this approach as improved product quality, speed to market, and customer satisfaction.
Agile SharePoint Development With Scrum
Provide an introduction to Agile development using Scrum and discuss how the iterative approach to development helps the customer to get the solution they want. Look at how this approach works when applied to SharePoint projects, how it helps leverage more of the core platform and focuses effort on the biggest value areas. We will look at the challenges this brings to your development team by doing early integration, dealing with upgrades and changes and understand how addressing the hard things early is the right approach. We will also discuss how Scrum gives visibility of the project and brings both good and bad news. How getting customer engagement is the primary challenge and how the flexible approach is often at odds with the way work is contracted.
Dietmar Strasser - Traditional QA meets Agile Development
EuroSTAR Software Testing Conference 2008 presentation on Traditional QA meets Agile Development by Dietmar Strasser. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Mike Cottmeyer - How to Own a Really big complex Product
This document discusses how to manage product ownership at scale for complex, multi-team products. It notes that product owners do not scale effectively and common strategies like assigning one product owner per team do not work. Instead, it advocates developing organizational capabilities for business analysis, engineering, and leadership/coordination. These capabilities can be expressed differently depending on the level of scale, such as through product owner teams, Scrum of Scrums, integration teams, and alignment of culture. The key is delivering value across multiple teams by thinking holistically about capabilities rather than focusing on individual roles.
Martijn Beijk & Charles Goodall
This document discusses how experiment-driven product development works at Optimizely and best practices for organizations. It provides analysis of over 100,000 experiments from 1,000 companies to identify best practices. These include:
- Running thousands of small experiments continuously to learn and improve products.
- Using feature flags to limit risks when rolling out new features and conduct staged rollouts.
- Validating ideas with "painted door" experiments before building them out.
- Measuring business impacts through A/B testing and iterative adjustments.
Scrum소개
The document introduces Scrum and its roles, artifacts, and activities. It discusses the Scrum process including sprint planning, daily standups, sprint demos, and retrospectives. It emphasizes that teams should strictly follow Scrum practices like having a product backlog, sprint backlog, and definition of done to achieve the benefits of an agile framework. Failing to properly implement Scrum can undermine its effectiveness.
Plan.pptx
The document outlines the product workflow process including research, development, marketing, sales, and integration & testing. It describes an agile methodology used including sprints, product backlogs, and a sprint process model. Key advantages of the agile approach are also listed such as transparency, accuracy, fast development, and less testing.
Testers in an agile world
Slide deck of the Testers in an Agile World workshop, covering the mindset, role, expectations and practices of a tester of the agile kind.
Product Owner
What is a Scrum Product Owner anyway? Time to find out what exactly they do and how the job is different than a project manager.
ERP Implementation Using Agile Project Management with Scrum
This document discusses using Agile project management and Scrum for ERP implementation. It introduces ERP systems and Agile project management approaches like Scrum. Scrum uses product owners, development teams, and scrum masters along with artifacts like product backlogs and sprints. Key Scrum ceremonies include sprint planning, daily stand-ups, and sprint reviews. Using Scrum for ERP implementation provides benefits like transparency, inspection, adaptation and aligning with Agile values.
Expo qa15 Keynote
The document discusses the need for a holistic view when scaling agile organizations. It covers topics like the problems of scaling agile, what constitutes a scaled agile organization, and how individuals can contribute to its success. The keynote speaker advocates adopting a networked structure over hierarchical ones and emphasizes quality being everyone's responsibility through cross-functional teams and a whole product focus.
Similar to A Story’s Journey (20)
How to Get a Product Manager Job: January 28, 2014
How to Get a Product Manager Job: January 28, 2014
Product Development using Agile Teams: What? Why? How?
Product Development using Agile Teams: What? Why? How?
Dietmar Strasser - Traditional QA meets Agile Development
Dietmar Strasser - Traditional QA meets Agile Development
Mike Cottmeyer - How to Own a Really big complex Product
Mike Cottmeyer - How to Own a Really big complex Product
ERP Implementation Using Agile Project Management with Scrum
ERP Implementation Using Agile Project Management with Scrum
Recently uploaded
How to Predict Vendor Bill Product in Odoo 17
This slide will guide us through the process of predicting vendor bill products based on previous purchases from the vendor in Odoo 17.
A Visual Guide to 1 Samuel | A Tale of Two Hearts
These slides walk through the story of 1 Samuel. Samuel is the last judge of Israel. The people reject God and want a king. Saul is anointed as the first king, but he is not a good king. David, the shepherd boy is anointed and Saul is envious of him. David shows honor while Saul continues to self destruct.
BIOLOGY NATIONAL EXAMINATION COUNCIL (NECO) 2024 PRACTICAL MANUAL.pptx
Practical manual for National Examination Council, Nigeria.
Contains guides on answering questions on the specimens provided
How to deliver Powerpoint Presentations.pptx
"How to make and deliver dynamic presentations by making it more interactive to captivate your audience attention"
Leveraging Generative AI to Drive Nonprofit Innovation
In this webinar, participants learned how to utilize Generative AI to streamline operations and elevate member engagement. Amazon Web Service experts provided a customer specific use cases and dived into low/no-code tools that are quick and easy to deploy through Amazon Web Service (AWS.)
Traditional Musical Instruments of Arunachal Pradesh and Uttar Pradesh - RAYH...
Traditional Musical Instruments of Arunachal Pradesh and Uttar Pradesh
Benner "Expanding Pathways to Publishing Careers"
This presentation was provided by Rebecca Benner, Ph.D., of the American Society of Anesthesiologists, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.
skeleton System.pdf (skeleton system wow)
🔥🔥🔥🔥🔥🔥🔥🔥🔥
إضغ بين إيديكم من أقوى الملازم التي صممتها
ملزمة تشريح الجهاز الهيكلي (نظري 3)
💀💀💀💀💀💀💀💀💀💀
تتميز هذهِ الملزمة بعِدة مُميزات :
1- مُترجمة ترجمة تُناسب جميع المستويات
2- تحتوي على 78 رسم توضيحي لكل كلمة موجودة بالملزمة (لكل كلمة !!!!)
#فهم_ماكو_درخ
3- دقة الكتابة والصور عالية جداً جداً جداً
4- هُنالك بعض المعلومات تم توضيحها بشكل تفصيلي جداً (تُعتبر لدى الطالب أو الطالبة بإنها معلومات مُبهمة ومع ذلك تم توضيح هذهِ المعلومات المُبهمة بشكل تفصيلي جداً
5- الملزمة تشرح نفسها ب نفسها بس تكلك تعال اقراني
6- تحتوي الملزمة في اول سلايد على خارطة تتضمن جميع تفرُعات معلومات الجهاز الهيكلي المذكورة في هذهِ الملزمة
واخيراً هذهِ الملزمة حلالٌ عليكم وإتمنى منكم إن تدعولي بالخير والصحة والعافية فقط
كل التوفيق زملائي وزميلاتي ، زميلكم محمد الذهبي 💊💊
🔥🔥🔥🔥🔥🔥🔥🔥🔥
Bossa N’ Roll Records by Ismael Vazquez.
Bossa N Roll Records presentation by Izzy Vazquez for Music Retail and Distribution class at Full Sail University
Gender and Mental Health - Counselling and Family Therapy Applications and In...
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
Jemison, MacLaughlin, and Majumder "Broadening Pathways for Editors and Authors"
Jemison, MacLaughlin, and Majumder "Broadening Pathways for Editors and Authors"National Information Standards Organization (NISO)
This presentation was provided by Racquel Jemison, Ph.D., Christina MacLaughlin, Ph.D., and Paulomi Majumder. Ph.D., all of the American Chemical Society, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 9 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2024-2025 - ...
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 9 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2024-2025 - ...Nguyen Thanh Tu Collection
https://app.box.com/s/tacvl9ekroe9hqupdnjruiypvm9rdaneRecently uploaded (20)
NEWSPAPERS - QUESTION 1 - REVISION POWERPOINT.pptx
NEWSPAPERS - QUESTION 1 - REVISION POWERPOINT.pptx
BIOLOGY NATIONAL EXAMINATION COUNCIL (NECO) 2024 PRACTICAL MANUAL.pptx
BIOLOGY NATIONAL EXAMINATION COUNCIL (NECO) 2024 PRACTICAL MANUAL.pptx
Leveraging Generative AI to Drive Nonprofit Innovation
Leveraging Generative AI to Drive Nonprofit Innovation
Traditional Musical Instruments of Arunachal Pradesh and Uttar Pradesh - RAYH...
Traditional Musical Instruments of Arunachal Pradesh and Uttar Pradesh - RAYH...
Gender and Mental Health - Counselling and Family Therapy Applications and In...
Gender and Mental Health - Counselling and Family Therapy Applications and In...
Jemison, MacLaughlin, and Majumder "Broadening Pathways for Editors and Authors"
Jemison, MacLaughlin, and Majumder "Broadening Pathways for Editors and Authors"
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 9 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2024-2025 - ...
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 9 CẢ NĂM - GLOBAL SUCCESS - NĂM HỌC 2024-2025 - ...
A Story’s Journey
- 1. A Story’s Journey Obinna Duru April 2017
- 2. Actors Product Owner Tester Developer Dev In Test Scrum Master The Business
- 3. ‣ New Business Idea Product Owner The Business
- 4. ‣ PO breaks it down Product Owner The Business
- 6. ‣ T-Shirt Sizing Product Owner TesterDeveloper Small Medium Large
- 7. ‣ Refinement Session Product Owner The Business Tester Developer Dev In Test 5 3 8 13 1 2 Priority Low High Scrum Master PO & Dev Team ?
- 8. ‣ Sprint Planning Product Owner The Business TesterDeveloper Dev In Test 5 3 8 13 1 2 Scrum Master Sprint 1
- 9. ‣ INVEST session Product Owner Developer Dev In Test Tester
- 10. ‣ Development Developer Dev In Test Tester Functional Code Automated Test Automated Test
- 11. ‣ Story Demo Product Owner Developer Dev In Test Tester
- 12. ‣ Sprint Demo Product Owner The Business Scrum Master Developer Tester Dev In Test
Editor's Notes
- The business has an idea Something new they want to build The invite the PO and have a good chat about it The PO confirms she has just the right team for the job Then she makes her notes and leaves
- The PO goes through the idea in great detail and breaks it down to smaller epics/stories Adding Initial description of each story And High level acceptance criteria
- PO sits with a Dev and a QA just to get their perspective and help expand the stories and in so doing, help break it down further You might have several of these based on complexity
- Time to gauge how big this is… PO with the help of a Dev and Tester (does not have to be the whole team) You can tell approximately how many sprints will be required The team review the epic/stories and give a rough estimate as to how big the work will be using T-Shirt sizing Small, Medium and Large
- The team goes for a refinement session Further discussions about each stories There is still a possibility of new stories created Estimates are given based on complexity (Story pointing) Stories are ordered based on Priority
- The Team goes for sprint planning Discussing refined stories in priority order Working with an agreed velocity (based on previous sprints) Taking holidays, absentees and other factors into consideration Further clarifications and new insights are highlighted as well Story points could be refined due to new insights A group of refined stories are selected for the new sprint
- The dev picks up a story to work on He invites the PO and Tester (and Dev In Test where applicable) to have an INVEST session They review the story acceptance criteria (AC) with 4 possible outcomes No change New ACs added Existing ACs removed New story added to backlog Shared understanding among all 3 (4) In some cases, a Feature file is written based on the ACs
- The dev implements the functional code and the Automated test Dev In test could implement the Automation code QA does exploratory tests around the functionality
- The Dev/QA demo the work done to the PO Armed with the Story and Feature file
- Demo the work done in the Sprint to the Business and Team.