site hit counter

[RIR]∎ PDF The Agile Business Analyst Moving from Waterfall to Agile Ryland Leyton Barbara Carkenord 9780692481851 Books

The Agile Business Analyst Moving from Waterfall to Agile Ryland Leyton Barbara Carkenord 9780692481851 Books



Download As PDF : The Agile Business Analyst Moving from Waterfall to Agile Ryland Leyton Barbara Carkenord 9780692481851 Books

Download PDF The Agile Business Analyst Moving from Waterfall to Agile Ryland Leyton Barbara Carkenord 9780692481851 Books

Written with special attention to the challenges facing the IT business analyst, The Agile Business Analyst is a fresh, comprehensive introduction to the concepts and practices of Agile software development. It is also an invaluable reference for anyone in the organization who interacts with, influences, or is affected by the Agile development team.

Business analysts will learn the key Agile principles plus valuable tools and techniques for the transition to Agile, including
  • Card writing
  • Story decomposition
  • How to manage cards in an Agile workflow
  • How to successfully respond to challenges about the value of the BA practice (with an “elevator pitch” for quick reference)
Scrum masters, iteration managers, product owners, and developers who have been suddenly thrust into a work environment with a BA will find answers to the many questions they’re facing
  • What does a BA actually do?
  • What’s their role on the team?
  • What should I expect from a BA?
  • How and when should I involve a BA, and what are the limits of their responsibility?
  • How can they help my team increase velocity and/or quality?
People managers and supervisors will discover
  • How the BA fits into the Agile team and SDLC
  • Crucial skills and abilities a BA will need to be successful in Agile
  • How to get the team and the new BA off on the right foot
  • How to explain the BA’s value proposition to others
  • How adding a BA can solve problems in an established team
Executives and directors will find answers to critical questions
  • In an Agile world, are BAs a benefit or just a cost to my organization?
  • How do I get value from a BA in the transition to Agile?
  • Can I get more from my development team by using the BA as a “force multiplier”?
  • What expectations should I be setting for my discipline managers?
With a foreword by Barbara Carkenord, The Agile Business Analyst is a must-read for any analyst working in an Agile environment.

“Fresh insights, practical recommendations, and detailed examples, all presented with an entertaining and enjoyable style. Leyton shares his experience, mentoring his reader to be a more effective analyst. He has hit a home run with this book!”
--Barbara Carkenord, Director, Business Analysis/RMC Learning Solutions

“Leyton does a great job explaining the value of analysis in an Agile environment. If you are a business-analysis practitioner and need help figuring out how you add value to your team, you’ll find this book valuable.”
--Kupe Kupersmith, President, B2T Training

The Agile Business Analyst Moving from Waterfall to Agile Ryland Leyton Barbara Carkenord 9780692481851 Books

I work in an organization where waterfall is the norm and Agile is the new kid in town. As an Analyst that is used to the traditional waterfall artifacts and is well versed in the difference between business requirements and functional requirements, I found this guide invalueable in assisting me to help our product owner to build our first backlog.

His tips on story decomposition are very helpful, but I'd say his notion of Epic to Feature to User seems a bit out of alignment with some of the freely available online resources who tout Theme to Epic to User Story. I'm not sure if there is really difference between the two, or if it's just a different way to say the same thing, but it's worth pointing out.

There are very helpful examples on story card writing, acceptance criteria, and even a case study in the back on a project delivered via waterfall vs the same requirements delivered in Agile.

We pass my copy of this book around freely in our group, it's a go to resource for the whole team who is trying to adapt to Agile in a Waterfall shop. I keep close tabs on this books whereabouts, because I don't want it to vanish into someone's tote bag, never to be seen again.

His webinars on the IIBA website are very helpful too.

Product details

  • Paperback 234 pages
  • Publisher Leyton Publishing; 1 edition (July 25, 2015)
  • Language English
  • ISBN-10 0692481850

Read The Agile Business Analyst Moving from Waterfall to Agile Ryland Leyton Barbara Carkenord 9780692481851 Books

Tags : The Agile Business Analyst: Moving from Waterfall to Agile [Ryland Leyton, Barbara Carkenord] on Amazon.com. *FREE* shipping on qualifying offers. Written with special attention to the challenges facing the IT business analyst, <I><B>The Agile Business Analyst</B></I> is a fresh,Ryland Leyton, Barbara Carkenord,The Agile Business Analyst: Moving from Waterfall to Agile,Leyton Publishing,0692481850,COMPUTERS Software Development & Engineering General
People also read other books :

The Agile Business Analyst Moving from Waterfall to Agile Ryland Leyton Barbara Carkenord 9780692481851 Books Reviews


