Hands-On Agile Software Development with JIRA

Great book for Scrummasters, Product Owners, and anyone else that wants to know more about what can be done with JIRA. I found the author articulate and thoughtful about choices he made in what to cover. I definitely would recommend reading this book as a quick start to get a JIRA project up and running or to put together some reports that help explain the team's outcomes.

I used this book along with a free JIRA instance from Atlassian. Due to UI changes, some screenshots may be out of date or different. However, for someone familiar with Agile using another tool, it is easy to follow along and quickly learn JIRA. It's just not the book for a beginner to Agile.

David really breaks things down in a way that is easy to understand and apply. Grom the beginining to the end the clear consise language made it easy to follow for someone not as familiar as Jira. Super helpful and cannot say enough good things!THANKS David

More of a poorly written documentation than a book. I read through the first few and last few pages and determined that it was not worth my time. Also difficult to follow the screenshots.Not recommended. Not even a bit.

Can be hard to follow since the explanations are not pointed out in the pictures and i am lost on most of the attempts. Screen shots of menus are shown instead of their effect or how to navigate TO the menu. The screen shots are way too difficult to read. The flow of examples is not smooth since the examples do not follow the material order, but the point is still made in some of them.Word choice for naming of lesson examples is very confusing when those same words are also used in other contexts, poor choices increase the confusion.High priced considering all these issues and not a great learning tool.Luckily I have found another book that covers Jira quite well, but bummer on the cost of this one.

This seemed to me to be a rewrite of the user guide with very low grade illustrations. Litho was poor making the images unreadable.

When should I use an Epic vs Story, how do we make sure that user stories are thoroughly completed? How do we make sure that interrelated systems retain their relationship?

I am an old-school programmer trying to get up-to-date with new methodology. This is an excellent start for me.