Search Results for: writing effective user stories

Blog
Blog

Agiles Produktmanagement Mit Scrum

Agiles Produktmanagement mit Scrum PDF
Author: Roman Pichler
Publisher: dpunkt.verlag
ISBN: 386491437X
Size: 36.10 MB
Format: PDF, Docs
Category : Computers
Languages : de
Pages : 156
View: 4020

Get Book

Agiles Produktmanagement mit Scrum hilft Ihnen, innovative Produkte mit Scrum zu entwickeln. Anhand zahlreicher Praxisbeispiele erklärt das Buch anschaulich und leicht verständlich den Einsatz agiler Produktmanagementkonzepte und -techniken. Hierzu zählen: •Die richtige Anwendung der Product-Owner-Rolle •Der effektive Einsatz einer agilen Produktvision und einer agilen Produkt-Roadmap •Der richtige Umgang mit dem Product Backlog inklusive Priorisierung, User Stories und nichtfunktionaler Anforderungen •Das Erstellen eines realistischen Releaseplans •Das richtige Verhalten des Product Owner in den Sprint-Besprechungen •Die Etablierung der Product-Owner-Rolle im Unternehmen Dieses Buch ist für alle Leser, die als Product Owner arbeiten oder dies vorhaben, sowie für Führungskräfte und Scrum Master, die sich für die Anwendung der Rolle und den Einsatz der Praktiken interessieren.

Writing Effective User Stories

Writing Effective User Stories PDF
Author: Tom Hathaway
Publisher: CreateSpace
ISBN: 9781519100498
Size: 13.94 MB
Format: PDF, Mobi
Category :
Languages : un
Pages : 66
View: 980

Get Book

DescriptionUser Stories are a great method for expressing stakeholder requirements, whether your projects follow an Agile, Iterative, or a Waterfall methodology. This book presents two common User Story structures to help you ensure that your User Stories have all the required components and that they express the true business need as succinctly as possible. It offers 5 simple rules to ensure that your User Stories are the best that they can be. That, in turn, will reduce the amount of time needed in User Story elaboration and discussion with the development team.After reading this book you will be able to:* Translate business needs into well-structured User Stories* Write User Stories that express the what and avoid the how* Apply five simple rules for writing effective User Stories* Clarify assumptions in User Stories by adding context* Identify and remove ambiguous and subjective terms and phrases in User Stories* Select the appropriate format for expressing User Stories for Agile Projects* Write stakeholder requirements in User Story format that solve business problems* Elaborate User Stories to identify measurable non-functional requirementsAuthor's NoteThe term "User Story" is a relative new addition to our language and its definition is evolving. In today's parlance, a complete User Story has three primary components, namely the "Card", the "Conversation", and the "Criteria". Different roles are responsible for creating each component. The "Card" expresses a business need. A representative of the business community is responsible for expressing the business need. Historically (and for practical reasons) the "Card" is the User Story from the perspective of the business community. Since we wrote this book specifically to address that audience, we use the term "User Story" in that context throughout. The "Conversation" is an ongoing discussion between a developer responsible for creating software that meets the business need and the domain expert(s) who defined it (e.g., the original author of the "Card"). The developer initiates the "Conversation" with the domain expert(s) to define the "Criteria" and any additional information the developer needs to create the application. There is much to be written about both the "Conversation" and the "Criteria", but neither component is dealt with in any detail in this publication. A well-written User Story ("Card") can drastically reduce the time needed for the "Conversation". It reduces misinterpretations, misunderstandings, and false starts, thereby paving the way for faster delivery of working software. We chose to limit the content of this publication to the "User Story" as understood by the business community to keep the book focused and address the widest possible audience.

Writing Effective User Stories

Writing Effective User Stories PDF
Author: Thomas and Angela Hathaway
Publisher: BA-Experts
ISBN:
Size: 24.33 MB
Format: PDF, ePub, Docs
Category : Business & Economics
Languages : en
Pages : 66
View: 1350

Get Book

