Book: More Agile Testing: Learning Journeys for the Whole Team

Book Cover: Book: More Agile Testing: Learning Journeys for the Whole Team

Packed with new examples from real teams, this insightful guide offers detailed information about adapting agile testing for your environment; learning from experience and continually improving your test processes; scaling agile testing across teams; and overcoming the pitfalls of automated testing. You’ll find brand-new coverage of agile testing for the enterprise, distributed teams, mobile/embedded systems, regulated environments, data warehouse/BI systems, and DevOps practices.

You’ll come away understanding

• How to clarify testing activities within the teamW

• Ways to collaborate with business experts to identify valuable features and deliver the right capabilities

• How to design automated tests for superior reliability and easier maintenance

• How agile team members can improve and expand their testing skills

• How to plan “just enough,” balancing small increments with larger feature sets and the entire system

• How to use testing to identify and mitigate risks associated with your current agile processes and to prevent defects

• How to address challenges within your product or organizational context

• How to perform exploratory testing using “personas” and “tours”

• Exploratory testing approaches that engage the whole team, using test charters with session- and thread-based techniques

• How to bring new agile testers up to speed quickly–without overwhelming them

Published: October 16, 2014
Genres:
Tags:
Reviews:Ben Linders on Amazon wrote:

This book can help you to catch up with new developments in the area of agile testing, with topics like scaling agile, DevOps, testing the Internet of Things (IoT) and agile testing in regulated environments.

I like how Janet and Lisa talk about "thinking skills". Collaboration and communication are important success factors to make agile teams work so there is a clear need for learning both professional and social skills.

Recommended reading for testers and for developers who want to learn more about testing.


Disclaimer: I’m affiliated with many online book stores. If you visit any of these stores via my website to buy books or any other products then I will receive a commission.

About Ben Linders

I help organizations with effective software development and management practices. Active member of several networks on Agile, Lean and Quality, and a frequent speaker and writer.
Bookmark the permalink.

Book: iTeam: Putting the ‘I’ Back into Team

Book Cover: Book: iTeam: Putting the 'I' Back into Team

It will surprise few professionals working in software development today to read that teams and teamwork are critical ingredients of a global economy. Productivity, product development and release, and even a company's survival increasingly will depend on teams to solve business problems. What may come as a surprise -- and a wake-up call -- is that, in many businesses, teams are completely ineffective.

One reason, posits William E. Perry in iTeam: Putting the 'I' Back into Team, is that most organizations put too much emphasis on joint effort, removing responsibility, ownership, and reward from individuals appointed to teams. What typically results is dysfunctional, essentially leaderless, and lacking in motivation.

Perry's call to put the emphasis back on individual responsibility among collaborating teammates is an urgent one. Decisions now made by management will more and more frequently be made and implemented by teams, making it necessary for organizations to ensure that the creativity and innovative methods of individuals be retained on teams.

Through extensive team experience and interviews with hundreds of individuals who have spent thousands of hours in team meetings, Perry has identified the attributes of great teams and great teamwork. iTeam examines the ten biggest challenges standing between most teams and excellence and explores in depth the fifty best practices teams can employ to improve performance.

Concluding that world-class teams comprise individuals who do what is right for their organization, and do what is right the right way, iTeam presents a clear, practical argument for building teams that have at their core a strong, proven leader who encourages and motivates team members to fulfill their team responsibilities.

Topics include:
* Reengineering the Team Approach to Problem Solving
* The Top-Ten Challenges to Effective Teamwork
* Selecting a Team Leader Who Will Lead
* Defining Team Entrance and Exit Criteria
* Selecting Team Members for Specific Roles
* Building Trust Among Team Members
* Training Team Members to Accomplish Their Assignments
* Listening to the Voice of the Customer
* Breaking Down Silos
* Avoiding Groupthink
* Assuring That Team Efforts Are Successful
* Rewarding Individual Team Members
* Keeping Teamwork Competitive
* Emerging Team Practices
* and much more

Published: June 1, 2009
Genres:
Tags:

Disclaimer: I’m affiliated with many online book stores. If you visit any of these stores via my website to buy books or any other products then I will receive a commission.

About Ben Linders

I help organizations with effective software development and management practices. Active member of several networks on Agile, Lean and Quality, and a frequent speaker and writer.
Bookmark the permalink.

Book: Agile Software Development with Distributed Teams

Book Cover: Book: Agile Software Development with Distributed Teams

All software projects face the challenges of diverse distances -- temporal, geographical, cultural, lingual, political, historical, and more. Many forms of distance even affect developers in the same room. The goal of this book is to reconcile two mainstays of modern agility: the close collaboration agility relies on, and project teams distributed across different cities, countries, and continents.

In Agile Software Development with Distributed Teams, Jutta Eckstein asserts that, in fact, agile methods and the constant communication they require are uniquely capable of solving the challenges of distributed projects. Agility is responsiveness to change -- in other words, agile practitioners maintain flexibility to accommodate changing circumstances and results. Iterative development serves the learning curve that global project teams must scale.

This book is not about how to outsource and forget your problems. Rather, Eckstein details how to carefully select development partners and integrate efforts and processes to form a better product than any single contributor could deliver on his or her own. The author de-emphasizes templates and charts and favors topical discussion and exploration. Practitioners share experiences in their own words in short stories throughout the book. Eckstein trains readers to be change agents, to creatively apply the concepts in this book to form a customized distributed project plan for success.

Topics include:

Understanding Distributed Development
The Productivity Myth
Ensuring Conceptual Integrity
Trust and Mutual Respect
Iterations and Releases
Using Features to Steer the Development Effort
Team Velocity
Virtual Retrospectives
Dispersed Synchronization
Introducing Agility to Global Projects
and much more

Published: July 1, 2010
Genres:
Tags:

Disclaimer: I’m affiliated with many online book stores. If you visit any of these stores via my website to buy books or any other products then I will receive a commission.

About Ben Linders

I help organizations with effective software development and management practices. Active member of several networks on Agile, Lean and Quality, and a frequent speaker and writer.
Bookmark the permalink.
  • Ben Linders – Independent Consultant Agile, Lean, Quality, and Continuous Improvement

    Ben Linders
    Ik help organisaties om effectiever software te ontwikkelen. Neem contact op voor mijn diensten.

    I help organizations to effectively develop software. Contact me to hear about my services.