User Stories
•Download as PPT, PDF•
2 likes•897 views
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 releases using techniques like setting up buckets for "must have", "should have", and "could have" stories. The developer's responsibilities include estimating stories accurately and not giving into pressure to provide lower estimates. The customer is responsible for prioritizing stories and having visibility into risks of different priority choices.
Report
Share
Report
Share
![Customer Team ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
The Smells Of Bad Design
The document discusses code smells that indicate issues with software design, including rigidity, fragility, immobility, viscosity, needless complexity, and opacity. It provides examples and questions to help identify when code exhibits these smells and suggests approaches to address them, such as improving reusability, reducing duplication, and employing techniques like peer review and documentation.
Kens Scrum Presentation
The document discusses several key aspects of Scrum:
1. Scrum is a framework based on empirical process control that was developed from lessons learned by companies like Toyota. It focuses on transparency, inspection, and adaptation.
2. Scrum provides a framework for self-organizing cross-functional teams to deliver working software frequently in short iterations with a "Done" definition.
3. Common reasons cited for Scrum failures include underlying problems in the organization already existing prior to adopting Scrum, as well as unwillingness to change engineering practices or deliver working code each iteration.
Scrum And The Enterprise
This document discusses strategies for scaling Scrum practices within large organizations. It addresses organizing teams, integrating work across teams, managing people and skills, prioritizing work in an enterprise backlog, and delivering value through iterative development focused on the highest priority items. Key challenges include integrating work across multiple teams and layers, managing specialized skills, and ensuring continuous delivery of value at the enterprise level.
Arch factory - Agile Design: Best Practices
This document provides guidance on agile architecture and design principles. It emphasizes that agile design is about responding quickly to change for customers and teams through transparency, lightweight processes, and continuous learning. Key principles discussed include designing incrementally without large upfront design; getting early and continuous feedback; delaying commitment and complexity; and maximizing evolutionary design through reversibility and packaging. The document also covers topics like testing, distributed teams, and delivering frequently.
Zero to tested
The document discusses strategies for improving test automation in challenging environments. It advocates for automating infrastructure provisioning using tools like Chef, Packer, Terraform and AWS to create ephemeral, automated environments. It also recommends building test code that is resilient to flakiness through techniques like retry logic, explicit waits, and logging/detecting non-determinism. The document provides a code example demonstrating how to automate infrastructure, write tests that can handle asynchronicity and other challenges, and effectively report failures to drive improvement.
Extreme programming
Slides from the talk from AgileVigo (https://www.meetup.com/agile-vigo/events/241197513/) on July 2017
Product Vs Craft
This document summarizes a talk given by Juan Delgado on the topics of product vs craft in software development. Some key points made in the document include:
- The quality and practices used in software development should be adapted based on the vision and goals of the product as well as where the product is in its lifecycle. Extreme quality may not be necessary early on.
- There is no single "right" way to build software - different approaches can both be appropriate depending on the context and needs of the product and business. Quality is contextual.
- Software teams should aim to implement "enough quality" - quality that allows for correctness and the ability to continue developing the product, but not necessarily perfect or extreme quality
An Introduction to XP and Agile
This document provides an introduction to eXtreme Programming (XP) and agile software development methods. It discusses some common problems with traditional software development approaches such as taking too long, costing too much, and requiring too many people. XP and agile aim to address these problems through principles like rapid delivery of working software in short iterations, frequent feedback, simplicity, respect, and flexibility. The document outlines XP practices like user stories, pair programming, test-driven development, and daily standups that embody these principles. It concludes by noting that agile methods have evolved over decades to become more effective approaches to software development.
Recommended
The Smells Of Bad Design
The document discusses code smells that indicate issues with software design, including rigidity, fragility, immobility, viscosity, needless complexity, and opacity. It provides examples and questions to help identify when code exhibits these smells and suggests approaches to address them, such as improving reusability, reducing duplication, and employing techniques like peer review and documentation.
Kens Scrum Presentation
The document discusses several key aspects of Scrum:
1. Scrum is a framework based on empirical process control that was developed from lessons learned by companies like Toyota. It focuses on transparency, inspection, and adaptation.
2. Scrum provides a framework for self-organizing cross-functional teams to deliver working software frequently in short iterations with a "Done" definition.
3. Common reasons cited for Scrum failures include underlying problems in the organization already existing prior to adopting Scrum, as well as unwillingness to change engineering practices or deliver working code each iteration.
Scrum And The Enterprise
This document discusses strategies for scaling Scrum practices within large organizations. It addresses organizing teams, integrating work across teams, managing people and skills, prioritizing work in an enterprise backlog, and delivering value through iterative development focused on the highest priority items. Key challenges include integrating work across multiple teams and layers, managing specialized skills, and ensuring continuous delivery of value at the enterprise level.
Arch factory - Agile Design: Best Practices
This document provides guidance on agile architecture and design principles. It emphasizes that agile design is about responding quickly to change for customers and teams through transparency, lightweight processes, and continuous learning. Key principles discussed include designing incrementally without large upfront design; getting early and continuous feedback; delaying commitment and complexity; and maximizing evolutionary design through reversibility and packaging. The document also covers topics like testing, distributed teams, and delivering frequently.
Zero to tested
The document discusses strategies for improving test automation in challenging environments. It advocates for automating infrastructure provisioning using tools like Chef, Packer, Terraform and AWS to create ephemeral, automated environments. It also recommends building test code that is resilient to flakiness through techniques like retry logic, explicit waits, and logging/detecting non-determinism. The document provides a code example demonstrating how to automate infrastructure, write tests that can handle asynchronicity and other challenges, and effectively report failures to drive improvement.
Extreme programming
Slides from the talk from AgileVigo (https://www.meetup.com/agile-vigo/events/241197513/) on July 2017
Product Vs Craft
This document summarizes a talk given by Juan Delgado on the topics of product vs craft in software development. Some key points made in the document include:
- The quality and practices used in software development should be adapted based on the vision and goals of the product as well as where the product is in its lifecycle. Extreme quality may not be necessary early on.
- There is no single "right" way to build software - different approaches can both be appropriate depending on the context and needs of the product and business. Quality is contextual.
- Software teams should aim to implement "enough quality" - quality that allows for correctness and the ability to continue developing the product, but not necessarily perfect or extreme quality
An Introduction to XP and Agile
This document provides an introduction to eXtreme Programming (XP) and agile software development methods. It discusses some common problems with traditional software development approaches such as taking too long, costing too much, and requiring too many people. XP and agile aim to address these problems through principles like rapid delivery of working software in short iterations, frequent feedback, simplicity, respect, and flexibility. The document outlines XP practices like user stories, pair programming, test-driven development, and daily standups that embody these principles. It concludes by noting that agile methods have evolved over decades to become more effective approaches to software development.
Mob Programming for Continuous Learning
This document discusses mob programming and ways to reduce feedback loops in coding. It describes the author's experience with mob programming on different projects involving 3-5 co-located programmers and sometimes remote members. Key aspects of mob programming discussed are strong-style pairing with designated driver and navigator roles, increased ownership and resilience from the whole team working on the same thing, and benefits like more just-in-time design discussions. The author also notes some challenges of mob programming including less flexibility and that it can look unusual to outsiders. Overall mob programming is presented as an effective way to continuously learn through reflection on shared work.
Why Do User Research And Usability Testing
User research and usability testing are important to remove obstacles for users and maximize benefits. Usability issues can reduce financial gains, damage a company's reputation, and lead to poor product results. While developers may think they know what users need, usability is best understood through field studies and user interviews rather than assumptions. User research should begin early in the design process to gather important insights into the interface design. Usability testing, even on a small scale, can provide valuable feedback to improve the user experience.
Agile xp crash_course_2010_05_21
This document provides an overview of Agile and eXtreme Programming (XP), including the core values and principles of the Agile Manifesto, roles and practices in XP, and how to adopt and apply XP to projects. It discusses key aspects of XP like short iterations, user stories, frequent releases, test-driven development, refactoring, collective code ownership, and more. The goal is to give the reader a crash course in Agile and XP methodologies.
Tdd 4 everyone full version
This document discusses test-driven development (TDD) and its importance for software development. It notes that TDD is not just about unit testing code, but is a key part of software craftsmanship. When practicing TDD, tests should be written from the perspective of understanding by business analysts and customers, not just for code implementation. TDD promotes a short feedback loop to continually refine code through testing. Examples provided demonstrate how to use TDD for a FizzBuzz coding exercise by first writing tests to define requirements and then coding to pass those tests.
Vesterli worst adf_project_ever_wildcard_2013
The document discusses 10 common things that can go wrong in projects, especially those using Oracle Application Development Framework (ADF). Some key issues include: 1) not having direct access to end users can lead to misunderstandings of requirements, 2) starting a project with a full team without establishing architecture can result in inconsistent development, and 3) feature creep and changing requirements can be difficult to accommodate and lead to delays if not managed properly. The document provides warnings and recommendations around these and other common pitfalls to help projects avoid issues and deliver on time and on budget.
2013 09-11 java zone - extreme programming live
The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk demonstrates test-driven development and pair programming. It discusses the benefits of these practices, such as producing higher quality code through simplicity, communication, and feedback. It encourages programmers to practice deliberately, both at work and at home, in order to continuously improve. The conclusion emphasizes freeing the mind and practicing programming as an art.
Life of a Tester v1
The document discusses the importance of software testing and the role of testers. It covers topics like why testing is important to ensure software quality, the role of testers in finding defects and maintaining quality, skills needed for testers like analytical thinking and communication, and reasons why software testing is a good career path, such as work-life balance and job satisfaction from finding issues. It also lists thought leaders in the software testing field and their Twitter handles.
Agile 2 - The Next Iteration of Agile - Lisa Cooney for Agile Nova 7-29-2021
Agile 2 - The Next Iteration of Agile - Lisa Cooney for Agile Nova 7-29-2021Lisa Boyer Cooney (she/her)
This document summarizes an Agile 2 conference presentation about the next iteration of Agile. It discusses criticisms of how Agile has been implemented, focusing on issues like lack of documentation, QA, and architecture. It also notes problems with tribalism around specific frameworks. The presentation team proposes principles for Agile 2 that emphasize balance, leadership, experimentation, and openness. The goal is to bring Agile back to its roots while addressing real-world problems.Continuous Deployment Through Technical Excellence
This document discusses continuous deployment and what is required to achieve it. Continuous deployment means code is always deployed to production. It requires version control, build/deploy pipelines, infrastructure as code, frequent and safe code updates, separation of rollout and activation, and good observability. Achieving it also requires changes to testing, coding, organization, planning, and learning practices. The document recommends starting with improving deployment frequency metrics and removing impediments through small experiments. It emphasizes improving incrementally based on what teams are passionate about or experiencing pain with.
Loosely Coupled Complexity - Unleash the power of your Domain Model with Comm...
The document discusses the disadvantages of an anemic domain model, where business logic is separated from the domain objects, making the model hard to maintain, test, and prone to duplication. It also suggests that a domain model should contain behavior, use the ubiquitous language, define aggregates as consistency boundaries, and protect the model with bounded contexts.
What Software Quality Assurance Means to Me
Software quality assurance means delivering useful features one at a time through a test-first methodology. Test-driven development gives confidence to experiment and serves as a benchmark for classes, with unit tests serving as regression tests. It allows senior developers to hand functional tests to junior developers to implement, focusing on outcomes over specific implementations. Both internal and external quality are important, with ambiguous APIs hindering productivity. Good development involves collaboration, even for solo projects, and smoke tests should always be run before sharing code with others.
Ilari henrik
The document discusses various confusions and misconceptions around software testing. It argues that there is no such thing as "manual testing" and instead testing should be viewed on a spectrum of degree of interactivity and tool support. It also discusses how testing is providing quality-related information about a product efficiently to stakeholders, and how testing involves experimentation rather than just checking. The document emphasizes the importance of understanding complex environments using the Cynefin model, and developing personal qualities like curiosity, precision, and community involvement to continually learn and improve testing practices.
Introduction to bdd
Behaviour Driven Development from the ground up. Non-technical introduction that motivates the adoption of BDD.
Best viewed as a video. Should be followed by Matt Wynne's session "BDD can save your agile"
This slide deck was orignally prepared by Steve Tooke for CukeUp AU and then modified and presented by Seb Rose to
Good Code / Bad Code
Check out SPADE, a framework for crafting quality with code. This presentation highlights five topics that designers and developers should be covering throughout design and development.
Agile testingandautomation
1. The document discusses lessons learned about agile testing and automation. It emphasizes that testing is more than just checking and that both automated and exploratory testing are important.
2. It recommends automating output checking where possible but also using exploratory testing. It also stresses the importance of unit, integration and end-to-end tests as well as code reviews.
3. The document advocates for test-driven development and notes how automated tests can reduce regression testing time. It emphasizes that successful testing requires collaboration between developers, testers and business stakeholders.
Hiring a developer: step by step debugging
The document provides guidance on hiring developers based on Joel Spolsky's book "The Ultimate Developer Recruiting Guide". It summarizes the key steps in Spolsky's hiring process: conducting interviews that last at least an hour and involve both technical exercises and allowing candidates to interview the hiring manager; focusing on finding candidates that are both smart and able to get things done; and emphasizing the importance of treating candidates and employees well to attract and retain top talent.
Small Hyper-Productive Teams (IT Brunch)
Presentation from IT Brunch online conference "Visiting Agile practitioners" (November 2011) about building of small hyper-productive teams and managing them to drive projects to success.
Development without Testers: Myth or Real Option?
Presentation from XP Days Ukraine (December, 2011) and QADnepr Mini Conference (Dnepropetrovsk, October 2011) about true role of testers and ways to fix development process to avoid their participation in usual stages of the quality control chain.
Become Software Tester or Developer
This is the slide deck that Director of Delivery of KMS presented at Can Tho University on Saturday, September 28th, 2013.
L'illusione dell'ortogonalità
Cosa abbiamo scoperto in questi 20 anni? Che cercare di cambiare il mondo focalizzandoci su un singolo aspetto, il processo, il TDD, il clean code, non porta da nessuna parte. I veri cambiamenti avvengono quando scopriamo le reali interazioni tra le parti, quando lasciamo la specializzazione e cominciamo a vedere il vero quadro d'insieme.
In questo talk vedremo come scelte architetturali apparentemente innocue, finiscano per impattare il processo, ed in generale di come processi, pratiche, architetture, persone e scelte di business non possano essere considerate come elementi disaccoppiati tra loro.
User Stories
This presentation provides the who, what, why, how, and when for user stories. It shows you examples of good and bad stories, how to get them in the first place, and how they define done on agile projects.
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
More Related Content
What's hot
Mob Programming for Continuous Learning
This document discusses mob programming and ways to reduce feedback loops in coding. It describes the author's experience with mob programming on different projects involving 3-5 co-located programmers and sometimes remote members. Key aspects of mob programming discussed are strong-style pairing with designated driver and navigator roles, increased ownership and resilience from the whole team working on the same thing, and benefits like more just-in-time design discussions. The author also notes some challenges of mob programming including less flexibility and that it can look unusual to outsiders. Overall mob programming is presented as an effective way to continuously learn through reflection on shared work.
Why Do User Research And Usability Testing
User research and usability testing are important to remove obstacles for users and maximize benefits. Usability issues can reduce financial gains, damage a company's reputation, and lead to poor product results. While developers may think they know what users need, usability is best understood through field studies and user interviews rather than assumptions. User research should begin early in the design process to gather important insights into the interface design. Usability testing, even on a small scale, can provide valuable feedback to improve the user experience.
Agile xp crash_course_2010_05_21
This document provides an overview of Agile and eXtreme Programming (XP), including the core values and principles of the Agile Manifesto, roles and practices in XP, and how to adopt and apply XP to projects. It discusses key aspects of XP like short iterations, user stories, frequent releases, test-driven development, refactoring, collective code ownership, and more. The goal is to give the reader a crash course in Agile and XP methodologies.
Tdd 4 everyone full version
This document discusses test-driven development (TDD) and its importance for software development. It notes that TDD is not just about unit testing code, but is a key part of software craftsmanship. When practicing TDD, tests should be written from the perspective of understanding by business analysts and customers, not just for code implementation. TDD promotes a short feedback loop to continually refine code through testing. Examples provided demonstrate how to use TDD for a FizzBuzz coding exercise by first writing tests to define requirements and then coding to pass those tests.
Vesterli worst adf_project_ever_wildcard_2013
The document discusses 10 common things that can go wrong in projects, especially those using Oracle Application Development Framework (ADF). Some key issues include: 1) not having direct access to end users can lead to misunderstandings of requirements, 2) starting a project with a full team without establishing architecture can result in inconsistent development, and 3) feature creep and changing requirements can be difficult to accommodate and lead to delays if not managed properly. The document provides warnings and recommendations around these and other common pitfalls to help projects avoid issues and deliver on time and on budget.
2013 09-11 java zone - extreme programming live
The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk demonstrates test-driven development and pair programming. It discusses the benefits of these practices, such as producing higher quality code through simplicity, communication, and feedback. It encourages programmers to practice deliberately, both at work and at home, in order to continuously improve. The conclusion emphasizes freeing the mind and practicing programming as an art.
Life of a Tester v1
The document discusses the importance of software testing and the role of testers. It covers topics like why testing is important to ensure software quality, the role of testers in finding defects and maintaining quality, skills needed for testers like analytical thinking and communication, and reasons why software testing is a good career path, such as work-life balance and job satisfaction from finding issues. It also lists thought leaders in the software testing field and their Twitter handles.
Agile 2 - The Next Iteration of Agile - Lisa Cooney for Agile Nova 7-29-2021
Agile 2 - The Next Iteration of Agile - Lisa Cooney for Agile Nova 7-29-2021Lisa Boyer Cooney (she/her)
This document summarizes an Agile 2 conference presentation about the next iteration of Agile. It discusses criticisms of how Agile has been implemented, focusing on issues like lack of documentation, QA, and architecture. It also notes problems with tribalism around specific frameworks. The presentation team proposes principles for Agile 2 that emphasize balance, leadership, experimentation, and openness. The goal is to bring Agile back to its roots while addressing real-world problems.Continuous Deployment Through Technical Excellence
This document discusses continuous deployment and what is required to achieve it. Continuous deployment means code is always deployed to production. It requires version control, build/deploy pipelines, infrastructure as code, frequent and safe code updates, separation of rollout and activation, and good observability. Achieving it also requires changes to testing, coding, organization, planning, and learning practices. The document recommends starting with improving deployment frequency metrics and removing impediments through small experiments. It emphasizes improving incrementally based on what teams are passionate about or experiencing pain with.
Loosely Coupled Complexity - Unleash the power of your Domain Model with Comm...
The document discusses the disadvantages of an anemic domain model, where business logic is separated from the domain objects, making the model hard to maintain, test, and prone to duplication. It also suggests that a domain model should contain behavior, use the ubiquitous language, define aggregates as consistency boundaries, and protect the model with bounded contexts.
What Software Quality Assurance Means to Me
Software quality assurance means delivering useful features one at a time through a test-first methodology. Test-driven development gives confidence to experiment and serves as a benchmark for classes, with unit tests serving as regression tests. It allows senior developers to hand functional tests to junior developers to implement, focusing on outcomes over specific implementations. Both internal and external quality are important, with ambiguous APIs hindering productivity. Good development involves collaboration, even for solo projects, and smoke tests should always be run before sharing code with others.
Ilari henrik
The document discusses various confusions and misconceptions around software testing. It argues that there is no such thing as "manual testing" and instead testing should be viewed on a spectrum of degree of interactivity and tool support. It also discusses how testing is providing quality-related information about a product efficiently to stakeholders, and how testing involves experimentation rather than just checking. The document emphasizes the importance of understanding complex environments using the Cynefin model, and developing personal qualities like curiosity, precision, and community involvement to continually learn and improve testing practices.
Introduction to bdd
Behaviour Driven Development from the ground up. Non-technical introduction that motivates the adoption of BDD.
Best viewed as a video. Should be followed by Matt Wynne's session "BDD can save your agile"
This slide deck was orignally prepared by Steve Tooke for CukeUp AU and then modified and presented by Seb Rose to
Good Code / Bad Code
Check out SPADE, a framework for crafting quality with code. This presentation highlights five topics that designers and developers should be covering throughout design and development.
Agile testingandautomation
1. The document discusses lessons learned about agile testing and automation. It emphasizes that testing is more than just checking and that both automated and exploratory testing are important.
2. It recommends automating output checking where possible but also using exploratory testing. It also stresses the importance of unit, integration and end-to-end tests as well as code reviews.
3. The document advocates for test-driven development and notes how automated tests can reduce regression testing time. It emphasizes that successful testing requires collaboration between developers, testers and business stakeholders.
Hiring a developer: step by step debugging
The document provides guidance on hiring developers based on Joel Spolsky's book "The Ultimate Developer Recruiting Guide". It summarizes the key steps in Spolsky's hiring process: conducting interviews that last at least an hour and involve both technical exercises and allowing candidates to interview the hiring manager; focusing on finding candidates that are both smart and able to get things done; and emphasizing the importance of treating candidates and employees well to attract and retain top talent.
Small Hyper-Productive Teams (IT Brunch)
Presentation from IT Brunch online conference "Visiting Agile practitioners" (November 2011) about building of small hyper-productive teams and managing them to drive projects to success.
Development without Testers: Myth or Real Option?
Presentation from XP Days Ukraine (December, 2011) and QADnepr Mini Conference (Dnepropetrovsk, October 2011) about true role of testers and ways to fix development process to avoid their participation in usual stages of the quality control chain.
Become Software Tester or Developer
This is the slide deck that Director of Delivery of KMS presented at Can Tho University on Saturday, September 28th, 2013.
L'illusione dell'ortogonalità
Cosa abbiamo scoperto in questi 20 anni? Che cercare di cambiare il mondo focalizzandoci su un singolo aspetto, il processo, il TDD, il clean code, non porta da nessuna parte. I veri cambiamenti avvengono quando scopriamo le reali interazioni tra le parti, quando lasciamo la specializzazione e cominciamo a vedere il vero quadro d'insieme.
In questo talk vedremo come scelte architetturali apparentemente innocue, finiscano per impattare il processo, ed in generale di come processi, pratiche, architetture, persone e scelte di business non possano essere considerate come elementi disaccoppiati tra loro.
What's hot (20)
Agile 2 - The Next Iteration of Agile - Lisa Cooney for Agile Nova 7-29-2021
Agile 2 - The Next Iteration of Agile - Lisa Cooney for Agile Nova 7-29-2021
Continuous Deployment Through Technical Excellence
Continuous Deployment Through Technical Excellence
Loosely Coupled Complexity - Unleash the power of your Domain Model with Comm...
Loosely Coupled Complexity - Unleash the power of your Domain Model with Comm...
Similar to User Stories
User Stories
This presentation provides the who, what, why, how, and when for user stories. It shows you examples of good and bad stories, how to get them in the first place, and how they define done on agile projects.
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
User Stories
User stories are short descriptions of a software feature written from the perspective of the end user. They should be independent, negotiable, valuable, and testable. Good practices for writing user stories include involving customers and users, modeling different user roles, and using techniques like interviews and workshops to gather requirements. Acceptance tests validate that a story's functionality meets the customer's expectations.
How UXD Can Provide Leadership Skills for Complex Software Projects: A 4-Day ...
The document summarizes a 4-day plan for UX designers to provide leadership on complex software projects. Day 1 involves identifying key entities, relationships, and tasks. Day 2 focuses on mapping typical user flows and exceptions. Day 3 is spent developing flow maps from the use cases. Day 4 presents the results to reach consensus and confirm decisions. The plan argues that UX techniques can bring order to chaotic projects and help practitioners take a leadership role.
absodbaosibdoiabn
This document provides information on marketing resume writing and tips for an effective resume. It includes sections on marketing, summaries, relevant experience, personal skills, technical skills tables, work experience examples, active verbs, education, and concludes with a thank you. The overall document aims to help candidates strengthen their resume and highlight their qualifications for marketing roles.
Better Software Keynote The Complete Developer 07
Luke Hohmann's keynote for Better Software conference on characteristics that execs want in their ideal developer.
Better Software Keynote The Complete Developer 07
Luke Hohmann's keynote for Better Software conference on what execs think make up the Complete Developer. Much more than coding skills.
The Whole Story of The User Story
Through the webinar, she will give an introduction to the user story concept. How to create them? How they can help us build better products for our customers. Do's and Don'ts.
Patton user modeling
The document discusses different models for understanding software users, including personas, profiles, actors, and roles. It provides examples of how to build profiles of different user types by making assumptions about their goals, tasks, skills, and context of use. The profiles can then be backfilled with facts from user research. Well-developed user models help software teams empathize with users and prioritize the most important user needs and design requirements.
From Use to User Interface
The document provides an overview of a workshop on user interface design using paper prototyping techniques. It discusses various models for understanding user needs, including Garrett's Elements of User Experience model. It then describes how to build a paper prototype, test it with users, identify issues, fix them, and retest in an iterative process. The goal is to design an interface that meets user needs and supports their tasks through participatory design activities like writing user stories, scenarios, and tests with paper prototypes.
The Collaborative UX Professional's Toolkit
Presentation from UXPA Boston 2013: The Collaborative UX Professional's Toolkit
Presented by Andrew Wirtanen and myself.
Art of Writing in Agile : STC Summit 2017
Please find enclosed the presentation on "Art of Writing in Agile" that I recently presented, during #STCSummit2017 #stc #stc2017 in Washington DC on 9th May, 2017.
recapitulando: de métodos ágeis até lean startup
This document discusses various agile methodologies including extreme programming (XP), scrum, lean UX, lean startups, and behavior driven development (BDD). It emphasizes the importance of committed people, flat maintenance costs, delivering quality software frequently, validating business assumptions, and maximizing delivered value. The key aspects of XP, scrum, and lean startup are summarized including roles, meetings, practices, and how they aim to achieve frequent delivery with a focus on the customer and business value.
Templates.pptx
The document describes several prioritization methods including MoSCoW, Kano Model, Feasibility-Desirability-Viability, Value/Effort Scale, and Customer Journey Mapping. MoSCoW categorizes requirements as Must have, Should have, Could have, and Won't have. The Kano Model sorts features into basic, performance, and delighter categories. Feasibility-Desirability-Viability rates ideas based on those three factors. Value/Effort Scale maps features on a grid based on effort to implement and business value. Customer Journey Mapping traces a user's experience through touchpoints.
User Stories explained
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.
UX Prototyping and Personas 9-5-14
This document discusses UX prototyping and personas as essential tools for creating great user experiences. It provides an overview of different prototyping methods like paper prototyping, digital tools like Balsamiq and Fireworks, and the benefits of each. It also covers what personas are, how to develop them, and how prototyping can be improved by focusing on specific persona goals and needs. The document encourages prototyping as early as possible using whatever tools are available and provides various activities to prototype interfaces using different methods.
SAD01 - An Introduction to Systems Analysis and Design
The document discusses software analysis and design. It introduces a case study of a large multiplayer online game called Epitaph that will be used to illustrate analysis and design concepts. Analysis involves generating an understanding of a system through techniques like object-oriented modeling. Design details how the system will function by showing interactions and interfaces through diagrams. The goal is effective communication between developers and stakeholders.
Writing Effective User Stories
This document discusses writing effective user stories for agile software development. It defines what user stories are, how they follow the INVEST model, and how to gather and manage user stories through techniques like user role modeling, interviews, observation, and workshops. It also covers pros and cons of the user story approach.
Data Science - Experiments
Three experiments I have done with data science. Related to text analysis, integration. Focusing on the learning's rather than details on how it was done with source code. I feel it is important to see this subject in relation to business problems rather than as pure branch of Statistics. Focusing on what has to be done enabled me to find the right solution from a complicated and very interesting subject.
Effective User Stories
The document discusses user stories for software requirements. It provides tips for writing good user stories, such as starting with user goals, writing smaller stories for soon-to-be-implemented functionality, keeping the user interface out of stories initially, and having the customer rather than developer write stories. It also identifies "smelly" user stories, such as those that are too small, interdependent, include too many details, or are written too far in advance.
Similar to User Stories (20)
How UXD Can Provide Leadership Skills for Complex Software Projects: A 4-Day ...
How UXD Can Provide Leadership Skills for Complex Software Projects: A 4-Day ...
SAD01 - An Introduction to Systems Analysis and Design
SAD01 - An Introduction to Systems Analysis and Design
User Stories
- 1. User Stories James Peckham (Extracted from Mike Cohn’s Book “User Stories Applied”)
- 16. Writing Stories Chapter 2
- 24. User role Modeling Chapter 3
- 41. Working with user proxies Chapter 5
- 52. Acceptance Testing User Stories Chapter 6
- 61. Guidelines for good stories Chapter 7
- 75. Estimating and Planning PART II
- 88. Planning a release Chapter 9
- 102. Planning an iteration Chapter 10
- 114. Part III FAQ