Top stories for agile

Buzz | Video | Top stories | My News


added 2009 Wed Mar 25 16:53:19 by mswatcher
In the ten years I???ve been programming I???ve learned two pretty important things. 1. Project success is about people and teams. No matter your process, good teams will succeed (usually in spite of your process) and bad teams will fail. 2. Every time you make a rule about something, people will stop thinking about that thing and blindly apply the rule.
added 2009 Wed Mar 25 13:13:10 by handersongomes
There is a lot of talk these days about 100% test coverage and if we should strive to reach it. I honestly think that 100% test coverage is a hot topic because it can be easily measured with tools like Cobertura and Clover. The most important question is how much test coverage is enough.
added 2009 Tue Mar 24 7:30:59 by firefalcon
Is there any relations between simple rules and software development? Sure there are. Software development process should be simple. Process complexity lead to mechanistic and dumb behavior.
added 2009 Tue Mar 24 2:49:10 by Mark Levison
Recommended Readings from the Editors at InfoQ
added 2009 Sun Mar 22 18:05:25 by kadlet51
Javascript testing does not scale well, so to solve the problem, John Resig is unveiling TestSwarm. It's a JavaScript client that continually pings a central server looking for more tests to run
added 2009 Sat Mar 21 22:48:53 by fjdzone
Getting a good continuous integration process in place poses many challenges. One of the biggest is making sure you have the discipline to support it.
added 2009 Fri Mar 20 10:51:03 by WeiLing
About 10 years ago I recall studying profusely so that I might pass my Java programmer's certification exam. I purchased a copy of an exam cram book that had sample questions similar to what I might encounter on my certification test. I recall dealing with questions like the following: * Can an abstract class be subclassed? * What interface does TreeMap implement? * What is the output of the following code snippet? * Identify the compile errors in the following code snippet. * What are the different access qualifiers?
added 2009 Fri Mar 20 2:58:32 by AlvinAshcraft
For a long time, I???ve said that my biggest job on the CodePlex team is to learn agile. Now I find myself saying ???if only I could go back in time, here???s what I would tell myself about agile:??
added 2009 Fri Mar 20 0:33:48 by firefalcon
Is it a good thing to have "Zero Defects" goal in the sprint? The answer is "Are you kidding me? Zero bugs? It's a miracle!"

