InfoQ Homepage Culture & Methods Content on InfoQ
-
Stephen Walther on Integrating JavaScript Unit Tests
Automated testing frameworks need both a good test library and a good integration story. While most JavaScript testing frameworks have been focusing on the former, Stephen Walther has been working on a solution to the integration problem.
-
Characteristics of an Agile Organization
Jim Collins, in his famous book “Good to Great” talks about his teams five year research where they determined what it takes to change a good company into a great one. Can Agile help in the creation of great companies?
-
Should You Assign Story Points To Bugs?
When migrating an existing project to Scrum, one often faces a backlog of unfixed bugs from the pre-Scrum era. Is it effective to assign story points to these bugs and prioritize some along with the user stories in each sprint?
-
Comparing Apple, Google and Microsoft
A Gartner webinar (PDF) compares three major players in the software industry today - Apple, Google and Microsoft –, trying to see where they stand today, and how IT decisions will be affected by their competition with each other. TheOpenSourcery compared the same companies from a different perspective: agility and openness.
-
Hudson Project Proposes Renaming to Jenkins
With Oracle having applied for the trademark on the Hudson project name, and potentially putting the future of the Hudson project in future jeopardy, the Hudson developers have proposed renaming the project to Jenkins. The developers are keen to emphasise that this is a rename, not a fork, of the project since the same developers will continue to work on the renamed project.
-
Bob Muglia Leaves Microsoft
Bob Muglia, a Microsoft veteran and president, has decided to leave Microsoft after Steve Ballmer’s decision to change him from leading the STB division.
-
Swarming: What's the Point?
Agile teams are encouraged to focus all their effort, as much as possible, on one story at a time--a practice known as "swarming." But why do this? What are the benefits you can expect to see by swarming each story?
-
Hearing From Real Customers at Agile 2011
The Working with Customers stage at Agile 2011 is looking for stories and submissions from customers of agile teams. The stage explores the interactions between the customer community and Agile development teams, focusing on the non-technology functions as well as the Agile development teams themselves. In this item the stage producers answer questions and appeal to real world customers.
-
Scrum Project Estimation Beyond the Near-Term?
How can you estimate the effort required for an entire Scrum project when Scrum only recommends doing task breakdowns for the next one or two sprints? Should we even try to estimate project effort in the mid- to long-term?
-
Entity Framework Code-First CTP5
Earlier this month the ADO.NET team released CTP5 of their Entity Framework Code-First library. The library is meant to provide a code-centric workflow for developers when working with data.
-
NIST Cloud Computing Twiki Launched
Today NIST began sending users their credentials for their Cloud Computing twiki, of which Kevin Jackson was one of the first to be granted access. The intent of the NIST working group is to promote cloud computing adoption and overcome the current percieved barriers of security, interoperability and portability.
-
Getting the Customer Involved
Agile methods place a strong emphasis on customer feedback and interaction. Projects with involved customers have much higher chances of success than projects which lack customer interaction. So, how do Agile teams keep the customer involved.
-
How To Complete Stories Without Leaving Bugs Behind
What can you do when unacceptable numbers of stories are "done" with development, but they still have many quality problems?
-
Does Agile Limit Financial Rewards for an Individual?
Tom Reynolds mentioned an interesting comment, that he had heard about the reluctance of people to move to Scrum. The reason quoted was that Scrum would have a direct impact on their financial rewards as it places a lot of emphasis on teams and not the individual.
-
Should We Move a Failed Story Back?
What should we do with a story on our task board when it fails testing?