InfoQ Homepage Team Collaboration Content on InfoQ

Articles

RSS Feed

Newer Older

Culture & Methods

My Experience as a QA in Scrum

The QA role in Scrum is much more than just writing test cases and reporting bugs. In this article, Priyanka Hasija shares her experiences and the valuable lessons learned over the past 2 years while serving as a QA analyst on a Scrum team. She explains how QAs not only perform agile tests but also fill many other roles and responsibilities, earning them a place of importance on the team.

Priyanka Hasija
on Jul 17, 2012
Interview with Simon Baker, Author of No Bull

InfoQ has interviewed Simon Baker, cofounder of Energized Work and the 2009 recipient of the Agile Alliance Gordon Pask Award, author of the "No bull" publication on the past 12 years of Agile.

Marta Jasinska
on May 28, 2012
Agile Adoption – Vital Behaviours and Influence Strategies

Steve is interested in uncovering better ways to deliver successful projects regardless of whether or not those ways are ‘agile’. After reading "Influencer, the Power to Change Anything" he found a set of behaviours and influence strategies that are helpful for giving projects the best chance for success and also for helping teams transition to agile.

Steve Rogalsky
on Dec 01, 2011
Laurent Bossavit: Agile Ten Years On

Laurent Bossavit discusses the importance of learning from history and reflects on the historical influences that have contributed to emergence of agile practices and techniques. He examines the impact agile approaches are having and the emergence of the new discipline of agile software development, and calls for formulation of a new generation of more inclusive Agile institutions.

Shane Hastie
on Jul 28, 2011
Git, Gerrit Review and Jenkins or Hudson CI Servers

Together, Gerrit and Jenkins/Hudson allow you to propose changes and have those proposals automatically compiled/tested/verified before a human review even starts. This article shows how to install and configure Gerrit and how to hook it up to Jenkins/Hudson to build all proposed changes.

Alex Blewitt
on Jun 10, 2011
Interview: William E. Perry - Author iTeams – Putting the “I” Back Into Team

In his book, iTeams – Putting the “I” Back Into Team, author William E. Perry demolishes the cliché - "There is no ‘I’ in team." As Perry explains, the phrase is nonsense because it is the individual differences in team members that make teams great. In this interview, Ben Linders explores with the author the motivations for writing the book as well as some of the key thoughts.

Ben Linders
on May 23, 2011
The Art of Creating Whole Teams: how agile has changed the way we work with our customers

Angela Martin earned her PhD examining how agile methods work in practice and what is different about this way of working. She shares some of the key practices which organisations can implement to increase their likelihood of successful cultural change through creating Whole Teams - truly cross functional collaborative teams working well together to deliver products which meet customer's needs

Angela Martin
on Mar 15, 2011
Breaking Down Walls, Building Bridges, and Takin’ Out the Trash

Agile Team Rooms can help double the productivity of an Agile Team. Most people are familiar with the Caves and Commons approach where the team has a common area on the inside of the room and private desks on the outside. Some teams dispense with the private spaces in the room, but few go as far as Menlo dispensing with the rooms altogether.

Richard Sheridan Lisamarie Babik
on Dec 22, 2010
Use of Kanban in the Operations Team at Spotify

In this article, InfoQ spoke with Mattias Jansson, Operations Engineer at Spotify (an online music streaming service) about the adoption of Kanban by the Spotify Operations team. Jansson offered a lot of detail about the choice to adopt Kanban as well as the experiences that the Operations team at Spotify has gained while implementing a Kanban-based approach to dealing with their workload.

Michael Prokop Mattias Jansson
on Sep 14, 2010
Skills for Scrum Agile Teams

The skills required to be hyper-productive in agile projects are different from those required by a traditional one. This article identifies behavioral and technical skills required for a team to have that edge. Anyone who acquires these "delta" traits should be equipped with the right set of behavioral and technical skills, which enable them to work effectively in an agile project.

Prasad Prabhakaran
on Jul 26, 2010
Fred Brooks on The Design of Design: Interview and Excerpt

A review of Frederick P. Brooks' latest book, The Design of Design. Few individuals have had as much influence on the 'practice' of software development and this book of loosely coupled essays on the essence of design, design process, and the development and nurturing of great designers extends and enhances previous contributions to the field. The review is enhanced with an interview and excerpt.

Dave West
on Jun 30, 2010
Agile Teamwork: The Leadership - Self-management Dilemma

Self-managed teams are unstable and are successful when the ‘Leadership – Self-Management’ dilemma is understood and dealt with. Too much central control destroys agility, inhibits creativity and resists change. Too much self-management leads to chaos and anarchy and destroys a team. A successful Agile Team operates as far along self-management as it can, without tipping over into chaos.

Rowan McCann
on Jan 05, 2010

Newer Articles

Older Articles

InfoQ Software Architects' Newsletter

Articles