This document discusses agile software development practices with a focus on user stories. It covers the objectives of using user stories, a brief history and motivation for agile practices, an overview of the agile process including daily standups and planning meetings, and the components and writing of user stories. It also discusses managing projects using tools for planning, estimating, and tracking progress. Key practices for development teams like refactoring, test automation, and dealing with unplanned tasks are also summarized.
Overview
- What is a User Story?
- User Story template
- examples of User Stories
- User Story Checklist
- Why not tasks?
- What is Acceptance Criteria?
- Examples of Acceptance Criteria
- Acceptance Criteria checklist
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
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
Overview
- What is a User Story?
- User Story template
- examples of User Stories
- User Story Checklist
- Why not tasks?
- What is Acceptance Criteria?
- Examples of Acceptance Criteria
- Acceptance Criteria checklist
Writing Good User Stories (Hint: It's not about writing)one80
User stories are typically the foundation of the Product Backlog. However, the original purpose has been lost. This is from a presentation that was given to help remind everyone of what User Stories are, and what they aren't. The purpose of User Stories is to drive conversations, not to hand "requirements" from one group to the next.
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
User story can be described as functional increment and it is a key element in agile environment. This presentation introduces fundamentals about user stories that can be used to educate teams or simply to review the basics.
What are User Stories? How should we write them? How to write them well?
Effective User Stories allow your team to be effective (deliver want the User needs) and efficient (Deliver it quickly and importantly don't deliver unneeded features).
It's told that if you don't like a cat you just don't know how to cook it. It's the same if we're talking about estimating and prioritizing user stories. This time we will back to unfinished the subject about bad examples of user stories and the stuff which one don't know how to treat as the user story. We will talk about which role, when and how work with user story and cover the main principles of user stories (no)estimations.
Subjects:
- What is and what is not a user story?
- Who, when and why — roles and ceremonies.
- To estimate or not to estimate?
- Case studies/practice
Product Backlog - Refinement and Prioritization TechniquesVikash Karuna
This presentation describes the important techniques used in Product Backlog refinement and prioritization in Agile development. The various techniques described here are very useful for product managers, product owners, scrum masters, and agile teams.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
"How to write better User Stories" por @jrhuertawebcat
Presentación realizada en el #webcat Barcelona de Abril 2013
Autor: José E. Rodríguez (@jrhuerta)
------------------------------------------------
RECURSOS:
- Agile Barcelona
http://agile-barcelona.org/
- "User Stories Applied: For Agile Software Development", Mike Cohn, 2004, Addison-Wesley Professional
http://www.amazon.com/User-Stories-Applied-Software-Development/dp/0321205685
- "Lean UX", Jeff Gothelf & Josh Seiden, 2012, O'Reilly Media
http://www.leanuxbook.com/
A quick guide to creating user stories. Lays out the basic user story and provides tips on creating the story.
Guide to User story Creation: https://agile-mercurial.com/2018/08/13/9-tips-for-writing-effective-user-stories/
Blog: https://agile-mercurial.com
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
User story can be described as functional increment and it is a key element in agile environment. This presentation introduces fundamentals about user stories that can be used to educate teams or simply to review the basics.
What are User Stories? How should we write them? How to write them well?
Effective User Stories allow your team to be effective (deliver want the User needs) and efficient (Deliver it quickly and importantly don't deliver unneeded features).
It's told that if you don't like a cat you just don't know how to cook it. It's the same if we're talking about estimating and prioritizing user stories. This time we will back to unfinished the subject about bad examples of user stories and the stuff which one don't know how to treat as the user story. We will talk about which role, when and how work with user story and cover the main principles of user stories (no)estimations.
Subjects:
- What is and what is not a user story?
- Who, when and why — roles and ceremonies.
- To estimate or not to estimate?
- Case studies/practice
Product Backlog - Refinement and Prioritization TechniquesVikash Karuna
This presentation describes the important techniques used in Product Backlog refinement and prioritization in Agile development. The various techniques described here are very useful for product managers, product owners, scrum masters, and agile teams.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
"How to write better User Stories" por @jrhuertawebcat
Presentación realizada en el #webcat Barcelona de Abril 2013
Autor: José E. Rodríguez (@jrhuerta)
------------------------------------------------
RECURSOS:
- Agile Barcelona
http://agile-barcelona.org/
- "User Stories Applied: For Agile Software Development", Mike Cohn, 2004, Addison-Wesley Professional
http://www.amazon.com/User-Stories-Applied-Software-Development/dp/0321205685
- "Lean UX", Jeff Gothelf & Josh Seiden, 2012, O'Reilly Media
http://www.leanuxbook.com/
A quick guide to creating user stories. Lays out the basic user story and provides tips on creating the story.
Guide to User story Creation: https://agile-mercurial.com/2018/08/13/9-tips-for-writing-effective-user-stories/
Blog: https://agile-mercurial.com
Do you want to write great User Stories that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop.
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.
Introduction to Agile Project Management and ScrumEric Krock
Brief introduction to Agile Project Management and Scrum covering user stories, story points, use of Fibonacci sequence values for story points, release planning, sprints, capacity, velocity, sprint commit meetings, sprint review meetings, and burndown charts. Explains the importance of returning the product to a potentially shippable state at the end of each sprint to reduce the accumulation of technical debt and keep the assessment of project progress realistic. Summarizes the roles in Scrum of the Product Owner (who writes or facilitates the writing by customers of user stories), the ScrumMaster (who manages the Scrum), and the Team (who do the work). Discusses values and best practices in Agile/Extreme Programming ("XP") values. Explains daily standup meeting in which people share what they did yesterday, what they’re doing today, and any blocking issues they’re encountering. Summarizes common problems with waterfall project management including a serialized process, longer time to market, isolation of developers from customer needs, plans falling out of synch with reality, lack of visibility into rate of progress, features being slashed late in the development cycle to bring in release dates, long time to project completion, late feedback from customers, projects falling behind schedule, and projects missing their market window or being killed before launch. Summaries problems with monolithic product requirements documents including length, lack of readability, disconnection from customer needs, and lack of clarity about which features are for which customers.
Introduction to Agile Project Management and ScrumVoximate
Brief introduction to Agile Project Management and Scrum covering user stories, story points, use of Fibonacci sequence values for story points, release planning, sprints, capacity, velocity, sprint commit meetings, sprint review meetings, and burndown charts. Explains the importance of returning the product to a potentially shippable state at the end of each sprint to reduce the accumulation of technical debt and keep the assessment of project progress realistic. Summarizes the roles in Scrum of the Product Owner (who writes or facilitates the writing by customers of user stories), the ScrumMaster (who manages the Scrum), and the Team (who do the work). Discusses values and best practices in Agile/Extreme Programming ("XP") values. Explains daily standup meeting in which people share what they did yesterday, what they're doing today, and any blocking issues they're encountering. Summarizes common problems with waterfall project management including a serialized process, longer time to market, isolation of developers from customer needs, plans falling out of synch with reality, lack of visibility into rate of progress, features being slashed late in the development cycle to bring in release dates, long time to project completion, late feedback from customers, projects falling behind schedule, and projects missing their market window or being killed before launch. Summaries problems with monolithic product requirements documents including length, lack of readability, disconnection from customer needs, and lack of clarity about which features are for which customers.
This presentation discusses how to split user stories using INVEST, a mnemonic created by Bill Wake. Mike Harris presented this presentation at Agile Philly.
From idea to ux roadmap - MakeIt Masterclass - Boost User ExperienceClaudio Cossio
The process to create and execute user experience (UX) improvements on web application or mobile app does not have to be a complicated task, even if you are working with multiple personas. We will talk about how to maintain relevant user stories that cross polinate on the different user personas and then create a working scheme that can be quick and easy to execute to create a UX roadmap.
The focus is to create proposals that do not add complexity to the proposed UX improvements and can be implemented with ease.
This PPT covers all 5 core components of managing software product development:
1. Software product management.
2. Projects/Tasks, including scrum
3. Management of code.
4. Management of technology.
5. Management of People.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
6. Process Overview Daily Standup Customer + Dev Team Story Workshop, Conversations, etc Customer Team I-Meet Customer + Dev Team Prioritize stories, estimate velocity R-Meet Customer + Dev Team Prioritize stories, estimate
7. A User Story 3 parts Planning placeholder & reminder Notes from conversations Tests Not system’s point of view
8. User Story – Planning Placeholder & Reminder Taskboard & Release/Sprint Planning (VersionOne*) Card Walls & Release/Sprint Planning (Mingle*) *Mingle is a trademark of Thoughtworks *VersionOne is a trademark of VersionOne
9. Notes from conversations E.g. Customer Service can search for orders so that they can quickly access the customer’s order when customer calls in to make changes to the delivery address Notes : Zie says always show customer name, order reference number, order date.
10. Tests Conveys to developers additional information Developers get an idea if they are done Treat as specification
14. Writing User Stories - Form and function The role, goal and motivation. <role’s> wants to do <goal> because <motivation> Example : As an account holder, I want to transfer funds between two of my accounts so that I can maximize the performance of my savings and avoid any fees associated with overdrafts and minimum balance rules.
15. Writing User Stories - INVEST E.g. of non-independent story : Customer can pay for basket items using iPay88 payment gateway Customer can pay for basket items using WorldPay payment gateway Possible Solutions: Combine both If combining both is too large – split out the base work: Customer can pay with one type of payment gateway Customer can pay with two additional types of payment gateway
16. Writing User Stories – INVEST Too much detail such that the extra details is associated to extra precision – always negotiable Valuable to Users User easily understands : Test with Credit Card, Debit Card and Cheque User cannot understand : Test that Payment table contains the authorization id for credit card Acceptable to indicate non-functional requirements like : This feature is expected to be used by 200 users concurrently and at any one time 200 payment records can be shown quickly, may be in 2s.
22. Writing User Stories - Responsibilities Customer Team : Responsible for writing stories, keeping in mind INVEST Developer : Help customer write stories which lack details, do not assume and always have conversation but have it at the point when supporting information is available
23. Writing User Stories - Trawling for Requirements User stories workshop, interviews ( open ended and context free questions ) , observation & questionnaire Role Modeling, Personas , Extreme characters
24. Writing User Stories - Trawling for Requirements Higher Fidelity Prototype Low Fidelity Prototype Returns/Exchange Status Delivery Input Return Details Refund Details (Based on Payment)
25. Story Smell Catalogues Stories are too small Interdependent Stories Goldplating Too many details Including user interface details too soon Thinking too far ahead Splitting too many stories Customer has trouble prioritizing Customer won’t write and prioritize stories
26. Questions What does INVEST stands for? Who constitute the Customer team? What are the tools available for trawling for requirements?
28. Managing - Planning Too many variables, too far ahead and replanning with better information not planned for 75% of all US IT projects are considered to be failures by those responsible for initiating them. Half of the projects exceeded budget by 200% 31% of projects were cancelled outright 53% of the all projects was so worrying that they were challenged.
29. Managing – Planning.Estimating Establish definition of story points Velocity = (Story Points Completed)/Sprint Previous velocity can be used to estimate Tools : Estimating : Tasks, Triangulating with Card Wall, Planning Poker
32. Managing – Planning.Release Two areas Features/Stories Prioritization : MoSCow Time Iteration Length Time to complete - Product Roadmap Move from story points to expected duration Product will be ready for release in approximately 5-7 iteration
33. Managing – Planning.Sprint Discuss a stories For each stories disaggregate into tasks Small enough to be accurate Developer accepts responsibility for each task Individually ensures estimate What! No task for upfront design?
35. Managing - Rules of the Game No changes to during a sprint Customer stay involves all the time
36. User Stories Not IEEE 830 Use cases – sized to deliver business value, “level of detail” Why Emphasize of quick chat Comprehensible by everyone Right size for planning Works for iterative development Defer details to a right point in time Support opportunistic design Encourages participatory design Build up tacit knowledge Stories may not be good ISO 9001 companies – Will have an issue with tear up stories
37. Team Practices Start off with simple design, but expect changes Refactoring ( and consequently test ) is important Test Automation is crucial Architecture, UML, use cases and agile software development Middle out
38. Questions What are the tools used in estimation? What is done in Release Planning? What are the tools used in Release Planning? Completion vs Number of Stories Points – which is preferred? Name the Team Practices. How do you deal with unplanned tasks?
44. Reference User Stories Applied for Agile Software Development – Mike Cohn – Addison Wesley http://www.thoughtworks.com/what-we-say/presentations/AgileMadeUsBetter.pdf Behavior Driven Development - Scott Belware - http://www.code-magazine.com/articleprint.aspx?quickid=0805061&printmode=true
Editor's Notes
Human’s capability to design without feedback is poor. Typically large upfront requirements and design will typically changeKey is to find that right balance – finding that balance differ from person to personIdea is start coding at the right time, so requirements can be
Customer team : Product Management, user ( if possible actual user ), testerCustomer PrioritiesDesirability from a broad base usersDesirability of the feature to a small number of important usersCohesiveness Developer PrioritiesTechnical riskCohesivenessStandupMeeting – think about a maximum of 3 things the team like to know about your work
Epic – very large stories with a large value for estimatesUser stories emphasize verbal rather than written communicationComprehensible by both you and the developersRight size for planningUser stories defer details until you have the best understanding about what you really need-> Stories can contain stories, just describe a large story and rip it up later splitting it to multiple stories
How much details is enough? The notes on the card is not important, it’s just to be a reminder, if you can remember don’t put it in.There are details that developers already think they know, it’s important that developer don’t assume – have the conversation and jot things down, don’t get too much detail, start coding first and get the feedback
Who:Customer teamWhen : During conversations between customer + developer and want to capture explicit detailsDedicated effort at the start of an iterationAfter programming of the storyWhat :-What else do the programmers need to know about this story-What am I assuming aout how this story will be implemented-What are the circumstances when this story may behave differently-What can go wrong during this storyFunctional in nature but possible to include ui flow, usability testing, performance testing, stress testingHow Needs to be automated – see fitnesseTesting for bugs not coverageAdd a test for each bug
Stories may not be independent initially, if
Issues, since there will be multiple gateway, the developer spend an upfront design and development for the base components and then provide the specific implementation and testing for each of the gateway
Epics fall into two types : Compound-split but retain cohesivenessComplex – pull research away from functionalityEg. complex algorithm, complex business process
Needs to be testable
Tools : Role ModelingCustomer Team
Constantly adjust plan to reflect the knowledge we gain from each iteration
Can be the 3 hours of solid work half dayCan be the ideal 8 hour work day, etc.Can be the 3 hours of solid work half day of two developers
Not every developer are the same – different backgroundsEstimating as a team levels outEveryone tries to complete as a team – prefers completing stories over starting new ones, Organization Development
Time Select iteration length Time to completePrioritizationBroadbase usersImportant usersCohesivenessCustomer Team Prioritizes with the help of the team
Personally I think upfront design is essential to be efficient, finding out the right balance is important – it should be allocated and the amount of time spend should be short – the longer the more complicated
