Free Ebook Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal
Find the secret to enhance the quality of life by reading this Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal This is a sort of book that you require currently. Besides, it can be your favorite book to read after having this book Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal Do you ask why? Well, Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal is a publication that has various characteristic with others. You could not need to understand who the author is, just how famous the job is. As sensible word, never evaluate the words from that speaks, however make the words as your inexpensive to your life.
Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal
Free Ebook Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal
Just how if there is a site that enables you to search for referred book Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal from all over the globe author? Instantly, the site will be amazing finished. So many book collections can be found. All will be so easy without complicated point to move from site to website to obtain guide Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal really wanted. This is the site that will offer you those requirements. By following this website you can get great deals varieties of publication Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal collections from variants sorts of writer and author preferred in this globe. Guide such as Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal and others can be obtained by clicking nice on web link download.
Checking out Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal is a quite helpful interest and also doing that could be undergone whenever. It means that reading a publication will certainly not limit your task, will not force the time to invest over, and won't spend much cash. It is an extremely affordable as well as reachable point to purchase Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal But, with that extremely cheap thing, you could get something new, Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal something that you never do as well as enter your life.
A new encounter can be gotten by reviewing a publication Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal Even that is this Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal or various other publication collections. We offer this book considering that you could find more points to motivate your ability as well as expertise that will certainly make you a lot better in your life. It will be additionally valuable for the people around you. We suggest this soft file of the book right here. To know how to get this book Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal, find out more here.
You can discover the web link that we provide in website to download Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal By acquiring the affordable cost as well as get finished downloading, you have actually completed to the first stage to obtain this Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal It will certainly be nothing when having bought this publication as well as do nothing. Review it as well as disclose it! Invest your few time to just review some covers of page of this publication Executable Specifications With Scrum: A Practical Guide To Agile Requirements Discovery, By Mario Cardinal to read. It is soft documents as well as very easy to read wherever you are. Enjoy your brand-new habit.
Most books about specifications still assume that requirements can be known up front and won’t change much during your project. In today’s “real world,” however, you must specify and build software in the face of high and continuing uncertainty. Scrum and other agile methods have evolved to reflect this reality. Now, there’s a complete guide to specifying software in agile environments when prerequisites are unclear, requirements are difficult to grasp, and anything about your project could change.
Long-time agile coach and enterprise architect Mario Cardinal shows how to create executable specifications and use them to test software behavior against requirements. Cardinal shows how to trawl requirements incrementally, step-by-step, using a vision-centric and emergent iterative practice that is designed for agility. Writing for analysts, architects, developers, and managers, Cardinal makes a strong case for the iterative discovery of requirements. Then, he moves from theory to practice, fully explaining the technical mechanisms and empirical techniques you need to gain full value from executable specifications.
You’ll learn to connect specifications with software under construction, link requirements to architecture, and automate requirements verification within the Scrum framework. Above all, Cardinal will help you solve the paramount challenge of software development: not only to solve the problem right, but also to solve the right problem.
You will learn how to
• Establish more effective agile roles for analysts and architects
• Integrate and simplify the best techniques from FIT, ATDD, and BDD
• Identify “core certainties” on which your project team should rely to ensure requirements discovery
• Manage uncertainty by discovering stakeholder desires through short feedback loops
• Specify as you go while writing small chunks of requirements
• Use storyboarding and paper prototyping to improve conversations with stakeholders
• Express stakeholder desires that are requirements with user stories
• Refine your user stories, and plan more effective Scrum sprints
• Confirm user stories by scripting behaviors with scenarios
• Transform scenarios into automated tests that easily confirm your software’s expected behavior as designs emerge and specifications evolve
• Ensure higher-quality software by specifying nonfunctional requirements
- Sales Rank: #2774311 in Books
- Brand: Brand: Addison-Wesley Professional
- Published on: 2013-08-08
- Released on: 2013-07-29
- Original language: English
- Number of items: 1
- Dimensions: 9.13" h x .43" w x 7.00" l, .0 pounds
- Binding: Paperback
- 192 pages
- Used Book in Good Condition
About the Author
Known for many years as an agile coach specialized in software architecture, Mario Cardinal is the co-founder of Slingboards Lab, a young start-up that brings sticky notes to smartphones, tablets and the web for empowering teams to better collaborate. A visionary and an entrepreneur, he likes to seize the opportunities that emerge from the unexpected. His friends like to describe him as someone who can extract the essence of a complicated situation, sort out the core ideas from the incidental distractions, and provide a summary that is easy to understand. For the ninth consecutive year, he has received the Most Valuable Professional (MVP) award from Microsoft. MVP status is awarded to credible technology experts who are among the very best community members willing to share their experience to help others realize their potential.
Most helpful customer reviews
4 of 4 people found the following review helpful.
Finally a good book on agile requirements elicitation
By T Anderson
This book is exactly what the sub-title "A Practical Guide to Agile Requirements Discovery" says it is. The book is a very detailed breakdown of the steps that should be taken by Scrum teams that want to succeed.
I have listed the chapters below to give you an overview of the topics the author covers in this book.
Chapter 1. Solving the Right Problem
Chapter 2. Relying on a Stable Foundation
Chapter 3. Discovering Through Short Feedback Loops and Stakeholders' Decrements
Chapter 4. Expressing Desirements with User Stories
Chapter 5. Refining User Stories by Grooming the Product Backlog
Chapter 6. Confirming User Stories with Scenarios
Chapter 7. Automating Confirmation with Acceptance Tests
Chapter 8. Addressing Nonfunctional Requirements
Chapter 9. Conclusion
In the first chapter the author covers how the scrum teams can distinguish requirements from the solution. In other words the what from the hows.
In the second chapter the author shows how to develop guardrails which are basically the artifacts and activities that will keep the project within its defined scope. The examples that the author uses are a healthy team, involvement of all stakeholders, a shared vision, a meaningful common goal, a set of high-level features, and "can-exist" assumption.
In chapter 3 the author really drives home applying the trial and error method for discovering desirements through short feedback loops.
In chapter 4, Expressing Desirements with User Stories, the author does a great job of showing how to create user stories. He does a great job of breaking down the structure of the user story and introducing the questions that you ask when creating them- who, what, and why, questions. The author also touches on the importance of establishing Ubiquitous Language. Ubiquitous Language is a shared team language that defines a certain domain. Chapter 6 also touches on Ubiquitous Language. He ends the chapter by introducing how to use a product backlog to record desirements.
The next chapter, Refining User Stories by Grooming the Product Backlog, is all about roles and activities that need to be in place in order to managing the product backlog correctly. Topics include Managing the Product Backlog, Collaborating to Groom the Product Backlog, Ranking User Stories with a Dot Voting Method, Illustrating User Stories with Storyboards, Sizing User Stories Using Comparison, Splitting User Stories Along Business Values, Tracking User Stories with a Collaboration Board, and Delivering a Coherent Set of User Stories.
Chapter 6 is all about confirming your User Stories by scripting scenarios that validate them. The author also introduces two tools for automating validation. He introduces the Framework for Integrated Test (FIT) and the Given-When-Then syntax the Behavior-Driven Development (BDD) community uses. He also touches on Ubiquitous Language again and its importance.
Chapter 7 is all about automating confirmation, which is done by turning scenarios into acceptance tests. This chapter explains how to make the scenarios "executable" by a computer. The author introduces existing BDD automation frameworks which include Cucumber for Ruby, JBehave for Java, and SpecFlow for Microsoft .NET. I downloaded SpecFlow which is a solid framework backed up by very thorough documentation.
The last chapter before the concluding chapter covers Nonfunctional Requirements (Quality Attributes). Quality attributes are all about tradeoffs and constraints. The author does a great job of explaining quality attributes, showing how they are broken down into internal and external categories, and then applied through constraints (which he calls restrictions).
The two things I like most about this book was the flow of the chapters and the author's recognition of the importance of architecture.
The chapters build on each other so I definitely recommend a cover to cover read of the book. The author has a great writing style, so that is easy to do.
When the author spells out what roles make up a team he includes architects. He defines architects as members of the development team who are responsible for designing the structural foundation upon which the solution is built. Their role is to ensure the development team builds the software right and delivers quality work. I have seen a lot of confusion in Scrum teams when it comes to architecture, because a lot of the Scrum material out there today discounts it.
All in all I found this book a very enjoyable read. If you are involved with agile development teams, you should definitely read this book. The elicitation of requirements is really lacking in most of the agile teams I encounter. This book can help to remedy that.
0 of 0 people found the following review helpful.
"Where's the meat??!!"
By Michael Simpson
Have you ever read a book where the first chapter or two are basically introduction before they get to "the good stuff"? This book seemed like it never got past the introduction - I read the first few chapters, and started skimming at chapter 5, wondering when the book was going to get meaty and introduce some good, useful information. By the time I reached the end, I was still wondering that. In the end, it was basically an introduction to Cucumber and Fit(nesse), but if you're already familiar with those, you're not going to learn much new.
Also, the book was written in a style that I would call awkward, at best. "Desirements"??!! Why do we need to invent new words?
Overall, I would be willing to recommend any number of books I haven't read as at least being more promising than this one.
0 of 0 people found the following review helpful.
A short little book with good information
By Craig E. Shea
A quick, short read, but it's to the point and has some good information in there. There's no one right way to do Scrum, after all, people over processes and tools, right? Anyway, I found the information useful.
Also, don't get hung up on the title, especially the bit about "Executable Specifications...." I thought this Scrum book might go into detail about applying BDD principles in your scrum activities, but BDD wasn't really touched on at all. The author did make a point, however, to go over the planning process, which was somewhat aligned with BDD, but it's a weak association at best.
Anyway, if you want some info on Scrum (i.e. you're new to Scrum), this book has good information. But, it's just information. Please evaluate the information given and see how it might apply (or might not apply, for that matter) to you and your team.
Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal PDF
Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal EPub
Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal Doc
Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal iBooks
Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal rtf
Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal Mobipocket
Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery, by Mario Cardinal Kindle