Fantastic. Really helped our team move from waterfall to agile.
A useful guide
needed it so I ordered it for work
Great, concise, clearly written business book on Agile. Written by a friend and donated to our local library.
Ryland Leyton is a valuable commodity that’s far too rare these days a subject-matter expert who's also a great communicator. This is precisely what a world as complex as that of Agile business analysis needs. Teaching runs in his family, and that background is readily evident in “The Agile Business Analyst.” As you read and study and learn from this excellent book, you'll find yourself thinking, "This guy really knows his stuff." There's something very satisfying as you witness a master craftsman at the top of his game.

The information design and architecture of this engagingly instructional book are flawless. When they’re done right in an academic guidebook, these are the kinds of factors that become “invisible” --- a casual reader might not even notice, at least consciously, how effective the presentation is. But we’ve all seen the opposite scenario, where smooth education is roadblocked by a clunky interface, confusing information hierarchy, or distractingly bad writing. You’ll find none of those weaknesses here.

Mr. Leyton was already well-known in the BA and Agile environment before "The Agile Business Analyst" was published. With this book he brings his expertise onto a national stage. Take advantage of the opportunity to strengthen your own understanding and, with Leyton’s skillful mentoring, become more than just "another smart guy in a room asking questions about technology." “The Agile Business Analyst” is philosophical, it’s practical, it’s eminently valuable in a thousand ways. Highly recommended.
Also posted in LinkedIn

As an Atlanta-based BA, I have seen Ryland Leyton, the author of The Agile Business Analyst, present on the topic before. His trainings at the local IIBA are among the best-attended, due to the richness of his content.

Needless to say, expectations for his new book are quite high. Having completed a first read, I will predict that this book will greatly impact the larger Business Analyst community in the years ahead.

For those transitioning to Agile, the chapters that provide two cases studies will be of particular interest. The first covers a BA’s work on a Waterfall project, while the second tracks the same project if using Agile practices. The two case studies are then compared, which alone makes this book essential reading for BAs.

For those already experienced with Agile, there is enough food for thought here regarding the pain points that most teams face date-driven vs. feature-driven releases, story decomposition, what is “enough,” and the BA’s relation to the other roles on the team. A pleasant surprise is the perspective about working within Matrix-ed organizations and its inherent challenges.

A book like this could have aimed to be The Ultimate Authority, such as Software Requirements by Karl Wiegers and Joy Beatty -- an all-encompassing work that aims to be the canon. The opposite would have been to be an excellent reference guide, such as the Software Requirements Memory Jogger by Ellen Gottesdiener.

Instead, this book aims for practicality over perfection, and succeeds in hitting the “sweet spot” of good business writing 1) Covering vast territory, while providing enough depth to be useful to a practitioner, and 2) keeping the material grounded enough for different audience levels to follow. (Think Seven Steps to Mastering Business Analysis by Barbara Carkenord).

The one area that warranted more coverage in this book is “Sprint Zero.” Although briefly mentioned, the concept continues to have very little written about it in Agile communities (and happens to be greatly impacted by the work of BAs). Also, the chapter on “Common Business Analysis Techniques That Work in Agile” deserves to grow into its own book.

All nitpicking aside, this is a practical and timely book which belongs on a short list of “Essential Reading for Early-Career BAs.” Add Mr. Leyton’s work to the group which includes Discover to Deliver, User Stories Applied, and Seven Steps to Mastering Business Analysis. He succeeds in delivering a great Minimum Viable Product -- a guide for BAs who need to start sprinting in Agile quickly.
I work in an organization where waterfall is the norm and Agile is the new kid in town. As an Analyst that is used to the traditional waterfall artifacts and is well versed in the difference between business requirements and functional requirements, I found this guide invalueable in assisting me to help our product owner to build our first backlog.

His tips on story decomposition are very helpful, but I'd say his notion of Epic to Feature to User seems a bit out of alignment with some of the freely available online resources who tout Theme to Epic to User Story. I'm not sure if there is really difference between the two, or if it's just a different way to say the same thing, but it's worth pointing out.

There are very helpful examples on story card writing, acceptance criteria, and even a case study in the back on a project delivered via waterfall vs the same requirements delivered in Agile.

We pass my copy of this book around freely in our group, it's a go to resource for the whole team who is trying to adapt to Agile in a Waterfall shop. I keep close tabs on this books whereabouts, because I don't want it to vanish into someone's tote bag, never to be seen again.

His webinars on the IIBA website are very helpful too.
Ebook PDF The Agile Business Analyst Moving from Waterfall to Agile Ryland Leyton Barbara Carkenord 9780692481851 Books

0 Response to "[RIR]∎ PDF The Agile Business Analyst Moving from Waterfall to Agile Ryland Leyton Barbara Carkenord 9780692481851 Books"

Post a Comment