Sponsors

 
added 2009 Wed Mar 18 11:04:27 by rivethead_
More and more people are working in teams where Continuous Integration is used. Not everyone truly ???gets??? it though?? Below is a quick list of things you, as a member of the team, need to keep in mind.
added 2009 Wed Mar 18 9:55:54 by peterstev
Scrum is simple and Scrum is hard. The Daily Scrum is simple daily routine to help the team self-organize, focus, and identify and eliminate impediments to progress. How do you conduct the Daily Scrum and how do you know if the Daily Scrum is achieving its purpose?
added 2009 Wed Mar 18 3:17:23 by cyberhitesh
In this we will understand the Use Case Diagrams used in UML, Use Case Diagrams describes the interaction of the user with the systems. There are two main components of Use Case Diagrams, ???Actors?? and ???Use Cases???.
added 2009 Tue Mar 17 23:35:30 by sergio.fierens
Why the new merging capabilities in subversion 1.5 are so important
added 2009 Tue Mar 17 22:50:06 by dgageot
Some people started attacks against a few TDD proponents, namely Kent Beck and Bob Martin. This is not the first time and it won???t be the last time. What these bloggers don???t get is that TDD is too good of a tool.
added 2009 Mon Mar 16 23:32:16 by robertdempsey
We???re very excited to announce the launch of scrum???d. Scrum???d provides simple project management for agile teams, allowing you to focus on results, rather than the process of achieving them. Scrum???d stays out of your way as you work, while providing complete transparency to everyone involved in the project. Inline editing, heavy use of drag-and-drop, and an inline help system are just a few of the things that make using scrum???d a breeze. Try scrum???d free for 30 days and get hooked.
added 2009 Mon Mar 16 18:45:06 by Matt Stine
So as I'm sitting here thumbing through my InfoQ feed on Google Reader, I come across the following posting: Software Craftsmanship Manifesto: A Call to Arms. It seems that a group of "programming patriots" has struck again (see the Manifesto for Agile Software Development - circa 2001), complete with a "founding document" look and feel.
added 2009 Mon Mar 16 13:14:40 by NBharti78
A core tenet of agile methodologies is to help teams deliver software more quickly. But with the plethora of agile practices available to choose from, teams new to agile struggle to find the right practices that help them realize speedier delivery. In coordination with the just published Agile refcard, DZone had the opportunity to chat with Amr Elssamadisy, Partner at Gemba Systems and author of "Agile Adoption Patterns: A Roadmap to Organizational Success", about agile and the promise of speedier delivery.
added 2009 Fri Mar 13 19:37:04 by iraza
Test Driven Development is the modern agile development technique that follow write test first approach. This software development approach in reducing developer debugging time and improving the code quality
added 2009 Fri Mar 13 5:13:05 by MCII
The agile movement has been nothing if not evangelical, even messianic, since its inception. From its founding with the publication of a manifesto (a manifesto!) to its subsequent, continual attack on the so-called waterfall model, agile and its exponents have hewn closely to the position that theirs is the one true path. And, consistent with this evangelical view, those who disagree either don???t really understand agile or are irretrievably deluded. For the deluded, only spectacular failure of their project will open their eyes.
added 2009 Wed Mar 11 23:39:17 by tietyt
This article explains mock objects, the difference between them and fake objects, why I migrated from fake objects to mock objects, and then some reviews of some java mocking frameworks.
added 2009 Wed Mar 11 15:18:32 by alruiz15
In this article I will explore two of the most widely accepted agile development practices, Test Driven Development and Continuous Integration, and question how these practices can be made better. I will examine their strengths, shortcomings, and how the ideas behind continuous testing can provide better and faster feedback on the health of a code base.
added 2009 Wed Mar 11 9:43:23 by peterstev
Last week I gave an introductory talk about Scrum to a group of people in Z?rich. One participant asked if it would be OK to make the Daily Scrum a Weekly Scrum? My answer: No way! Here's why...
added 2009 Tue Mar 10 17:14:28 by lucas.teixeira
Hello! Good news for today!! I just got @ work and saw in my twitter that Graeme Rocher just updated Grails with the new Version 1.1. Take a look in its Release notes and my comments!
added 2009 Tue Mar 10 12:39:59 by bloid
This is the final post in my series about a client???s consternation with regard to Agile Process Overhead. This last topic had to do with their Sprint Planning Meeting and how to make commitments. The problem? ???Jean, how do we plan for unplanned work??? In this case, the team was referring to production issues that would come up that HAD to be addressed, even though they could not be predicted during the Sprint/Iteration Planning Meeting.
added 2009 Tue Mar 10 3:03:38 by firefalcon
Here are three common bug management anti-patterns in a development process.
added 2009 Mon Mar 9 23:07:48 by mkoryak
A quick demonstration of differences between tellurium and selenium tests with code examples.
added 2009 Mon Mar 9 6:03:02 by A. Cetin CAVDAR
Continuous Integration (CI) is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.
added 2009 Sat Mar 7 19:51:04 by gerps
Neil Martin shows us which technologies are a must have when starting a new .NET project. Featured projects: db4o, Nant (Ant for .NET), NBehave (for testing), MOQ (for mocking) and Unfuddle (a service for Git and Subversion hosting).
added 2009 Sat Mar 7 9:58:33 by sutts
Code is like traveling: the less baggage the better. No bags is bliss, a little backpack hardly noticeable. Chunky wheelie bag: bearable but irksome. But several chunky wheelie bags, and it starts to get ?? logistically challenging. Not to mention increased risk of hernia.
added 2009 Sat Mar 7 0:25:17 by jamonc
So what would I think are the most important principles for building a Framework? Here are my current ones, in no specific order. I plan on gathering a collection of these on my pages, but for now here are a few to go on.


12345678910111213 ... 15 »