InfoQ Homepage Agile Content on InfoQ
-
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?
-
Temporary Code, Sustainable Code and Everything in Between
There is code which is well tested, well re-factored and built to last. There is also code which is planned to be thrown away in a few days. Between these two extremes, there is a lot of gray area. The code in this gray area is written with the presumption that it would be cleaned up later but is never done.
-
2010 US Scrum Gathering, The After-Shocks
The 2010 US Scrum Gathering went down 2 weeks ago in Orlando, and InfoQ has followed the buzz since. Enjoy what we've found from the vast pool of great blogs, articles, notes, videos, pictures, presentations and more that have surfaced since the event.
-
Agile Documentation: Is There Clarity?
Agile documentation is not exactly the most clear cut subject in the community? How much documentation should we create? What works? What doesn't? How do we transform from a traditional process to an agile one with regards to documents? This is an area that lacks clarity in the agile community.
-
A Manifesto of Done
Alixx Skevington posted a Manifesto of Done as the beginning of a discussion thread, talking about the commitments team members make to each other about the quality of their work and clearly expressing their commitment to delivering business value through their code. Covering areas such as coding standards, usable code, unit testing and test coverage he emphasises the importance of quality work.
-
WebSockets and Bayeux/CometD
There are two technologies which bring communication into browser-based applications at the moment; Bayeux (aka CometD) and more recently, WebSockets. Will one supersede the other, or are there sufficient differences for both to thrive?
-
An Alternative to Certifications
The Agile Skills project is a resource for establishing a baseline of skills that an Agile Developer needs. It provides an evolving repository and a place to start learning about these skills.
-
Conflict is Human: Let's Use It Well
Lyssa Adkins, author of Coaching Agile Teams maintains that not only does "resolving" conflict not work - it can even be counter-productive. Can conflict actually catapult teams to higher performance? In her ADP2009 keynote, she presented a model for helping teams learn to de-escalate from destructive into constructive forms of conflict.
-
InfoQ User Survey Results
Back in January, InfoQ published a User Survey and asked for people to take a few minutes and fill it out. Our reasoning for doing so was pretty straightforward - we wanted to know how we could improve the InfoQ experience for you, the user. We were pleasantly surprised that within a few days of posting the survey we had received several thousand replies - these are the results of that survey.
-
Harmonizing Agile With "User-Centered Design"
UX specialist Anthony Colfelt presents a case for how agile, alone, might not be sufficient and a thorough and engaging look into how User-Centered Design can, and should, be merged with it.
-
Most Effective Team Structure
Agile talks about small team sizes with the magic numbers of 7 plus minus 2. Agile also recommends whole teams. Whole team is a concept that advises for having sufficient skills within the team itself to get the job done. Thus the development team has the testing skills, database skills, user interface skills, apart from the core development skills. Is defining the team structure this easy?
-
Is the Agile Community Being Unreasonable?
A recent thread on the pmi-agile Yahoo! group discusses some frustrations of the Agile recommendations that seem on the verge of naivete.