InfoQ Homepage Scrum Content on InfoQ
-
Is it Time to Stop Estimating User Stories?
Most new Agile teams transition from hours based estimates to relative estimation using story points, but do we even need estimates at all?
-
The Future of UI/UX in Agile
Many people who are new to Agile are confused about the place of UI and UX design on Agile teams. Previously many teams have tried keeping the work separate from the team or having the work done one sprint ahead. Recently, there has been more talk about welcoming UI and UX into Agile teams and Lean UX has been at the forefront.
-
How Rigid is Scrum?
Scrum is seen as an adaptive and flexible software development methodology which aims to improve the development process. Over the years, there have been many success stories which have been attributed to Scrum. However, some teams continue to smell a good amount of inflexibility and rigidity. Is it Scrum at fault or is it a flawed adoption process?
-
Scrum Alliance Strengthens CSP Certification, Announces Beta
The Scrum Alliance announced plans to strengthen the Certified Scrum Professional (CSP) designation into "a certification program that meets worldwide standards for structure and testing required for accreditation." The CSP designation, goes beyond the CSM as it requires experience applying agile in the workplace. Details for a beta program will be in the next Scrum Alliance Newsletter.
-
Do We Need an Iteration Zero?
There are usually multiple things which need to be done before the start of a project. Teams usually use 'Iteration Zero' to put all necessary systems in place in order to start delivering business value in subsequent iterations. Is this the right way?
-
When to Cease Being an Agile Coach?
Agile coach Morgan Ahlström recently turned to the Agile Coach Support mailing list to ask how to deal with an organization that said they wanted the benefits of becoming more agile, but was behaving in ways contrary to that goal.
-
Possible Solutions to the Single Product Owner Problem
A Product Owner arguably, is one of the most demanding roles in Scrum. Product Owner is, single handedly responsible for the success of the project and is expected to lead the development effort by conveying the vision to the team. He is expected to help the team produce maximum business value. Is this expecting a lot from a single role?
-
The Importance of Agile Feedback Loops
Several members of the Agile community emphasize the importance of feedback loops in the effectiveness of Agile development processes.
-
What Constitutes A High-Quality Agile Transition?
In a number of blog postings, members of the Agile community offer their perspectives on what constitutes a high-quality transition to Agile methods within an organization
-
Time-Tracking For Scrum Cost Control
Should you track the time of individual Scrum tasks for cost-control purposes?
-
Are Social Networks, Agile and Cloud Changing Offshore Software Development?
In his famous book “The world is flat”, Thomas L. Friedman talks about the convergence of events which led to many countries becoming a part of the global supply chain. This resulted in definition of new rules of economics. Israel Gat takes the concept further to suggest that software development has ceased to be location dependent, thanks to Social networking and collaborative techniques.
-
Taking a Break From Sprinting
Over the long term, can teams sustain constant work on the product backlog? If a break is needed, what's the most effective way of doing it?
-
Should the Product Owner Also Be the ScrumMaster?
What are the advantages and disadvantages of having the same person fill both the Product Owner and the ScrumMaster role on the same Scrum project? Is this really a workable option?
-
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?
-
Agile/Scrum Retrospectives–Tips and Tricks
Retrospectives and feedback loops are at the heart of any successful Agile/Scrum implementation. They’re the tool we use to help teams improve. Yet in two day introduction to Agile classes they often get glossed over. Lacking time trainers (including this one) often race through the topic outlining only one simple type of retrospectives.