WHAT IS THIS BOOK ABOUT? This Book Is About the “Card” (User Story: Card, Criteria, Conversation) User Stories are a great method for expressing stakeholder requirements, whether your projects follow an Agile, Iterative, or a Waterfall methodology. They are the basis for developers to deliver a suitable information technology (IT) app or application. Well-structured user stories express a single action to achieve a specific goal from the perspective of a single role. When writing user stories, stakeholders knowledgeable about the role should focus on the business result that the IT solution will enable while leaving technology decisions up to the developers. Good user stories are relevant to the project, unambiguous, and understandable to knowledge peers. The best user stories also contain crucial non-functional (quality) requirements, which are the best weapon in the war against unsatisfactory performance in IT solutions. This book presents two common user story structures to help you ensure that your user stories have all the required components and that they express the true business need as succinctly as possible. It offers five simple rules to ensure that your user stories are the best that they can be. That, in turn, will reduce the amount of time needed in user story elaboration and discussion with the development team. This book targets business professionals who are involved with an IT project, Product Owners in charge of managing a backlog, or Business Analysts working with an Agile team. Author’s Note The term “User Story” is a relative new addition to our language and its definition is evolving. In today’s parlance, a complete User Story has three primary components, namely the “Card”, the “Conversation”, and the “Criteria”. Different roles are responsible for creating each component. The “Card” expresses a business need. A representative of the business community is responsible for expressing the business need. Historically (and for practical reasons) the “Card” is the User Story from the perspective of the business community. Since we wrote this book specifically to address that audience, we use the term “User Story” in that context throughout. The “Conversation” is an ongoing discussion between a developer responsible for creating software that meets the business need and the domain expert(s) who defined it (e.g., the original author of the “Card”). The developer initiates the “Conversation” with the domain expert(s) to define the “Criteria” and any additional information the developer needs to create the application. There is much to be written about both the “Conversation” and the “Criteria”, but neither component is dealt with in any detail in this publication. A well-written User Story (“Card”) can drastically reduce the time needed for the “Conversation”. It reduces misinterpretations, misunderstandings, and false starts, thereby paving the way for faster delivery of working software. We chose to limit the content of this publication to the “User Story” as understood by the business community to keep the book focused and address the widest possible audience. WHO WILL BENEFIT FROM READING THIS BOOK? How organizations develop and deliver working software has changed significantly in recent years. Because the change was greatest in the developer community, many books and courses justifiably target that group. There is, however, an overlooked group of people essential to the development of software-as-an-asset that have been neglected. Many distinct roles or job titles in the business community perform business needs analysis for digital solutions. They include: - Product Owners - Business Analysts - Requirements Engineers - Test Developers - Business- and Customer-side Team Members - Agile Team Members - Subject Matter Experts (SME) - Project Leaders and Managers - Systems Analysts and Designers - AND “anyone wearing the business analysis hat”, meaning anyone responsible for defining a future IT solution TOM AND ANGELA’S (the authors) STORY Like all good IT stories, theirs started on a project many years ago. Tom was the super techie, Angela the super SME. They fought their way through the 3-year development of a new policy maintenance system for an insurance company. They vehemently disagreed on many aspects, but in the process discovered a fundamental truth about IT projects. The business community (Angela) should decide on the business needs while the technical team’s (Tom)’s job was to make the technology deliver what the business needed. Talk about a revolutionary idea! All that was left was learning how to communicate with each other without bloodshed to make the project a resounding success. Mission accomplished. They decided this epiphany was so important that the world needed to know about it. As a result, they made it their mission (and their passion) to share this ground-breaking concept with the rest of the world. To achieve that lofty goal, they married and began the mission that still defines their life. After over 30 years of living and working together 24x7x365, they are still wildly enthusiastic about helping the victims of technology learn how to ask for and get the digital (IT) solutions they need to do their jobs better. More importantly, they are more enthusiastically in love with each other than ever before!

Essential Scrum

