InfoQ Homepage Agile Content on InfoQ
-
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.
-
QCon Live: What's Happening at QCon London This Week?
This week, the fourth annual QCon London is in progress. Starting on March 8th with tutorials and ending on March 12th with a "meet the speakers" social, there will be a lot happening. This article describes the many ways that readers can follow along with the events at QCon as they are happening.
-
What is Story Point? Are they Necessary?
Michael de la Maza asks the question what exactly is a Story Point? He went looking for an answer and found many: “Story points represent nebulous units of time.” or “Story point is a random measure used by Scrum teams. This is used to measure the effort required to implement a story.”
-
The Open UP Debate
Following on from the discussion of the various flavours of Unified Process, there is some debate about the OpenUP process framework - is it Agile, or a reactionary result of the move to lighter processes?
-
Uncovering Serious Flaws of Agile and Scrum
Software development is known to be a creative process. The failure of traditional methods, where the dynamic environment of software development was ignored, made Agile methods fairly popular. There has been a growing adoption of Agile methodologies, particularly Scrum. However, is everything all right with Agile? Kai Gilb does not think so. He suggested that there are serious flaws with Agile.
-
Rules for Better Retrospectives
James Carr recently published a list of five rules to help improve the effectiveness of retrospectives. The rules are based on his experiences in hundreds of retrospectives, both successful and not.
-
Experiment Driven Development - The Post-Agile Way
TDD and BDD are now widely-used software development techniques. However, solely following TDD & BDD may still lead to missed business opportunities, or worse, a negative impact to the business. Two questions which TDD & BDD are unable to answer are: How do you measure the usage of your application? How do you get feedback from your customers? Is Experiment-Driven Development (EDD) the answer?
-
Agile Team Spaces: Do's and Don'ts
Many of us, who are new to Agile, would believe that putting an Agile team together in a room gets the job done. A few of us would actually pay attention to what makes a room a team room which can enhance productivity and motivation. Many Agile teams have already shared their perspective on what would make an ideal team room. Here are a few recent ones.
-
A Critique of the Pomodoro Technique
Is the pomodoro technique really all it's cracked up to be? Are we over-analyzing the issue and creating complexity where none is needed? Mario Fusco shared his critique of the pomodoro technique with InfoQ and we are sharing it with our readers along with many others.
-
The Various Flavors of Unified Process
The Rational Unified Process(RUP) was developed through the 1990's as a framework for software engineering best practices. Features such as iterations, simplicity, focus on value and regular feedback were identified as being important for Asuccessful software engineering. A number of authors have built methodologies that adapt UP to different project domains. This article examines some of them.
-
Deciphering Burndown Charts
Burndown charts are considered to be one of the most useful information radiators on an Agile team. It is a graphical representation of amount of work left to do (y-axis) versus time (x-axis). The interesting part is that the analysis of the burndown chart can reveal multiple pointers on how the team is doing and what can they do to improve further.
-
QCon London in One Month: 103 Speakers, 107 Sessions, 500+ Attendees
QCon London is in 1 month! The final schedule is now online and features 103 speakers and 107 sessions on key topics designed for senior developers, team leads, architects in enterprise software development shops. The last chance to save £196 expires in 2 weeks.