InfoQ Homepage Culture & Methods Content on InfoQ
-
Using Scrum of Scrums with Agile Teams to Coordinate and Collaborate
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
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
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
Raf Gemmail surveys recent commentary and presentations on the successes and failures of lean-startup methodology within both startups and big enterprise.
-
Lessons Learned from Apple's GoToFail Bug
The recent security weakness found in both iOS and OS X hints at flaws in coding style guidelines, unit testing, system testing, code review policies, error management strategies, and tools deployment. An overview.
-
Having Actions Done from Retrospectives
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
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
InfoQ spoke to VersionOne CEO Robert Holler about their Agile Live Webinar series
-
Agile 2014 Keynote Speakers Announced
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
-
QCon London in 2 weeks – Seven Key Reasons to Attend
Going into its 8th year, QCon London is UK’s premier event designed exclusively for senior enterprise software development professionals: technical team leads, architects, software engineers, and project managers. If you've thought of attending, there is still a chance to go to one of the best conferences for our craft. QCon is now less than 2 weeks away! Why register? Seven Key Reasons to Attend.
-
How Team Members Learn From Each Other in Agile Teams
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
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
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
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.
-
Balancing Experiments and Deliveries in Product Development
Experimentation using for instance lean startup can help you learn about your customers and find out which features and product would be valuable. The value however comes from building products and actually delivering them to customers. You need to find ways to balance between experimentation and delivery.