85 Results for : backlog

  • Thumbnail
    Cryptocurrency: How to Invest in Blockchain Technologies like Bitcoin, Ethereum and Litecoin , Hörbuch, Digital, ungekürzt, 90min
    Are you trying to figure out the best way to get started in cryptocurrency? Do you want to learn more about the new currencies? This book is your answer. Cryptocurrency has been with us since Bitcoin was introduced in the year 2009. However, it lately that cryptocurrency has persistently hit financial market headlines bringing in new owners, investors, and traders. The avalanche of new entrants has even clogged some trading platforms resulting in delays and temporary closures. This is due to processing of the overwhelming backlog of applicants who want to join their trading platforms.  Some people have never heard of cryptocurrency. However, there are many who have heard of cryptocurrency but have not found an appropriate source of information that sufficiently addresses their need to be informed and, thus, be enabled to participate in this digital currency revolution. The purpose of this book is to introduce you to the world of cryptocurrency by providing you with crucial information that can help you make the right decision. This book introduces you to the basics of the technology behind cryptocurrency. This is so that you can understand why it differs from other currencies and why it is attracting such a heavy magnitude of attention. While most people know Bitcoin and sometimes treat it as synonymous with cryptocurrency, this book introduces you to other popular cryptocurrencies and upcoming cryptocurrencies. This is so that should you decide to enter the cryptocurrency market, you are able to get a choice that fits your budget, location, and means of buying it.  Being a currency, cryptocurrency is traded just as any other currency is traded in the forex market. The exception is that cryptocurrencies have a unique trading platform. In this book, you will learn some of the best cryptocurrency trading platforms that you can join. ungekürzt. Language: English. Narrator: Mark Rossman. Audio sample: https://samples.audible.de/bk/acx0/117479/bk_acx0_117479_sample.mp3. Digital audiobook in aax.
    • Shop: Audible
    • Price: 9.95 EUR excl. shipping
  • Thumbnail
    Agile Product Management: Product Owner: 26 Tips to Manage Your Product and Work with Scrum Teams , Hörbuch, Digital, ungekürzt, 83min
    Product Owner - Your Job Just Got Easier In this audiobook you will be given a multitude of proven tips to effectively create a product and work with scrum teams. I am confident that this audiobook will enable you to learn a multitude of skills, since it starts by giving you a full introduction to the concept of scrum and agile product development, scrum and agile principles, and a host of other valuable information that will give you a full understanding of the topic. I then walk you through the process of understanding your role as a product owner, how your role differs from that of a traditional product manager, how to create products, and a lot more. Once you've learned all that, I will then give you valuable tips for effectively creating a product and working with teams. As you go through the class, you will come across a wide range of practical examples that you can use to understand the scrum framework a lot better. This audiobook is broken up into easy-to-digest parts. In it you will learn: A brief recap of agile and scrum, its principles, and other concepts involved in scrum What your job as a product owner entails and how your work differs from that of a typical product manager How to create a product using the scrum framework How product creation in scrum differs from other agile frameworks, like the waterfall method How to create a product road map Tips that you can follow to create your product and to manage your scrum team So let's get started, and let me teach you how to improve product backlog management. Table of contents: Agile Product Management Product Owner Tips to Manage Your Product and Work with Scrum Teams Introduction Scrum Methodology: The Basics What Is Agile? What Is Scrum? Sprints Scrum Team (Also Refe ungekürzt. Language: English. Narrator: Randal Schaffer. Audio sample: https://samples.audible.de/bk/acx0/062235/bk_acx0_062235_sample.mp3. Digital audiobook in aax.
    • Shop: Audible
    • Price: 9.95 EUR excl. shipping
  • Thumbnail
    Essential Scrum (eBook, PDF)
    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 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. 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 Scrum Master 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
    • Shop: buecher
    • Price: 29.99 EUR excl. shipping
  • Thumbnail
    Agile Product Management: Product Owner: 27 Tips to Manage Your Product & Agile: The Complete Overview of Agile Principles and Practices , Hörbuch, Digital, ungekürzt, 177min
    Agile product management just got easier! Product Owner: 27 Tips to Manage Your Product and Work with Scrum Teams: In this class, you will be given a multitude of proven tips to effectively create a product and work with scrum teams. I am confident that this class will enable you to learn a multitude of skills since it starts by giving you a full introduction to the concept of scrum and agile product development, scrum and agile principles, and a host of other valuable information that will give you a full understanding of the topic. I then walk you through the process of understanding your role as a product owner, how your role differs from that of a traditional product manager, how to create products, and a lot more. Once you've learnt all that, I will then give you valuable tips for effectively creating a product and working with teams. As you go through the class, you will come across a wide range of practical examples that you can use to understand the scrum framework a lot better. To break this class into easy-to-digest parts, you will learn: A brief recap of agile and scrum, its principles and other concepts involved in scrum What your job as a product owner entails and how your work differs from that of a typical product manager How to create a product using the scrum framework How product creation in scrum differs from other agile frameworks like the Waterfall method How to create a product roadmap 27 tips that you can follow to create your product and to manage your scrum team So let's get started and let me teach you how to improve product backlog management. Thank you and congratulations on taking this class, Agile: The Complete Overview of Agile Principles and Practices. In this class you will be given a complete overview of agile principles and practices used to deliver projects. I know you will get value from this class as it gives ungekürzt. Language: English. Narrator: Randal Schaffer. Audio sample: https://samples.audible.de/bk/acx0/094884/bk_acx0_094884_sample.mp3. Digital audiobook in aax.
    • Shop: Audible
    • Price: 9.95 EUR excl. shipping
  • Thumbnail
    User Stories Applied
    Learn to build robust software that more closely meets the customer's needs through applying the concept of user stories. A clear explanation of the most agile means of gathering software requirements Thoroughly reviewed and eagerly anticipated by the agile software development community Allows the reader to save time and resources by gathering the proper requirements BEFORE coding begins The concept of user stories has its roots as one of the main tenets of Extreme Programming. In simple terms, user stories represent an effective means of gathering requirements from the customer (roughly akin to use cases). This book describes user stories and demonstrates how they can be used to properly plan, manage, and test software development projects. The book highlights both successful and unsuccessful implementations of the concept, and provides sets of questions and exercises that drive home its main points. After absorbing the lessons in this book, readers will be able to introduce user stories in their organizations as an effective means of determining precisely what is required of a software application. Product Description 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. Features + Benefits Learn to build robust software that more closely meets the customer's needs through applying the concept of user stories. ° A clear explanation of the most agile means of gathering software requirements ° Thoroughly reviewed and eagerly anticipated by the agile software development community ° Allows the reader to save time and resources by gathering the proper requirements BEFORE coding begins Backcover Agile requirements: discovering what your users really want. With this book, you will learn to: Flexible, quick and practical requirements that work Save time and develop better software that meets users' needs Gathering user stories -- even when you can't talk to users How user stories work, and how they differ from use cases, scenarios, and traditional requirements Leveraging user stories as part of planning, scheduling, estimating, and testing Ideal for Extreme Programming, Scrum, or any other agile methodology ---------------------------------------------------------------------------------------------------------- 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. ADDISON-WESLEY PROFESSIONAL Boston, MA 02116 www.awprofessional.com ISBN: 0-321-20568-5 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 Responsibilities. Customer Responsibilities. Questions. III: FREQUENTLY DISCUSSED TOPICS. 12: What Stories Are Not. User Stories Aren't IEEE 830. User Stories Are Not Use Cases. User Stories Aren't Scenarios. Summary. Questions. 13: Why User Stories? Verbal Communication. User Stories Are Comprehensible. User Stories Are the Right Size for Planning. User Stories Work for Iterative Development. Stories Encourage Deferring Detail. Stories Support Opportunistic Development. User Stories Encourage Participatory Design. Stories Build Up Tacit Knowledge. Why Not Stories? Summary. Developer Responsibilities. Customer Responsibilities. Questions. 14: A Catalog of Story Smells. Stories Are Too Small. Interdependent Stories. Goldplating. Too Many Details. Including User Interface Detail Too Soon. Thinking Too Far Ahead. Splitting Too Many Stories. Customer Has Trouble Prioritizing. Customer Won't Write and Prioritize the Stories. Summary. Developer Responsibilities. Customer Responsibilities. Questions. 15: Using Stories with Scrum. Scrum Is Iterative and Incremental. The Basics of Scrum. The Scrum Team. The Product Backlog. The Sprint Planning Meeting. The Sprint Review Meeting. The Daily Scrum Meeting. Adding Stories to Scrum. A Case Study. Summary. Questions. 16: Additional Topics. Handling NonFunctional Requirements. Paper or Software? User Stories and the User Interface. Retaining the Stories. Stories for Bugs. Summary. Developer Responsibilities. Customer Responsibilities. Questions. IV: AN EXAMPLE. 17: The User Roles. The Project. Identifying the Customer. Identifying Some Initial Roles. Consolidating and Narrowing. Role Modeling. Adding Personas. 18: The Stories. Stories for Teresa. Stories for Captain Ron. Stories for a Novice Sailor. Stories for a Non-Sailing Gift Buyer. Stories for a Report Viewer. Some Administration Stories. Wrapping Up. 19: Estimating the Stories. The First Story. Advanced Search. Rating and Reviewing. Accounts. Finishing the Estimates. All the Estimates. 20: The Release Plan. Estimating Velocity. Prioritizing the Stories. The Finished Release Plan. 21: The Acceptance Tests.The concept of user stories has its roots as one of the main tenets of ExtremeProgramming. In simple terms, user stories represent an effective means ofgathering requirements from the customer (roughly akin to use cases). Thisbook describes user stories and demonstrates how they can be used to properlyplan, manage, and test software development projects. The book highlightsboth successful and unsuccessful implementations of the concept, and providessets of questions and exercises that drive home its main points. After absorbingthe lessons in this book, readers will be able to introduce user stories in theirorganizations as an effective means of determining precisely what is required ofa software application.
    • Shop: buecher
    • Price: 31.99 EUR excl. shipping
  • Thumbnail
    Backlog Studies
    Backlog Studies: ab 1.99 €
    • Shop: ebook.de
    • Price: 1.99 EUR excl. shipping
  • Thumbnail
    Visual Studio Team Foundation Server 2012
    Visual Studio Team Foundation Server 2012 - Adopting Agile Software Practices: From Backlog to Continuous Feedback: ab 20.99 €
    • Shop: ebook.de
    • Price: 20.99 EUR excl. shipping
  • Thumbnail
    Iterative Business Model Canvas- Entwicklung - Von der Vision zum Produkt-Backlog
    Iterative Business Model Canvas- Entwicklung - Von der Vision zum Produkt-Backlog - Agile Entwicklung von Produkten und Geschäftsmodellen: ab 19.99 €
    • Shop: ebook.de
    • Price: 19.99 EUR excl. shipping
  • Thumbnail
    Iterative Business Model Canvas Development - From Vision to Product Backlog
    Iterative Business Model Canvas Development - From Vision to Product Backlog - Agile Development of Products and Business Models: ab 19.99 €
    • Shop: ebook.de
    • Price: 19.99 EUR excl. shipping
  • Thumbnail
    Visual Studio Team Foundation Server 2012
    Visual Studio Team Foundation Server 2012 - Adopting Agile Software Practices: From Backlog to Continuous Feedback: ab 30.49 €
    • Shop: ebook.de
    • Price: 30.49 EUR excl. shipping

Similar searches: