Amazon Vehicles GoldBox Amazon Fashion Learn more nav_sap_plcc_ascpsc Ingrid Fire TV Stick Happy Belly Coffee Totes Amazon Cash Back Offer TheKicks TheKicks TheKicks  Amazon Echo  Echo Dot  Amazon Tap  Echo Dot  Amazon Tap  Amazon Echo Starting at $49.99 All-New Kindle Oasis Florida Georgia Line Water Sports
Profile for Methods & Tools Software Development Magazine > Reviews

Browse

Methods & To...'s Profile

Customer Reviews: 31
Top Reviewer Ranking: 2,908,897
Helpful Votes: 101


Community Features
Review Discussion Boards
Top Reviewers

Guidelines: Learn more about the ins and outs of Your Profile.

Reviews Written by
Methods & Tools Software Development Magazine RSS Feed (Vevey Switzerland)

Show:  
Page: 1 | 2 | 3 | 4
pixel
Quality Code: Software Testing Principles, Practices, and Patterns
Quality Code: Software Testing Principles, Practices, and Patterns
by Stephen Vance
Edition: Paperback
44 used & new from $26.94

5.0 out of 5 stars A great book on how to grow code and quality together., October 28, 2014
There are many books about software testing, but I will put Quality Code in the best that I have read. It presents a philosophy about software testing that has been mine in my software developer life: the programmer is the main person responsible for the quality of its code. Quality Code is a book that I will strongly recommended to every software developer that is convinced that code quality is his main responsibility and not something that will be eventually managed by a QA department elsewhere before delivery. This is a great book on how to grow code and quality together.


The Agile Culture: Leading through Trust and Ownership
The Agile Culture: Leading through Trust and Ownership
by Pollyanna Pixton
Edition: Paperback
Price: $25.37
50 used & new from $9.86

0 of 1 people found the following review helpful
5.0 out of 5 stars The Agile Manifesto values "individuals and interactions over processes and tools, May 12, 2014
I recommend this book to every software development manager or project manager who want to have a better understanding of the people aspects of application development, whether they are using or not an Agile approach to software development. This book will also interest every Agile software developer interested in the people aspects of software development.


Being Agile: Eleven Breakthrough Techniques to Keep You from "Waterfalling Backward"
Being Agile: Eleven Breakthrough Techniques to Keep You from "Waterfalling Backward"
by Scott Will
Edition: Paperback
Price: $27.81
41 used & new from $23.52

4.0 out of 5 stars A structured approach with breakthrough ideas to Agile transformation, March 31, 2014
The goal of the book Eleven Breakthrough Techniques to Keep You from Waterfalling Backward is clearly stated in its first page: "Transforming from a waterfall-based methodology to agile is no small undertaking. This book is for people who may find their team falling back into old habits when the going gets tough or just because an old waterfall approach seems like the right thing to do. It is also for those teams that have adopted agile but do not feel like there has been a significant improvement."

I think that this book achieves its goal of discussing the problems when you try to adopt Agile practices. I will therefore recommend this book to every software developer and project manager involved in this type of transition.


Agile Analytics: A Value-Driven Approach to Business Intelligence and Data Warehousing (Agile Software Development Series)
Agile Analytics: A Value-Driven Approach to Business Intelligence and Data Warehousing (Agile Software Development Series)
by Ken Collier
Edition: Paperback
Price: $40.59
50 used & new from $30.32

2 of 3 people found the following review helpful
4.0 out of 5 stars Agile Practices for All Data-Centered System Development, September 13, 2012
This book aims to provide an adaptation of the Agile development approach to the specific characteristics of Datawarehouse (DW) and Business Intelligence (BI) systems development. The book is well written and well structured. The concepts are illustrated with many anecdotes and examples. An important list of references and further reading material is available at the end of the book. My favorite part is the chapter 6 that deals with evolving design, a key factor for successful agile projects.

