InfoQ Homepage Agile Content on InfoQ
-
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.
-
US Scrum Gathering, An All-Open Space Final Day
The 2010 US Scrum Gathering in Orlando wraps up after an all-Open Space Day 3, exemplifying the collaborative and empirical essence of Scrum as its originally intended.
-
US Scrum Gathering, An Exciting Day Two
Day two of the 2010 Scrum Gathering, packed full of a whirlwind of topics, talkers, activities, useful nuggets, and again (of course) healthy debates. Highlights including Harrison Owens, the creator of Open Space (as we know it), Jeff Patton's User Story Mapping, Jurgen Appello on self-organization and much, much more.
-
The “Do Not Disturb” Team Member
Many developers like to work in isolation, for some time, if not always. XP recommends a room arrangement called “Caves and Commons”. Commons area is organized to maximise osmotic communication. Caves are meant to facilitate isolation for activities like personal email, phone calls or a quick spike. However, there could be a situations where a team member wants to take this isolation too far.
-
US Scrum Gathering 2010 Kicks Off With a Day of "Deep Dives"
The 2010 US Scrum Gathering kicked off Monday in Orlando with a buzzworthy day of "deep dive" learning, collaboration, and healthy debate.