BT

Improving Process with Two Definitions of Done

by Savita Pahuja on  Mar 11, 2014 2

Separate ideal and current versions of Definition of Done can be used in agile teams. The purpose is to expand Definition of Done to grow in maturity and quality. This can be implemented on physical boards as well as on other electronic Agile Tools like Jira.

Attitudes for Sustainable Lean Startup Teams

by Ben Linders on  Mar 11, 2014

Ramli John gave an ignite talk about the minimum viable attitudes for lean startup teams at the 2013 lean startup conference. According to Ramli there are three attitudes that help teams to run lean sustainable over time: humbleness, hunger and happiness.

ThoughtWorks Open Sources Go, a CD Tool

by Abel Avram on  Mar 07, 2014 8

ThoughtWorks has recently open sourced their Continuous Delivery (CD) tool, called Go, having its origins in CruiseControl and providing a pipeline process that covers the entire code development process: continuous integration, testing and deploying.

Using Scrum of Scrums with Agile Teams to Coordinate and Collaborate

by Ben Linders on  Mar 06, 2014

Scrum of scrums can be used to scale the daily stand-up meeting when multiple teams are involved. Its purpose is to support agile teams in collaborating and coordinating their work with other teams. Several authors have shared views on scrum of scrums, with experiences of using them.

The Retr-O-Mat Retrospective Activity Generator: Now Available in Print

by Fabian Lange on  Mar 04, 2014

Random retrospective activity generator "Retr-O-Mat" now available as printed edition, contains 50 activities from various sources.

Mike Cohn Suggests Unfinished Work in Sprint Review

by Rui Miguel Ferreira on  Mar 04, 2014

Mike Cohn explains why sometimes it is worth to present unfinished product backlog items during the sprint review meeting.

Finding the Best-fit for Lean Startup Methodology

by Rafiq Gemmail on  Feb 28, 2014

Raf Gemmail surveys recent commentary and presentations on the successes and failures of lean-startup methodology within both startups and big enterprise.

Having Actions Done from Retrospectives

by Ben Linders on  Feb 27, 2014

Agile retrospectives help teams to find and do actions to improve continuously. There are different ways to do follow up on the actions and to evaluate if actions are leading to better team performance and more value delivered to customers.

Scaling The Happiness Index

by Savita Pahuja on  Feb 27, 2014 1

A report on how happiness index could be scaled out from team level to organization level. Frank Schlesinger, Corinna Baldauf and Stowe Boyd shared their experiences of scaling the happiness index and tools for implementation.

Q&A with VersionOne CEO Robert Holler – Agile Live Webinars

by Shane Hastie on  Feb 26, 2014

InfoQ spoke to VersionOne CEO Robert Holler about their Agile Live Webinar series

Agile 2014 Keynote Speakers Announced

by Shane Hastie on  Feb 24, 2014

The Agile Alliance has announced keynote speakers who will present at the Agile 2014 conference in Orlando, FL, USA. They are Aneesh Chopra, former and first U.S. Chief Technology Officer, Diana Larsen, author, consultant and an authority on agile adoption, and Bjarte Bogsnes a leader in the Beyond Budgeting community

How Team Members Learn From Each Other in Agile Teams

by Ben Linders on  Feb 20, 2014

When adopting agile teams can use (external) coaches and mentors. But teams can also develop themselves by having team members mentoring and coaching each other. Team members can learn skills and abilities from other team members in multidisciplinary teams, enabling the team to grow as a whole and become self-organized.

Interview with VersionOne CEO Robert Holler on the State of Agile Survey Results

by Shane Hastie on  Feb 19, 2014

InfoQ spoke to VersionOne CEO Robert Holler about the 8th State of Agile survey results which were recently released.

Interview with VersionOne CEO Robert Holler on the Winter Product Release

by Shane Hastie on  Feb 13, 2014

InfoQ spoke to VersionOne CEO Robert Holler about the features of the Winter 2014 release and their strategic investment themes.

Applying Use Cases in Agile: Use Case 2.0, Slicing and Laminating

by Ben Linders on  Feb 13, 2014 1

To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2013 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT