scrumexpert

Getting Software Testing Done in the Sprint

May 3, 2012 0

This is an on-going series of blog posts that want to answer the classical question: How is software testing done during Scrum sprints? In the first installments, Clemens Reijnen discusses the importance of having testing knowledge in the team and implementing a collaborative culture. He then presents regression testing, test automation, end-to-end testing, avoiding overlapping tests, product backlog item implementation sequence, risk and business driven tests, writing acceptance tests. Microsoft Visual Studio is used as an example of tools supporting software testing practices in Scrum sprints.

Focus and Feedback Importance

May 1, 2012 0

Martin von Weissenberg explains in his blog post that focus and rapid feedback not only improve software development projects but shorten them dramatically as well. He use an experimental setting to compute the ROI for four different approaches: traditional plan-driven project delivering near the end, an unfocused project with continuous delivery, a focused project with an 80/20 Pareto distribution of value and a focused project with an 80/50 Pareto distribution of value. The results prove that focus and rapid feedback in the form of continuous delivery are game-changer.

Choosing the Right Scrum Sprint Length

April 25, 2012 0

What should be the lenght of a Scrum sprint? There is no unique answer to this question. In this blog post, Mitch Lacey provides some key factor to consider when you try to choose the right sprint length for your Scrum project. These should be considered looking at the expected duration of the project, the customers/stakeholders and the Scrum team. His conclusion is that the right sprint length balances a craving for customer feedback and input with the team ability to deliver and the customer’s ability to respond.

What Works in Scaled Agile: Feature, Component or Mixed Teams?

April 23, 2012 0

One of the first steps in an Agile adoption is the formation and organization of agile teams. Leadership often struggles to figure out how many people should be on each team, what skill sets should included, and whether the team should be focused on solution components, feature delivery, or a mix.

Sprint Are not Just for User Stories

April 17, 2012 0

How do you manage activities that don’t seem directly related to features in your Scrum sprints? This blog post discusses why it is a problem when Scrum teams start to wonder about having time to manage infrastructure, technical debt or test framework. For Johanna Rothman this is the sign that the culture is not Agile enough and that the product owner doesn’t want to take iteration time to schedule anything other than features in an iteration. She offers seven hints on how to improve this situation, saying that product owners that don’t want to fund technical debt will instead create more of it.

Managing Technical Debt in Large Software Development Projects

March 29, 2012 1

The nice metaphor of technical debt introduced some 18 years ago by Ward Cunningham has slowly taken roots in our collective conceptual toolbox, as a nice way to express some of the pains that software projects suffer from. Most software developers who have had some experience with significant, long-lived projects can feel it, sometimes point to it, but more than often can’t do much about it. In most cases, technical debt is seen as something very negative, burdening projects forever under increasing amount of interests. But some technical debt can be deliberate, more akin to borrowing to make an strategic investment, and this is especially the case for architectural-level debt.

Agile Support and Maintenance

March 27, 2012 0

As Agile approaches are gaining acceptance in software development organization, this article discusses how Agile could impact the support and maintenance processes of existing mature products.

« 1 … 117 118 119 120 121 … 151 »