Essential Scrum PDF
Author: Kenneth S. Rubin
Publisher: mitp Verlags GmbH & Co. KG
ISBN: 3826690478
Size: 61.41 MB
Format: PDF, ePub
Category : Computers
Languages : de
Pages : 480
View: 4625

Get Book

Umfassendes Scrum-Wissen aus der Praxis Mit Vorworten von Mike Cohn und Ron Jeffries Umfassendes Scrum-Wissen auf Team-, Produkt- und Portfolio-Ebene Kernkonzepte, Rollen, Planung und Sprints ausführlich erläutert Auch geeignet zur Vorbereitung auf die Scrum-Zertifizierung Aus dem Inhalt: 1. Teil: Kernkonzepte Scrum-Framework Agile Prinzipien Sprints Anforderungen und User Stories Das Product Backlog Schätzungen und Velocity Technische Schulden 2. Teil: Rollen Product Owner ScrumMaster Entwicklungsteam Strukturen des Scrum-Teams Manager 3. Teil: Planung Scrum-Planungsprinzipien Mehrstufige Planung Portfolio-Planung Visionsfindung/Produktplanung Release-Planung 4. Teil: Sprints Sprint-Planung Sprint-Ausführung Sprint Review Sprint-Retrospektive Dieses Buch beschreibt das Wesen von Scrum – die Dinge, die Sie wissen müssen, wenn Sie Scrum erfolgreich einsetzen wollen, um innovative Produkte und Dienstleistungen zu entwickeln. Es ist entstanden, weil der Autor Kenneth S. Rubin als Agile- und Scrum-Berater oft nach einem Referenzbuch für Scrum gefragt worden ist – einem Buch, das einen umfassenden Überblick über das Scrum-Framework bietet und darüber hinaus die beliebtesten Ansätze für die Anwendung von Scrum präsentiert. Dieses Buch ist der Versuch, die eine entscheidende Quelle für alles Wesentliche über Scrum bereitzustellen. Rubin beleuchtet die Werte, Prinzipien und Praktiken von Scrum und beschreibt bewährte, flexible Ansätze, die Ihnen helfen werden, sie viel effektiver umzusetzen. Dabei liefert er mehr als nur die Grundlagen und weist zudem auf wichtige Probleme hin, die Ihnen auf Ihrem Weg begegnen können. Ob Sie sich nun zum ersten Mal an Scrum versuchen oder es schon seit Jahren benutzen: Dieses Buch weiht Sie in die Geheimnisse des Scrum-Entwicklungsverfahrens ein und vermittelt Ihnen ein umfangreiches Scrum-Wissen auf Team-, Produkt- und Portfolio-Ebene. Für diejenigen, die bereits mit Scrum vertraut sind, eignet es sich als Scrum-Referenz. Rubin hat das Buch nicht für eine bestimmte Scrum-Rolle geschrieben. Stattdessen soll es allen, die direkt oder indirekt mit Scrum zu tun haben, ein gemeinsames Verständnis von Scrum und den Prinzipien, auf denen es beruht, vermitteln. Stellen Sie sich meine Überraschung und mein Entzücken vor, als ich feststellte, dass das Buch praktisch alles behandelt, was man über Scrum wissen muss – sowohl für Anfänger als auch für alte Hasen. Ron Jeffries (aus dem Vorwort) Über den Autor: Kenneth S. Rubin ist zertifizierter Scrum- und Agile-Trainer und -Berater und hilft Unternehmen, ihre Produktentwicklung effektiver und wirtschaftlicher zu gestalten. Er hat inzwischen mehr als 18.000 Menschen in den Bereichen Agile und Scrum, Organisation objektorientierter Projekte und Übergangsmanagement unterwiesen und Hunderten von Unternehmen als Berater zur Seite gestanden. Rubin war der erste Managing Director der weltweit agierenden Scrum Alliance und erfolgreich als Scrum-Product-Owner, ScrumMaster und Entwickler unterwegs.

Extreme Programming

