InfoQ Homepage Agile Content on InfoQ
-
Organizing Self-organizing Teams
Rashina Hoda is a PhD researcher who has been examining how self-organization actually happens on teams. She has studied teams in New Zealand and India and identified six distinct roles that emerge when teams effectively self-organize. She spoke to InfoQ about her research, which will be published at the International Conference on Software Engineering (ICSE2010) to be held in Cape Town in May.
-
SEMAT - Software Engineering Method and Theory
SEMAT was founded in November 2009 with the bold claim that the software industry has too many fads and immature practices. The signatories promised to refound software engineering and bring it into the modern age.
-
Visual Risk Management
Irrespective of the size of the project, stakeholders feel confident when they can a keep track of the risks and their mitigation strategies. Agile heavily promotes the use of information radiators. Keeping in line with the philosophy of radiators, Agilists suggested different ways of depicting risks visually for easy tracking and mitigation.
-
The Emerging Dynamics of Certification
Scrum and agile certification is now very much in focus. The 'certification story' is unfolding to become a major subject of debate in 2010. The story has several facets, with action from the Scrum Alliance, Scrum.org and the community-at-large, including notable bloggers and the Agile Skills Project. At issue is the basic value of certification.
-
InfoQ Feature Set: What Do You Want To See?
What’s next for InfoQ? What are some of the areas we should be focusing on feature wise? We'd like to ask you where you’d like the site to go from a feature-set perspective. InfoQ is still lagging behind many of the world-class media sites out there. We may not be the New York Times, but with your help we'll have the will and the way to get there!
-
Jim Shore Suggests Automated Acceptance Tests Are Not The Right Move
Much of the generally accepted agile literature will advise you that the best way to capture your user's needs is through examples encoded into automated tests - "automated acceptance tests". Thought-leader Jim Shore says maybe not, while others still challenge him.
-
Is the 'C' Word Dividing the Agile Community?
There has been a lot that has been said about Scrum Certifications. Some people like the idea and others oppose it vehemently. Ron Jeffries recently stated that though he has been writing about the good aspects of Scrum Alliance’s Certifications but he is concerned that the 'C' word is keeping away a lot of valuable members of the Agile community.
-
Twist 2.0 Supports Behavior Driven and Collaborative Testing
ThoughtWorks Studios recently released the latest version and second major revision of Twist, its Agile test automation product. Twist 2.0 helps testers, developers and business analysts with collaborative testing. It also supports writing tests scripts using Groovy dynamic language.
-
Toyota Using Waterfall?
Lean software development has been inspired by lean manufacturing and specifically the work that Toyota pioneered in the field. It is then very surprising to find out that the software development arm of Toyota has been working with waterfall and is in it's infancy in lean software development.
-
Repetitive Tasks an Agile Smell?
Is slicing stories in horizontal tasks an Agile Smell? Is this common habit used in Scrum/Agile Planning meetings - hurting a team's focus on customer value? What is being suggested instead?
-
Making Change Stick
Making cultural change in an organisation is hard, and fraught with risk. Adopting Agile principles is a major cultural shift for many organisations. Management consultant and author Steve Denning has been researching what makes change stick, and provides some concrete advice for change agents.
-
Agile in the Mainstream
Mainstream Agile is an idea whose time appears to have arrived. Larger consulting services firms are now touting "agility", with firms like IBM Global Business Services and Cap Gemini pitching Agile-related service offerings. Given this kind of sudden mainstream popularity, what does it mean for Agile in general? What does "mainstream" Agile look like? What's in mainstream Agile?
-
Monetizing the Technical Debt
Most Agile teams recognize the evils associated with technical debt. Just like a financial debt, the technical debt incurs interest payments. These are paid in the form of extra effort required to maintain and enhance the software. Most Agilists recommend repaying the technical debt as early as possible. However, most Agile teams fail to monetize the technical debt.
-
Scrum Gathering: Community of Practice
The Agile community is developing consensus around three important areas of practice: requirements gathering, agile coaching, and open space formats for group learning. At the recent Scrum Gathering, these topics were prominent topics of discussion on Day 1, Day 2, and Day 3 of the event. InfoQ explored each of these further to gain a better understanding of their place in Agile.
-
A New Addition to the InfoQ Family: The Operations Community
A 7th community has now joined the current 6 on InfoQ. When one looks at our existing queues, one sees a definitive pattern - we currently focus upon application development and architecture (.NET, Ruby, Java, SOA, Architecture) and also Agile techniques, primarily in the context of application development. However, what happens to that software once it's been developed?