Cargando…
User stories applied : for agile software development /
Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with "user stories": sim...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Boston :
Addison-Wesley,
©2004.
|
| Colección: | Addison-Wesley signature series.
|
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
MARC
| LEADER | 00000cam a2200000Ia 4500 | ||
|---|---|---|---|
| 001 | OR_ocm57365091 | ||
| 003 | OCoLC | ||
| 005 | 20231017213018.0 | ||
| 006 | m o d | ||
| 007 | cr unu|||||||| | ||
| 008 | 050104s2004 maua ob 001 0 eng d | ||
| 010 | |z 2004043655 | ||
| 040 | |a OCL |b eng |e pn |c OCL |d OCLCQ |d OCLCG |d CEF |d OCLCQ |d OCLCE |d NRC |d IDEBK |d OCLCQ |d OCLCF |d OCLCO |d OCLCQ |d YDX |d N$T |d OCLCQ |d AU@ |d WYU |d UAB |d VT2 |d HS0 |d ERF |d UKBTH |d UKAHL |d LDP |d TOH |d OCLCO |d INARC |d LVT |d TAC |d OCLCQ | ||
| 019 | |a 607155889 |a 607799184 |a 667061214 |a 729549894 |a 748094367 |a 759522168 |a 809688689 |a 1056375403 |a 1061013228 |a 1064016484 |a 1074319904 |a 1083176732 |a 1103276031 |a 1104493158 |a 1108993041 |a 1112549722 |a 1129359049 |a 1153023646 |a 1159657767 |a 1181155399 |a 1192338848 |a 1224591107 |a 1240509855 |a 1285850239 |a 1302291550 |a 1302705058 | ||
| 020 | |a 9780132702645 |q (electronic bk.) | ||
| 020 | |a 0132702649 |q (electronic bk.) | ||
| 020 | |z 9780321205681 | ||
| 020 | |z 0321205685 | ||
| 020 | |a 1282433164 | ||
| 020 | |a 9781282433168 | ||
| 020 | |a 9786612433160 | ||
| 020 | |a 6612433167 | ||
| 020 | |a 0321680359 | ||
| 020 | |a 9780321680358 | ||
| 024 | 8 | |a 9780321205681 | |
| 024 | 8 | |a 0321205685 | |
| 029 | 1 | |a AU@ |b 000057222082 | |
| 029 | 1 | |a HEBIS |b 291436250 | |
| 029 | 1 | |a AU@ |b 000067112843 | |
| 035 | |a (OCoLC)57365091 |z (OCoLC)607155889 |z (OCoLC)607799184 |z (OCoLC)667061214 |z (OCoLC)729549894 |z (OCoLC)748094367 |z (OCoLC)759522168 |z (OCoLC)809688689 |z (OCoLC)1056375403 |z (OCoLC)1061013228 |z (OCoLC)1064016484 |z (OCoLC)1074319904 |z (OCoLC)1083176732 |z (OCoLC)1103276031 |z (OCoLC)1104493158 |z (OCoLC)1108993041 |z (OCoLC)1112549722 |z (OCoLC)1129359049 |z (OCoLC)1153023646 |z (OCoLC)1159657767 |z (OCoLC)1181155399 |z (OCoLC)1192338848 |z (OCoLC)1224591107 |z (OCoLC)1240509855 |z (OCoLC)1285850239 |z (OCoLC)1302291550 |z (OCoLC)1302705058 | ||
| 050 | 4 | |a QA76.76.D47 |b C643 2004 | |
| 072 | 7 | |a COM |x 051230 |2 bisacsh | |
| 082 | 0 | 4 | |a 005.1 |2 22 |
| 084 | |a ST 230 |2 rvk | ||
| 049 | |a UAMI | ||
| 100 | 1 | |a Cohn, Mike, |d 1962- | |
| 245 | 1 | 0 | |a User stories applied : |b for agile software development / |c Mike Cohn. |
| 260 | |a Boston : |b Addison-Wesley, |c ©2004. | ||
| 300 | |a 1 online resource (xxi, 268 pages) : |b illustrations. | ||
| 336 | |a text |b txt |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 347 | |a text file | ||
| 490 | 1 | |a Addison-Wesley signature series | |
| 500 | |a "A Kent Beck signature book." | ||
| 504 | |a Includes bibliographical references (pages 259-262) and index. | ||
| 588 | 0 | |a Print version record. | |
| 505 | 0 | |a Foreword. Acknowledgments. Introduction. I: GETTING STARTED. 1: An Overview. What Is a User Story? Where Are the Details? "How Long Does It Have to Be?" The Customer Team. What Will the Process Be Like? Planning Releases and Iterations. What Are Acceptance Tests? Why Change? Summary. Questions. 2: Writing Stories. Independent. Negotiable. Valuable to Purchasers or Users. Estimatable. Small. Testable. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 3: User Role Modeling. User Roles. Role Modeling Steps. Two Additional Techniques. What If I Have On-Site Users? Summary. Developer Responsibilities. Customer Responsibilities. Questions. 4: Gathering Stories. Elicitation and Capture Should Be Illicit. A Little Is Enough, or Is It? Techniques. User Interviews. Questionnaires. Observation. Story-Writing Workshops. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 5: Working with User Proxies. The Users' Manager. A Development Manager. Salespersons. Domain Experts. The Marketing Group. Former Users. Customers. Trainers and Technical Support. Business or Systems Analysts. What to Do When Working with a User Proxy. Can You Do It Yourself? Constituting the Customer Team. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 6: Acceptance Testing User Stories. Write Tests Before Coding. The Customer Specifies the Tests. Testing Is Part of the Process. How Many Tests Are Too Many? The Framework for Integrated Test. Types of Testing. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 7: Guidelines for Good Stories. Start with Goal Stories. Slice the Cake. Write Closed Stories. Put Constraints on Cards. Size the Story to the Horizon. Keep the UI Out as Long as Possible. Some Things Aren't Stories. Include User Roles in the Stories. Write for One User. Write in Active Voice. Customer Writes. Don't Number Story Cards. Don't Forget the Purpose. Summary. Questions. II: ESTIMATING AND PLANNING. 8: Estimating User Stories. Story Points. Estimate as a Team. Estimating. Triangulate. Using Story Points. What If We Pair Program? Some Reminders. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 9: Planning a Release. When Do We Want the Release? What Would You Like in It? Prioritizing the Stories. Mixed Priorities. Risky Stories. Prioritizing Infrastructural Needs. Selecting an Iteration Length. From Story Points to Expected Duration. The Initial Velocity. Creating the Release Plan. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 10: Planning an Iteration. Iteration Planning Overview. Discussing the Stories. Disaggregating into Tasks. Accepting Responsibility. Estimate and Confirm. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 11: Measuring and Monitoring Velocity. Measuring Velocity. Planned and Actual Velocity. Iteration Burndown Charts. Burndown Charts During an Iteration. Summary. Developer Res. | |
| 506 | |3 Use copy |f Restrictions unspecified |2 star |5 MiAaHDL | ||
| 533 | |a Electronic reproduction. |b [S.l.] : |c HathiTrust Digital Library, |d 2010. |5 MiAaHDL | ||
| 538 | |a Master and use copy. Digital master created according to Benchmark for Faithful Digital Reproductions of Monographs and Serials, Version 1. Digital Library Federation, December 2002. |u http://purl.oclc.org/DLF/benchrepro0212 |5 MiAaHDL | ||
| 583 | 1 | |a digitized |c 2010 |h HathiTrust Digital Library |l committed to preserve |2 pda |5 MiAaHDL | |
| 520 | |a Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best 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. In User Stories Applied , Mike Cohn 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, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach. | ||
| 546 | |a English. | ||
| 542 | |f Copyright © 2004 by Pearson Education, Inc. |g 2004 | ||
| 590 | |a O'Reilly |b O'Reilly Online Learning: Academic/Public Library Edition | ||
| 650 | 0 | |a Computer software |x Development. | |
| 650 | 6 | |a Logiciels |x Développement. | |
| 650 | 7 | |a COMPUTERS |x Software Development & Engineering |x General. |2 bisacsh | |
| 650 | 7 | |a Computer software |x Development. |2 fast |0 (OCoLC)fst00872537 | |
| 650 | 7 | |a Engineering & Applied Sciences. |2 hilcc | |
| 650 | 7 | |a Computer Science. |2 hilcc | |
| 653 | |a Agile | ||
| 776 | 0 | 8 | |i Print version: |a Cohn, Mike, 1962- |t User stories applied. |d Boston : Addison-Wesley, ©2004 |z 0321205685 |w (DLC) 2004043655 |w (OCoLC)54365622 |
| 830 | 0 | |a Addison-Wesley signature series. | |
| 856 | 4 | 0 | |u https://learning.oreilly.com/library/view/~/0321205685/?ar |z Texto completo (Requiere registro previo con correo institucional) |
| 938 | |a EBSCOhost |b EBSC |n 1596293 | ||
| 938 | |a ProQuest MyiLibrary Digital eBook Collection |b IDEB |n 243316 | ||
| 938 | |a YBP Library Services |b YANK |n 14854413 | ||
| 938 | |a Askews and Holts Library Services |b ASKH |n AH31453255 | ||
| 938 | |a Internet Archive |b INAR |n userstoriesappli0000cohn | ||
| 994 | |a 92 |b IZTAP | ||