Extreme Programming PDF
Author: Kent Beck
Publisher: Pearson Deutschland GmbH
ISBN: 9783827321398
Size: 44.30 MB
Format: PDF, ePub
Category :
Languages : de
Pages : 186
View: 4717

Get Book


User Stories Applied

User Stories Applied PDF
Author: Mike Cohn
Publisher: Addison-Wesley Professional
ISBN: 9780321205681
Size: 57.24 MB
Format: PDF
Category : Computers
Languages : un
Pages : 268
View: 2008

Get Book

"Offers a requirements process that saves time, eliminates rework, and leads directly to better software. A great way to build software that meets users' needs is to begin with 'user stories': simple, clear, brief descriptions of functionality that will be valuable to real users. ... [the author] provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, [the author] shows how to organize them, prioritize them, and use them for planning, management, and testing"--Back cover.

Writing Effective Use Cases

Writing Effective Use Cases PDF
Author: Alistair Cockburn
Publisher: Addison-Wesley Professional
ISBN:
Size: 65.54 MB
Format: PDF, ePub, Docs
Category : Computers
Languages : un
Pages : 270
View: 4345

Get Book

This guide will help readers learn how to employ the significant power of use cases to their software development efforts. It provides a practical methodology, presenting key use case concepts.

Entwurfsmuster

Entwurfsmuster PDF
Author:
Publisher: Pearson Deutschland GmbH
ISBN: 9783827328243
Size: 14.15 MB
Format: PDF
Category :
Languages : de
Pages : 479
View: 1707

Get Book


Dead Aid

Dead Aid PDF
Author: Dambisa Moyo
Publisher: Haffmans & Tolkemitt
ISBN: 3942989719
Size: 63.63 MB
Format: PDF, ePub, Docs
Category : Social Science
Languages : de
Pages : 236
View: 7525

Get Book

Afrika ist ein armer Kontinent. Ein Kontinent voller Hunger, blutiger Konflikte, gescheiterter Staaten, voller Korruption und Elend. Um zu helfen, adoptieren Prominente afrikanische Halbwaisen und flanieren durch Flüchtlingslager, laden die Gutmenschen unter den Popstars zu Benefiz-Konzerten, und westliche Staaten haben in den letzten 50 Jahren eine Billion Dollar an afrikanische Regierungen gezahlt. Aber trotz Jahrzehnten von billigen Darlehen, nicht rückzahlbaren Krediten, Schuldenerlassen, bilateraler und multilateraler Hilfe steht Afrika schlimmer da als je zuvor. Mit Dead Aid hat Dambisa Moyo ein provokatives Plädoyer gegen Entwicklungshilfe und für Afrika geschrieben. Knapp, faktenreich und zwingend legt sie ihre Argumente dar. Entwicklungshilfe, im Sinne von Geld-Transfers zwischen Regierungen, macht abhängig. Sie zementiert die bestehenden Gegebenheiten, fördert Korruption und finanziert sogar Kriege. Sie zerstört jeden Anreiz, gut zu wirtschaften und die Volkswirtschaft anzukurbeln. Entwicklungshilfe zu beziehen ist einfacher, als ein Land zu sanieren. Im Gegensatz zu Bono und Bob Geldoff weiß Moyo, wovon sie spricht. Die in Sambia geborene und aufgewachsene Harvard-Ökonomin arbeitete jahrelang für die Weltbank. In Dead Aid erklärt sie nicht nur, was die negativen Folgen von Entwicklungshilfe sind und warum China für Afrika eine Lösung und nicht Teil des Problems ist; sie entwirft zudem einen Weg, wie sich Afrika aus eigener Kraft und selbstbestimmt entwickeln kann. In den USA und Großbritannien löste Dead Aid eine hitzige Debatte aus. Es stand mehrere Wochen auf der New York Times Bestsellerliste und wurde vom Sunday Herald zum Buch des Jahres gewählt. Das Time Magazine wählte Dambisa Moyo 2009 zu einer der 100 wichtigsten Persönlichkeiten der Welt.