I will naturally recommend this book to every developer or manager involved DW and BI projects, but this book has also a much broader appeal. The issues specific DW or BI are not far for every large project, where databases play a major role, as it might be for instance in a mainframe environment. There you usually have to balance the architecture, performance and stability needs expressed on the database and operation sides of your organization with the goal of delivering frequently new working software. With his process of adapting Agile to data analytics, Ken Collier provides also a interesting framework for people that are involved in the transition from a traditional project management structure to an Agile approach.


How Google Tests Software
How Google Tests Software
by James A. Whittaker
Edition: Paperback
Price: $28.48
49 used & new from $18.45

1 of 4 people found the following review helpful
4.0 out of 5 stars For Everybody who Feels Concerned with Software Quality, September 13, 2012
This book describes how Google organizes its software testing process and, more interestingly, how and why it created the current organization. It is organized on the main roles that are specifically involved in software testing at Google: Software Engineer in Test (SET), Test Engineer (TE), Test Engineering Manager. For each of this role, there is an explanation of its activities. This material is completed by some case studies and interviews of people that work for these roles at Google. The book is well written with a lot of interesting concepts about software testing and how to implement it in an organization. This is balanced with the practical view from software testers and software managers at Google that speak about their day-to-day work. I will naturally recommend this book to every software tester and software development manager, but more broadly to everybody who feels concerned with quality in software development.


The Scrum Field Guide: Practical Advice for Your First Year (Agile Software Development Series)
The Scrum Field Guide: Practical Advice for Your First Year (Agile Software Development Series)
by Mitch Lacey
Edition: Paperback
Price: $40.75
39 used & new from $16.94

1 of 1 people found the following review helpful
5.0 out of 5 stars Improving Your Scrum Practices, September 13, 2012
Scrum offers minimal guidelines for agile project management. In this book, Mitch Lacey provides Scrum practitioners with material that should help them improve their Scrum practices. Each chapter starts with a story that put the topic in perspective. It is followed by a discussion on the conceptual aspects. At the end of the chapter, a "Keys to Success" part summarizes the important content of the chapter and a reference section provides pointer to additional knowledge. I have particularly appreciated the chapters about the sprint length determination, doing new development and maintenance at the same time or the sprint emergency procedures. The book is easy to read and I will recommend this book to every Agile practitioner and every non-Agile practitioner too ;O)


Practical Unit Testing with TestNG and Mockito
Practical Unit Testing with TestNG and Mockito
by Tomek Kaczanowski
Edition: Paperback
Price: $35.00
9 used & new from $30.99

7 of 7 people found the following review helpful
4.0 out of 5 stars Good introduction to unit testing, not only for Java programmers, May 21, 2012
According to the author, this book is aimed at developers who want to produce high-quality, maintainable unit tests. It is intended especially for those who would like to start unit testing their code, but are unsure about how to get started and what to focus on. Despite the Java/TestNG/Mockito orientation that the title might suggest, the book contains a high percentage of general unit testing knowledge that can be applied (mostly) independently of the language and tools that you are using.

I liked the approach of the author to have an open view on unit testing and presenting all the available choices for testing strategies or tools selection instead of just pushing his own opinion. This book is highly recommendable to all software developers interested in unit testing, particularly if you are working in a Java context.


Management 3.0: Leading Agile Developers, Developing Agile Leaders (Addison-Wesley Signature Series (Cohn))
Management 3.0: Leading Agile Developers, Developing Agile Leaders (Addison-Wesley Signature Series (Cohn))
by Jurgen Appelo
Edition: Paperback
Price: $43.99
62 used & new from $31.36

