The practical value of this presentation is to help business analysts to adapt to agile and use appropriate techniques to achieve better requirements. The key take aways;
-Understand the difference between a traditional way of dealing with requirements and the agile way.
-Describe core agile requirements practices
-Understand challenges with agile requirements
-Learn sty a high level the User story concepts and Describe where they fit in the life cycle
-Understand how Acceptance tests extend User Stories
-Understand the evolution of user stories and their and elaboration throughout the life cycle
This document provides information about a workshop on slicing and splitting stories to deliver value each sprint. The main audience is product owners and business analysts who want to help the development team understand requirements. The goals of the workshop are to teach participants how to write excellent user stories and acceptance criteria, apply definitions of ready and done, understand vertical slicing, and know how to split stories. The workshop covers topics like product statements, personas, core activities, storytelling, minimal viable products, product backlog items, user stories, vertical slicing, and splitting stories.
Introduction To User Stories For Agile Product Developmentzenpdm
The document discusses user stories, which describe functionality or features a product will deliver to users. It explains that a user story should have an independent central character and plot, with a clear outcome. The document outlines best practices for writing user stories according to the INVEST criteria - ensuring stories are independent, negotiable, valuable, estimable, small, and testable. It concludes by inviting the reader to a workshop to further discuss techniques for identifying user stories.
Scoping and Estimating WordPress Projects as an AgencyJohn Giaconia
WordCamp Los Angeles 2016. Scoping and Estimating WordPress Projects as an Agency. Presentation video available here: http://wordpress.tv/2016/09/25/john-j-giaconia-and-kara-hansen-scoping-and-estimating-wordpress-projects-as-an-agency/
The document discusses planning and estimating user stories for software development. It provides guidance on writing user stories, estimating story points, determining team velocity, prioritizing stories, and planning iterations and releases. Key points include writing stories from the user's perspective using active voice, estimating stories as a team in story points rather than hours, using velocity from past iterations to plan future work, and prioritizing stories based on business value and risk.
Agile requirements and compliance finding a balanceCherifa Mansoura
When adopting an agile approach, different projects vary considerably in terms of the importance of the requirements elements and their complexities. The more complex the organisation is, the most difficult it is to adopt agile practices without tailoring them to meet the situation they are in. For regulated organisation, compliance isn’t optional, it also isn’t cheap. And with new regulations, mandates and standards being released practically monthly, many organizations are struggling to find a balance between their IT governance and the adoption of agile practices in their Software delivery. Fortunately, there are ways to stretch the agile principles/practices to count for the context you are in. On another hand, the governance needs to adapt to the new ways of developing software.without sacrificing other priorities. This presentation, inspired by Scott Ambler's book, scratches the surface, and explores some best practices that will help reduce the regulations/compliance burden during an agile delivery.
Doing agile by book is ok for the beginning. However, it's not enough. You should continue to learn by gaining new knowledge during the project. User stories and the way you're working with them are the bricks which form the foundation the better experience.
User Stories could be Your best partner and support in project, yet them could become your worst nightmare. Where and how User Stories help? When and how User Stories could become a large burden?
Next time we will dig into user story deeper. How it differs from requirements, use cases or test cases? From what parts it consists and why?
This document provides information about a workshop on slicing and splitting stories to deliver value each sprint. The main audience is product owners and business analysts who want to help the development team understand requirements. The goals of the workshop are to teach participants how to write excellent user stories and acceptance criteria, apply definitions of ready and done, understand vertical slicing, and know how to split stories. The workshop covers topics like product statements, personas, core activities, storytelling, minimal viable products, product backlog items, user stories, vertical slicing, and splitting stories.
Introduction To User Stories For Agile Product Developmentzenpdm
The document discusses user stories, which describe functionality or features a product will deliver to users. It explains that a user story should have an independent central character and plot, with a clear outcome. The document outlines best practices for writing user stories according to the INVEST criteria - ensuring stories are independent, negotiable, valuable, estimable, small, and testable. It concludes by inviting the reader to a workshop to further discuss techniques for identifying user stories.
Scoping and Estimating WordPress Projects as an AgencyJohn Giaconia
WordCamp Los Angeles 2016. Scoping and Estimating WordPress Projects as an Agency. Presentation video available here: http://wordpress.tv/2016/09/25/john-j-giaconia-and-kara-hansen-scoping-and-estimating-wordpress-projects-as-an-agency/
The document discusses planning and estimating user stories for software development. It provides guidance on writing user stories, estimating story points, determining team velocity, prioritizing stories, and planning iterations and releases. Key points include writing stories from the user's perspective using active voice, estimating stories as a team in story points rather than hours, using velocity from past iterations to plan future work, and prioritizing stories based on business value and risk.
Agile requirements and compliance finding a balanceCherifa Mansoura
When adopting an agile approach, different projects vary considerably in terms of the importance of the requirements elements and their complexities. The more complex the organisation is, the most difficult it is to adopt agile practices without tailoring them to meet the situation they are in. For regulated organisation, compliance isn’t optional, it also isn’t cheap. And with new regulations, mandates and standards being released practically monthly, many organizations are struggling to find a balance between their IT governance and the adoption of agile practices in their Software delivery. Fortunately, there are ways to stretch the agile principles/practices to count for the context you are in. On another hand, the governance needs to adapt to the new ways of developing software.without sacrificing other priorities. This presentation, inspired by Scott Ambler's book, scratches the surface, and explores some best practices that will help reduce the regulations/compliance burden during an agile delivery.
Doing agile by book is ok for the beginning. However, it's not enough. You should continue to learn by gaining new knowledge during the project. User stories and the way you're working with them are the bricks which form the foundation the better experience.
User Stories could be Your best partner and support in project, yet them could become your worst nightmare. Where and how User Stories help? When and how User Stories could become a large burden?
Next time we will dig into user story deeper. How it differs from requirements, use cases or test cases? From what parts it consists and why?
This presentation describe
What is the need for user stories in Agile project?
What is a story?
Why story?
What is criteria for a good story?
What are not stories?
Prerequisite? Knowledge of Scrum and it’s terms
This document provides information on user stories in Agile software development. It defines what a user story is, how it should be written in the form of a short description of a requirement from the perspective of an end user, and includes elements like acceptance criteria. It also discusses best practices for user stories, such as keeping them small and focused on one goal, and how user stories are used to plan and track work in Sprints.
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
The document provides an overview of user stories in agile software development. It discusses the agile manifesto and its focus on individuals, interactions, working software, and responding to change. It then covers what user stories are, how they are written in a "who, what, why" format, and how they provide an alternative to traditional work breakdown structures. It also discusses techniques for writing user stories like modeling user roles and trawling for requirements. The document emphasizes that both functional and non-functional requirements should be considered and that the agile team is responsible for fully understanding requirements.
In response to seeing a "how to pass your Scrum Master/Agile Coach Interview" we've created a way for employers to call BS on candidates who could otherwise dupe their way into a coaching role.
Business analyst interview questions and answersRobin G
The document provides interview questions and answers for business analysts. It begins with an introduction explaining the purpose of interview preparation. It then lists over 30 common interview questions for business analysts along with detailed answers. The questions cover topics like requirements gathering, documentation, analysis techniques, and responsibilities of a business analyst. Diagrams, methodologies, and concepts relevant to the business analyst role are also discussed.
Building Cloud-Native App Series - Part 1 of 11
Microservices Architecture Series
Design Thinking, Lean Startup, Agile (Kanban, Scrum),
User Stories, Domain-Driven Design
The document discusses achieving better requirements on Agile projects. It begins by introducing traditional structured requirements approaches and how Agile differs. The main points covered include:
- User stories are the basis for requirements on Agile projects, bridging business goals to implementation. Stories should fit in iterations.
- Common pitfalls when dealing with Agile requirements include lack of context, unclear acceptance criteria, and not accounting for all work.
- The document recommends adopting seven habits to improve requirements, such as establishing scope and context, prioritizing based on business value, and elaborating requirements progressively with just enough detail. Acceptance tests should define requirements.
The document discusses various techniques for splitting large user stories into smaller stories in Agile software development. It provides examples of splitting stories based on workflows, business rules, data variations, and elementary processes or data entry. Splitting large stories improves understanding, facilitates feedback, and increases development throughput. Some key benefits mentioned are that smaller stories are easier to estimate, implement, and meet the criteria to be independently valuable and testable.
How to Foster Engagement and Understanding Using AgileSalesforce Admins
The document discusses how to foster engagement and understanding using Agile principles such as product backlogs, user stories, acceptance criteria, and complexity points. It provides examples of common problems like being overloaded with work that is not prioritized or delivered work that does not meet requirements. The document recommends using a product backlog to prioritize all work, estimating complexity points rather than time, and having stakeholders choose the work based on points. It also recommends writing user stories and acceptance criteria for each to ensure the delivered work meets requirements. Using these Agile practices can help improve understanding, delivery, and provide metrics to stakeholders.
You will learn about the key aspects of the DevOps cycle including:
Continuous Business Planning
Collaborative Development
Continuous Testing
Continuous Release & Deployment
Continuous Monitoring
Continuous Customer Feedback & Optimization
Whether you are Business Analyst, Program Manager, Process Specialist or Tool Specialist, this will be a great session to help you learn about building better solutions.
* Team velocity is 24 story points per iteration
* Total backlog size is 256 story points
* To calculate the number of iterations:
- Total backlog size / Team velocity
- 256 / 24 = 10.67 iterations (round up to 11 iterations)
* Adding a 35% buffer to the backlog size:
- Backlog size * (1 + Buffer percentage)
- 256 * (1 + 0.35) = 345.6 story points
* With the buffered backlog size:
- Buffered backlog size / Team velocity
- 345.6 / 24 = 14.4 iterations (round up to 15 iterations)
Therefore, the number of iterations without buffer is 11 and with 35%
Bertrand Meyer presents an overview of agile methods and provides an assessment of their merits and shortcomings. He discusses key agile concepts like the agile manifesto and principles. Meyer then evaluates what he sees as the good aspects of agile such as frequent iterations and emphasis on working code, as well as the ugly aspects like rejection of upfront requirements and analysis. Finally, he cautions that proper assessment of agile methods requires avoiding rhetorical devices and unverifiable claims often used in agile discourse.
Life cycle of user story: Outside-in agile product management & testing, or...Ravi Tadwalkar
It has always been my pleasure and fun to facilitate workshops for PM (product management) community at and outside Cisco, although this was first time I did a BDD workshop with PMs alone. And I realized today how PayPal has been a really great venue for SVPMA annual product camp "unconference" for 1k+ PMs with 550 waitlisted this year! I look forward to this event every year now...huge success!
Abstract:
As Product Owners and Managers are driving innovation thru' those fuzzy ideas in terms of scenarios, testers have always been thinking about those in form of test cases which take form of acceptance criteria for those scenarios. When you talk about those scenarios to your teams or even peers, you see those diverging ideas converging to something concrete.
That's how BDD helps you shape that idea. That fuzzy scenario, when validated thru' an engineering "spike", can be useful for product management MRD/PRD/use-case-models/stories...whatever it is that you want to use to drive product development.
And this is where Agile Tester role begins! So instead of doing top-down or bottoms-up product management & testing, try this outside-in approach. Go for it!
My workshop on BDD is about what I term as "Outside-in agile product management". To understand what I really mean by that, here is my slideshare presentation used rarely when teaching from the back of the class during this hyper-interactive workshop.
Session 1 - The Agile vs Non agile divide.pptxWatchDogs6
This document provides an overview of agile versus traditional project management approaches. It begins with a visual depicting rafters needing either fast maneuverability based on immediate conditions or a pre-planned design. It then discusses the iterative model versus waterfall model and asks whether the reader prefers a collaborative or directive manager. Key differences in the agile manifesto are outlined, such as valuing individuals/interactions over processes. The document notes configuration management is easier with agile due to focusing work and discusses advantages even if other documents need maintained. It provides examples of project types better suited to each approach and emphasizes that resistance to change can occur even after studies prove certain steps don't improve quality.
This document provides an overview of agile versus traditional project management approaches. It begins with a metaphor comparing rafters who need to maneuver quickly based on conditions ahead versus those who need a pre-planned route. It then discusses the iterative model and agile methodology compared to the traditional waterfall model. Key differences highlighted between agile and traditional approaches include the emphasis on individuals and interactions over processes, working software over documentation, and responding to change over following a strict plan. The document also discusses configuration management and how handling requirements and designs can be easier with agile development. Overall, it presents agile and traditional methods as having some shared goals around delivering valuable products, but differing in aspects like how much control and documentation is valued during the
Agile Analysis Techniques by Harlan Bennett and Kevin PiousExcella
Harlan Bennett, Senior Consultant, CapTech
Kevin Pious, BA Center of Excellence Lead, CapTech
Most of the key skills that analysts have can be applied to any type of project methodology. However, there are certain principles that more closely apply to Agile business analysis. Based on the Agile Extension to the Business Analysis Body of Knowledge, we will look at some key principles that analysts need to follow that will help lead to overall project success. The key principles are:
• See The Whole
• Think as a Customer
• Analyze to Determine What is Valuable
• Get Real Using Examples
• Understand What is Doable
• Stimulate Collaboration and Continuous Improvement
• Avoid Waste
This was some thoughts for maturing our Agile SDLC with some specific notes on how to improve JIRA workflows. This was a discussion slide deck; it's very wordy
A deep dive into components of a user story, looking at beyond the basics that we all know (ought to know) and are familiar with. The deck provides guidance on developing individual components that make up a ‘Ready for Dev’ user story.
This presentation describe
What is the need for user stories in Agile project?
What is a story?
Why story?
What is criteria for a good story?
What are not stories?
Prerequisite? Knowledge of Scrum and it’s terms
This document provides information on user stories in Agile software development. It defines what a user story is, how it should be written in the form of a short description of a requirement from the perspective of an end user, and includes elements like acceptance criteria. It also discusses best practices for user stories, such as keeping them small and focused on one goal, and how user stories are used to plan and track work in Sprints.
Techniques for Effectively Slicing User Stories by Naresh JainNaresh Jain
In order to achieve my goals, as a buyer of your product, I want awesome feature. AT: make sure your users stories don't get in the way.
Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories and acceptance criteria, that everyone on the team understands. We'll learn various techniques to slice your stories using the tracer-bullet approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.
Agenda:
What do you do to Large Stories? Spike, Split, Stub & Timebox (SSST) technique.
Core Slicing Techniques:
1. System Slice
1.a. Static vs. Dynamic
1.b. Real-time vs. Batch Processing
1.c. Build vs. Buy
1.d. Automated vs. Manual Steps
1.e. Defer certain roles
2. Behavioural Slice
2.a. Adjusting Sophistication - MVF (Minimum Viable Feature) or Walking Skeleton
2.a.1. Acceptance Criteria
2.b. By-pass certain steps in the workflow
2.c. Focus on Happy Path First (edge cases later)
2.d. No options - 1 option - Many options
3. Incrementally improve ‘Ilities' (Usability, Scalability, Reliability, etc.)
3.a. Simpler UI (even consider using a standard UI)
3.b. Minmal Data
3.c. Improve Performance Iteratively
The document provides an overview of user stories in agile software development. It discusses the agile manifesto and its focus on individuals, interactions, working software, and responding to change. It then covers what user stories are, how they are written in a "who, what, why" format, and how they provide an alternative to traditional work breakdown structures. It also discusses techniques for writing user stories like modeling user roles and trawling for requirements. The document emphasizes that both functional and non-functional requirements should be considered and that the agile team is responsible for fully understanding requirements.
In response to seeing a "how to pass your Scrum Master/Agile Coach Interview" we've created a way for employers to call BS on candidates who could otherwise dupe their way into a coaching role.
Business analyst interview questions and answersRobin G
The document provides interview questions and answers for business analysts. It begins with an introduction explaining the purpose of interview preparation. It then lists over 30 common interview questions for business analysts along with detailed answers. The questions cover topics like requirements gathering, documentation, analysis techniques, and responsibilities of a business analyst. Diagrams, methodologies, and concepts relevant to the business analyst role are also discussed.
Building Cloud-Native App Series - Part 1 of 11
Microservices Architecture Series
Design Thinking, Lean Startup, Agile (Kanban, Scrum),
User Stories, Domain-Driven Design
The document discusses achieving better requirements on Agile projects. It begins by introducing traditional structured requirements approaches and how Agile differs. The main points covered include:
- User stories are the basis for requirements on Agile projects, bridging business goals to implementation. Stories should fit in iterations.
- Common pitfalls when dealing with Agile requirements include lack of context, unclear acceptance criteria, and not accounting for all work.
- The document recommends adopting seven habits to improve requirements, such as establishing scope and context, prioritizing based on business value, and elaborating requirements progressively with just enough detail. Acceptance tests should define requirements.
The document discusses various techniques for splitting large user stories into smaller stories in Agile software development. It provides examples of splitting stories based on workflows, business rules, data variations, and elementary processes or data entry. Splitting large stories improves understanding, facilitates feedback, and increases development throughput. Some key benefits mentioned are that smaller stories are easier to estimate, implement, and meet the criteria to be independently valuable and testable.
How to Foster Engagement and Understanding Using AgileSalesforce Admins
The document discusses how to foster engagement and understanding using Agile principles such as product backlogs, user stories, acceptance criteria, and complexity points. It provides examples of common problems like being overloaded with work that is not prioritized or delivered work that does not meet requirements. The document recommends using a product backlog to prioritize all work, estimating complexity points rather than time, and having stakeholders choose the work based on points. It also recommends writing user stories and acceptance criteria for each to ensure the delivered work meets requirements. Using these Agile practices can help improve understanding, delivery, and provide metrics to stakeholders.
You will learn about the key aspects of the DevOps cycle including:
Continuous Business Planning
Collaborative Development
Continuous Testing
Continuous Release & Deployment
Continuous Monitoring
Continuous Customer Feedback & Optimization
Whether you are Business Analyst, Program Manager, Process Specialist or Tool Specialist, this will be a great session to help you learn about building better solutions.
* Team velocity is 24 story points per iteration
* Total backlog size is 256 story points
* To calculate the number of iterations:
- Total backlog size / Team velocity
- 256 / 24 = 10.67 iterations (round up to 11 iterations)
* Adding a 35% buffer to the backlog size:
- Backlog size * (1 + Buffer percentage)
- 256 * (1 + 0.35) = 345.6 story points
* With the buffered backlog size:
- Buffered backlog size / Team velocity
- 345.6 / 24 = 14.4 iterations (round up to 15 iterations)
Therefore, the number of iterations without buffer is 11 and with 35%
Bertrand Meyer presents an overview of agile methods and provides an assessment of their merits and shortcomings. He discusses key agile concepts like the agile manifesto and principles. Meyer then evaluates what he sees as the good aspects of agile such as frequent iterations and emphasis on working code, as well as the ugly aspects like rejection of upfront requirements and analysis. Finally, he cautions that proper assessment of agile methods requires avoiding rhetorical devices and unverifiable claims often used in agile discourse.
Life cycle of user story: Outside-in agile product management & testing, or...Ravi Tadwalkar
It has always been my pleasure and fun to facilitate workshops for PM (product management) community at and outside Cisco, although this was first time I did a BDD workshop with PMs alone. And I realized today how PayPal has been a really great venue for SVPMA annual product camp "unconference" for 1k+ PMs with 550 waitlisted this year! I look forward to this event every year now...huge success!
Abstract:
As Product Owners and Managers are driving innovation thru' those fuzzy ideas in terms of scenarios, testers have always been thinking about those in form of test cases which take form of acceptance criteria for those scenarios. When you talk about those scenarios to your teams or even peers, you see those diverging ideas converging to something concrete.
That's how BDD helps you shape that idea. That fuzzy scenario, when validated thru' an engineering "spike", can be useful for product management MRD/PRD/use-case-models/stories...whatever it is that you want to use to drive product development.
And this is where Agile Tester role begins! So instead of doing top-down or bottoms-up product management & testing, try this outside-in approach. Go for it!
My workshop on BDD is about what I term as "Outside-in agile product management". To understand what I really mean by that, here is my slideshare presentation used rarely when teaching from the back of the class during this hyper-interactive workshop.
Session 1 - The Agile vs Non agile divide.pptxWatchDogs6
This document provides an overview of agile versus traditional project management approaches. It begins with a visual depicting rafters needing either fast maneuverability based on immediate conditions or a pre-planned design. It then discusses the iterative model versus waterfall model and asks whether the reader prefers a collaborative or directive manager. Key differences in the agile manifesto are outlined, such as valuing individuals/interactions over processes. The document notes configuration management is easier with agile due to focusing work and discusses advantages even if other documents need maintained. It provides examples of project types better suited to each approach and emphasizes that resistance to change can occur even after studies prove certain steps don't improve quality.
This document provides an overview of agile versus traditional project management approaches. It begins with a metaphor comparing rafters who need to maneuver quickly based on conditions ahead versus those who need a pre-planned route. It then discusses the iterative model and agile methodology compared to the traditional waterfall model. Key differences highlighted between agile and traditional approaches include the emphasis on individuals and interactions over processes, working software over documentation, and responding to change over following a strict plan. The document also discusses configuration management and how handling requirements and designs can be easier with agile development. Overall, it presents agile and traditional methods as having some shared goals around delivering valuable products, but differing in aspects like how much control and documentation is valued during the
Agile Analysis Techniques by Harlan Bennett and Kevin PiousExcella
Harlan Bennett, Senior Consultant, CapTech
Kevin Pious, BA Center of Excellence Lead, CapTech
Most of the key skills that analysts have can be applied to any type of project methodology. However, there are certain principles that more closely apply to Agile business analysis. Based on the Agile Extension to the Business Analysis Body of Knowledge, we will look at some key principles that analysts need to follow that will help lead to overall project success. The key principles are:
• See The Whole
• Think as a Customer
• Analyze to Determine What is Valuable
• Get Real Using Examples
• Understand What is Doable
• Stimulate Collaboration and Continuous Improvement
• Avoid Waste
This was some thoughts for maturing our Agile SDLC with some specific notes on how to improve JIRA workflows. This was a discussion slide deck; it's very wordy
A deep dive into components of a user story, looking at beyond the basics that we all know (ought to know) and are familiar with. The deck provides guidance on developing individual components that make up a ‘Ready for Dev’ user story.
This document discusses different definitions and uses of epics in agile software development. Epics can refer to large user stories that don't fit in a single sprint, placeholders for multiple user stories, or initiatives in hierarchical backlogs. Epics allow tracking of large, loosely defined ideas and outcomes. The Scaled Agile Framework uses epics at the portfolio level for company-wide initiatives. Epics help deliver complex requests, apply strategies, engage managers, focus skills, ensure cost visibility, and move from traditional to agile processes. They should be managed by defining outcomes and consistently applying the chosen definition.
Re-uploading my User Story Splitting workshop; it seems to have gone missing.
This is a slide deck I have used for helping people learn various user story splitting techniques.
This document discusses user stories and how they can help software development teams understand user needs better than traditional requirements specifications. It provides examples of proper user stories, outlines key principles of writing effective stories, and explains how stories evolve through collaborative conversations between business stakeholders and developers. The document cautions that while documents are not abandoned, less documentation is preferable to reduce overhead and allow stories to change shape based on feedback.
Here are 3 scenarios that could be attached to the user story card:
Scenario 1: As a customer, I search for flights from New York to Los Angeles for next weekend. The results show available flights for those dates.
Scenario 2: As a customer, I select a flight from the results and am taken to a page to enter my personal details and payment information to complete the booking.
Scenario 3: As a customer, I receive a confirmation email after completing my booking with all the flight details.
Conversation
The team discusses things like:
- What dates constitute "next weekend"?
- What payment methods will be accepted?
- What information is included in the confirmation email?
Confirmation
Aligning Product Strategy with Customer Feature RequestsProductPlan
We’ve all been on customer calls where we’re asked for a feature that just does not align with our product strategy. It’s not a problem if one request is an outlier, but how should you handle recurring requests from your customers that do not align with your product strategy? In this webinar, product management veterans share real examples of feature requests that did not naturally fit with the company’s vision.
Similar to Achieving better requirements in agile (20)
SATTA MATKA DPBOSS KALYAN MATKA RESULTS KALYAN CHART KALYAN MATKA MATKA RESULT KALYAN MATKA TIPS SATTA MATKA MATKA COM MATKA PANA JODI TODAY BATTA SATKA MATKA PATTI JODI NUMBER MATKA RESULTS MATKA CHART MATKA JODI SATTA COM INDIA SATTA MATKA MATKA TIPS MATKA WAPKA ALL MATKA RESULT LIVE ONLINE MATKA RESULT KALYAN MATKA RESULT DPBOSS MATKA 143 MAIN MATKA KALYAN MATKA RESULTS KALYAN CHART
Best Competitive Marble Pricing in Dubai - ☎ 9928909666Stone Art Hub
Stone Art Hub offers the best competitive Marble Pricing in Dubai, ensuring affordability without compromising quality. With a wide range of exquisite marble options to choose from, you can enhance your spaces with elegance and sophistication. For inquiries or orders, contact us at ☎ 9928909666. Experience luxury at unbeatable prices.
Adani Group's Active Interest In Increasing Its Presence in the Cement Manufa...Adani case
Time and again, the business group has taken up new business ventures, each of which has allowed it to expand its horizons further and reach new heights. Even amidst the Adani CBI Investigation, the firm has always focused on improving its cement business.
The Steadfast and Reliable Bull: Taurus Zodiac Signmy Pandit
Explore the steadfast and reliable nature of the Taurus Zodiac Sign. Discover the personality traits, key dates, and horoscope insights that define the determined and practical Taurus, and learn how their grounded nature makes them the anchor of the zodiac.
SATTA MATKA DPBOSS KALYAN MATKA RESULTS KALYAN CHART KALYAN MATKA MATKA RESULT KALYAN MATKA TIPS SATTA MATKA MATKA COM MATKA PANA JODI TODAY BATTA SATKA MATKA PATTI JODI NUMBER MATKA RESULTS MATKA CHART MATKA JODI SATTA COM INDIA SATTA MATKA MATKA TIPS MATKA WAPKA ALL MATKA RESULT LIVE ONLINE MATKA RESULT KALYAN MATKA RESULT DPBOSS MATKA 143 MAIN MATKA KALYAN MATKA RESULTS KALYAN CHART
During the budget session of 2024-25, the finance minister, Nirmala Sitharaman, introduced the “solar Rooftop scheme,” also known as “PM Surya Ghar Muft Bijli Yojana.” It is a subsidy offered to those who wish to put up solar panels in their homes using domestic power systems. Additionally, adopting photovoltaic technology at home allows you to lower your monthly electricity expenses. Today in this blog we will talk all about what is the PM Surya Ghar Muft Bijli Yojana. How does it work? Who is eligible for this yojana and all the other things related to this scheme?
High-Quality IPTV Monthly Subscription for $15advik4387
Experience high-quality entertainment with our IPTV monthly subscription for just $15. Access a vast array of live TV channels, movies, and on-demand shows with crystal-clear streaming. Our reliable service ensures smooth, uninterrupted viewing at an unbeatable price. Perfect for those seeking premium content without breaking the bank. Start streaming today!
https://rb.gy/f409dk
Efficient PHP Development Solutions for Dynamic Web ApplicationsHarwinder Singh
Unlock the full potential of your web projects with our expert PHP development solutions. From robust backend systems to dynamic front-end interfaces, we deliver scalable, secure, and high-performance applications tailored to your needs. Trust our skilled team to transform your ideas into reality with custom PHP programming, ensuring seamless functionality and a superior user experience.
SATTA MATKA DPBOSS KALYAN MATKA RESULTS KALYAN MATKA MATKA RESULT KALYAN MATKA TIPS SATTA MATKA MATKA COM MATKA PANA JODI TODAY BATTA SATKA MATKA PATTI JODI NUMBER MATKA RESULTS MATKA CHART MATKA JODI SATTA COM INDIA SATTA MATKA MATKA TIPS MATKA WAPKA ALL MATKA RESULT LIVE ONLINE MATKA RESULT KALYAN MATKA RESULT DPBOSS MATKA 143 MAIN MATKA KALYAN MATKA RESULTS KALYAN CHART KALYAN CHART
Enhancing Adoption of AI in Agri-food: IntroductionCor Verdouw
Introduction to the Panel on: Pathways and Challenges: AI-Driven Technology in Agri-Food, AI4Food, University of Guelph
“Enhancing Adoption of AI in Agri-food: a Path Forward”, 18 June 2024
The Role of White Label Bookkeeping Services in Supporting the Growth and Sca...YourLegal Accounting
Effective financial management is important for expansion and scalability in the ever-changing US business environment. White Label Bookkeeping services is an innovative solution that is becoming more and more popular among businesses. These services provide a special method for managing financial duties effectively, freeing up companies to concentrate on their main operations and growth plans. We’ll look at how White Label Bookkeeping can help US firms expand and develop in this blog.
NIMA2024 | De toegevoegde waarde van DEI en ESG in campagnes | Nathalie Lam |...BBPMedia1
Nathalie zal delen hoe DEI en ESG een fundamentele rol kunnen spelen in je merkstrategie en je de juiste aansluiting kan creëren met je doelgroep. Door middel van voorbeelden en simpele handvatten toont ze hoe dit in jouw organisatie toegepast kan worden.
SATTA MATKA DPBOSS KALYAN MATKA RESULTS KALYAN CHART KALYAN MATKA MATKA RESULT KALYAN MATKA TIPS SATTA MATKA MATKA COM MATKA PANA JODI TODAY BATTA SATKA MATKA PATTI JODI NUMBER MATKA RESULTS MATKA CHART MATKA JODI SATTA COM INDIA SATTA MATKA MATKA TIPS MATKA WAPKA ALL MATKA RESULT LIVE ONLINE MATKA RESULT KALYAN MATKA RESULT DPBOSS MATKA 143 MAIN MATKA KALYAN MATKA RESULTS KALYAN CHART
Satta matka fixx jodi panna all market dpboss matka guessing fixx panna jodi kalyan and all market game liss cover now 420 matka office mumbai maharashtra india fixx jodi panna
Call me 9040963354
WhatsApp 9040963354
1. Achieving better requirements
on Agile projects: User stories and beyond
CHERIFA MANSOURA
Agile Coach, Business Architect
ca.linkedin.com/in/linkedincherifamansoura
TEKsystems, Montreal
cherifa174@gmail.com
2. 2 2
Agenda
§ A quick peep into the ‘World of structured requirements’
§ The Agile way of Requirements
§ Common pitfalls when dealing with Agile Requirements
§ Adopt SEVEN habits to achieve better requirements
Here is Edward bear, coming downstairs now, bump, bump,
bump
on the back of his head…
It is as far as he knows, the only way of coming downstairs
But sometimes he feels that there really is another way……..
AA Milne, Winnie-ther-Pooh
AGILE
SEVEN
HABITS
USER
STORIES
3. 3
The World of Structured Requirements
‘Big Requirements Up Front (BRUF)’ Approach
§ Changes are not handled effectively
§ Assumption / guess work on requirements
§ Artifact-driven and Overreliance on
documentation
The Waterfall Paradox: Scope and Time (or
Cost) are fixed, but in practice, all three
constraints become fixed.
Waterfall seems simple to adopt
... which leads us to the ‘Iron Triangle’.
Why do organizations choose to work
this way? Quality
Scope
4. 4
Break the ‘Iron Triangle’ with Agile
4
Scope
Quality
Scope = Value
§ The product backlog is the backbone for scope management
§ Not ‘all’ will be done
§ Prioritisation is key to delivering value and mitigating risks earlier
Time is fixed
§ Sprints and Iterations
§ Releases and Milestones
Cost is constrained
§ Project costs are usually fixed
§ Resources are constrained by
Brooks’ Law
Of the three critical factors – scope, cost, and time – vary at least one
6. 6
Consider an Agile Approach and breaking down the barriers
Prioritized
Requirement List
TestsCode
Requirements
specs
Tests
Code
Requirements
One whole team
Silos
Agile Team Collaborates with
Customer
ü Done
ü Done
ü Done
7. 7
Agile Requirements: Strategies are changing
Practices are shifting into a leaner way
Continual customer involvement
§ Product owner represents the stakeholders
§ Active participation of the Stakeholders
Shared vision
§ Understand business needs
§ Focus on stakeholders goals
Requirements elicitations
§ Conversations, agile modeling, workshops
Requirements analysis
§ Performed “just in time”
Requirements documentation
§ User stories, storyboards, acceptance tests, agile
models
§ Is your documentation adding value? Test it
Ceremony, Formality
§ More relaxed approach
8. 8
And how is that done?
User Stories
§ Basis for the Requirements
§ Bridges the gaps from business goals to implementation plans
9. 9
User Stories: An Agile Approach to Requirements
Card
As an amazon customer, I want to view book details so
that I can decide to buy it
Conversation What information is needed to search for a book?
What information is displayed?
Confirmation Try it with author name
Try it with a title
Try it with key words
• Stories are short, simple description of a feature told from the perspective of the
person who desires the new capability, usually a user or customer of the system
• Stories should be able to fit into a single iteration; if the size is larger, it should be
grouped into smaller logical sections
• Epics will be used for the following purposes (to be created from business
requirements)
– As placeholder for a functionality/group of stories where the work hasn’t been clarified
10. 10
Span Releases
Fit in releases
Fit in iterations
Where do User Stories fit in?
Business perspective
• Epics backlog
• Stakeholders goals
• Backlog constraints
System perspective
• Features
User perspective
• Stories backlog
• Backlog constraints
10
Source: Dean Lefingwell
TASKS
Epics
Features
User Stories
Implemented by
11. 11
Common pitfalls while dealing with Agile Requirements
§ Major challenges with attitude over new language
– User stories, velocity, story points, epics, backlog..
§ Major challenges with requirements and requirements details
– Is the context known? How much do we know about the dependencies links that are of
contextual relevance.
– How do you establish upfront business commitments?
– Are you in a contractual situation?
– How do we account for backlog items that do not fit
user story paradigm?
– Aside from user stories, what are ways to represent
product needs?
– Where are my business rules?
– Where are my “quality of services” (NFR)?
– Where do I track other constraints?
§ Major challenges with stories
– User story vs system story User stories are just part of
requirements
– Finding epics and stories from process models? Who is in charge?
12. 12
HABIT #1
§ Establish Context and Scope
HABIT #2
§ Focus on Business Value
HABIT #3
§ Prioritize
HABIT #4
§ Elaborate requirements progressively
HABIT #5
§ Collaborate, Communicate
HABIT #6
§ Focus on quality
HABIT #7
§ Manage
Adopt SEVEN effective habits
13. 13
Adopt Habit #1: Establish Context and Scope
Product
Backlog
User/System
Stories
Defects / Change
Requests
§ Establish a shared vision that captures customers real needs
§ Consider your organization scaling factors: i.e. distributed team
§ Consider all work that needs to be done
Defects, Change Requests, Review the work of other teams, and so on.
§ All of this work needs to be taken into account when creating the backlog.
As a customer I want to be … 5
As a customer I want to be … 3
As a administrator I want … 2
As a business planner I … 3
Defect 1 ….. 8
As a administrator I want … 2
Change Request 1 5
As a customer I want to be … 1
Change Request 2 8
Product Backlog Size
RankOrder
Product
Backlog
Vision
14. 14
Put Information in the right context
§ Requirements
§ Functional Requirements
§ Non Functional Requirements (NFR) which are:
• Cross-cutting
• Pertinent to many functional requirements (user stories)
• Typically maintained outside of the work item list
• Addressed throughout the entire project
• Often technical constraints on your solution
§ Other functional requirements
§ Business rules
§ Data requirements
§ Others: Dependencies between teams
§ Track dependencies using the stories paradigm
§ Technical stories to
capture NFR’s
§ Acceptance Criteria
§ Acceptance Criteria
§ Epics / Stories
15. 15
NFR vs Constraints
§ Using a check list to validate Qualities and the development of architectural aspects
§ When see a fit, use the story paradigm…
Tip
§ Use a check list to discover constraints that will impact the project that is revisited every time the
team is estimating, prioritizing…
Availability
Maintainability
Portability
Safety
Security
Performance
Usability
Design Constraints
Regulations Standards
Common kind of
Non Functional requirements
Known constraints
ü Story1
ü Story2
ü Constraint - User Story A
ü AC for User Story B
16. 16 16
Adopt Habit #2: Focus on business and user values
Explore how to define business value not only from User Stories but from
other requirements
.
§ Delivered business value is the only measure of success
§ We must establish a shared vision that captures customers
real needs
§ Ranked Backlog: List of work items prioritized by importance
or value to the business stakeholders, risk and dependencies
§ And…..select the practices that add value……deliver
iteratively….deliver something of value every iteration
Tips
§ It does not matter what type a requirement is, functional or not, just that you do not forget to
include it when prioritizing, estimating.
§ In agile do not try to force requirements language on people
§ Smart team should be aware of what add “value” to business and users.
17. 17
Adopt Habit #3: Prioritize
Only with a clear business
value, will the stakeholders be
able to adequately prioritize
the release content
Prioritize them,
Size them using story points,
Rank order them, by taking
into account the NFR and
constraints
See http://www.agilemodeling.com/essays/prioritizedRequirements.htm
19. 19
Obtain "Just enough detail" when needed
§ Apply “Just barely enough” practice
§ Do some agile modeling (Model
storming)
§ Defer detail until you have the best
understanding you are going to have
about what you really need
§ Apply these principles:
– Evolutionary design
– Good enough for the customer
– Good enough for the “purpose” of the
iteration.
Source: Scott Ambler; agile modeling
20. 2020
Beyond Stories are details… but “Just enough details”
For each story selected, gather the details
§ During conversation: Discuss story, make sure
everyone understands
– Clarify the goal and business value
– Collaborate
– Flesh out details (Business rules,
constraints, ..NFR)
§ Define Acceptance criteria
§ Define the tasks required to complete the work
§ Review the tasks as a team if they were defined
separately
§ If the amount of time required to complete tasks
exceeds time available, drop a story or break a
story down, reassess
21. 21
Adopt Habit #5: Collaborate, Communicate
Emphasize verbal rather than written communication
Collaborate any time , anywhere any required!
§ Collaborate to build the backlog
§ Collaborate to build consensus on appropriate level of
details required
§ Collaborate during your iteration planning
§ Collaborate at any time during your construction phase
– Tasks and stories belong to the team
– The team is anyone who can participates.
– Work flows between team members.
§ Adopt a Business value focused collaboration: Do not
supports a task culture (vs. value culture) where work
isn’t collaborative
22. 2222
Adopt Habit #6: Focus on Quality
Acceptance tests are your requirements specifications
Why quality matters?
§ Quality is not an after thought in agile world
§ Quality is to make sure
– the requirements are correct
– They meet the stakeholders needs
§ Acceptance criteria drive the acceptance tests.
§ Acceptance tests, define what you will test, what you will not test
– Acceptance tests define when story is done
– Are artifacts of the conversations, not intended to be thorough
§ Acceptance tests drive (not replace) the real test code, drive (not replace) the test
case development, etc.
– Detailed test management as appropriate is still required
23. 23
Discovering your acceptance criteria during conversation
§ Identify your Acceptance criteria from
– your stories attributes
– NFR that are not stories
– Business rules that are not stories
§ Acceptance criteria are always required
– What is required to make the story acceptable to the stakeholder?
– Does the story deliver the value intended?
– Does the solution solve the user’s problem?
– Based on decisions made in story discussions that define how the story will work
§ Acceptance criteria are measurable and concrete
§ Acceptance criteria are specific
§ Acceptance criteria are unambiguous
§ Acceptance criteria are achievable
24. 24
Adopt Habit #7: Manage
§ Use the Product Backlog as the single source of all
planning activities.
§ Effectively scope and manage backlog and release /
sprint plan.
§ ‘Manage’ NOT ‘Control’.
§ Do not undermine self-organization.
§ Involve the teams in determining their constitution.
§ Define effective “doneness” criteria.
§ Use Metrics and measurement capabilities to help
the team track progress .
26. 26
What are the take aways?
§ Apply Agile principles and take them to heart
– No more kicking requirements over the wall
– No more big requirements documents
– Become embedded in the team and the process
§ Become part of the full project lifecycle
– Realise requirements is an ongoing process throughout project
– Prepare to be a part of the team for longer time frame, through
many iterations/sprints
– Become embedded in the Quality aspect of the lifecycle
§ Embrace change!
– Embrace the organisational change that comes with agile
– Embrace constant change to the project scope/requirements/
needs/priorities