0 of 1 people found the following review helpful
4.0 out of 5 stars All models are wrong but some are useful, August 5, 2011
In his foreword, Robert C. Martin wrote that he hates management book, but "this book is smart". I think that this book might be smart because Jurgen is smart. If I tried to summarize what you get from his book, you can consider Jurgen Appelo as the hidden son resulting from a relationship between a Springer Verlag journal's editor and Mike Cohn, with some influence from Aardman Studios in the education. You will therefore jump from sentences like "It is often seen as the opposite of reductionism, although complexity scientists believe that complexity is the bridge between the two, and both are necessary but insufficient [Corning 2002:69]" (I hope that you have all recognized the definition of "holism") to a checklist for a Agile Goals that contains questions like "is the goal manageable and measurable so that success can be determined?" You will therefore go back and forth between high level system or behavioral theories and practical management situations and practices. Despite its high theoretical content, the book is very enjoyable and easy to read and you shouldn't be afraid by what could appear initially as a strong theoretical content.

Jurgen Appelo is so smart that he even make the own assessment of his book at the end, based on the quote that "all models are wrong but some are useful" He says "It makes no sense discussing which idea is wrong, because they all are. The real challenge is in finding which ideas is useful in what context". I think that reading his book will provide you with a larger ideas' toolkit and help you assess which ideas might be useful in a particular context for your project management journey.


Managing Software Debt: Building for Inevitable Change (Agile Software Development Series)
Managing Software Debt: Building for Inevitable Change (Agile Software Development Series)
by Chris Sterling
Edition: Hardcover
23 used & new from $27.99

4.0 out of 5 stars This book provides meaningful insights on how to prevent creating too much debt, August 5, 2011
Technical debt has become a trendy term for an issue that exists since the beginning of software development projects. It is what happens when you neglect, consciously or not, the long-term quality of your software to achieve other usually short term benefits. After defining the concept of software debt, Chris Sterling explores the topic of managing software debt in all software development activities. Three chapters are dedicated to the topic of design and architecture, discussing how they should fit in Agile approaches.

As its title suggests, this book goes even further than the concept of technical debt as it try to cover all dimensions of software development debt. My favorite chapter comes at the end where the notion of experience debt is explored. I have witnessed many projects where the technical or product knowledge was concentrated on fewer and fewer people, due to change in project team composition, effectively making them the bottlenecks where all application evolutions had to be processed. We sometimes create more debt in the heads than in the code.

The book is well written and easy to read. Every chapter begins with a mindmap of the topic that will be explored, thus giving a big picture of its content. The material mixes high level definitions with practical examples and real life stories. A summary is proposed at the end of each chapter

At every stage of the software development life cycle, we make decisions that have long term consequences. This book provides meaningful insights on how to prevent creating too much debt and how to reduce the existing burden. I will recommend it to everybody who is concerned with software quality with a longer view than the end of the next iteration.


Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (Agile Software Development Series)
Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise (Agile Software Development Series)
by Dean Leffingwell
Edition: Hardcover
Price: $45.71
91 used & new from $23.65

14 of 15 people found the following review helpful
4.0 out of 5 stars A detailed and extensive study of the agile gathering and management of requirements in enterprises, August 5, 2011
Although many might tend to limit the concept of agile requirements to "user stories", this book reminds us that there could be more than just a post-it on an information radiator when we talk about requirements. The title of one of the initial chapters is "The Big Picture of Agile Requirements" and this book provides it, together with the small details that can help you write better stories.

Dean Leffingwell describes the general context of managing requirements in organizations based on a three levels view: portfolio, program and team. The concept of requirements is different at each of these levels: from the investment themes and epics of the enterprise strategy to the user stories implemented by teams during Scrum sprints. An interesting concept developed in the book is the Agile Release Train (ART) that aggregates user stories in features set. The goal is to adjust the team's capacity to produce software with the ability of customers to absorb it.

The book is very well written, achieving balance between a structured approach and easiness to read. It contains many case studies, templates and sample agenda that help relate the ideas expressed with the daily activities. Three appendixes at the end propose interviews and document templates, along with a release-planning checklist.

This book provides a detailed and extensive study of the agile gathering and management of requirements in enterprises and I will recommend it to everybody involved in some software requirement activity, from the business analyst to the project manager or developer.


Page: 1 | 2 | 3 | 4