Agile Buddha - Page 11 - Demystifying Agile, Getting to its Core

Traditional Testing will be Dead Soon!!

Repeated software-development tasks are becoming automated through the application of Continuous Delivery and DevOps. If developers are taking more and more testing responsibilities into their hands, I wonder what will be the role of traditional (manual **only**) testing and testers moving forward?

Spotify Scaled Agile Case-Study – Lessons For Smaller Teams

by ShriKant Vashishtha Leave a Comment

A while back, Henrik Kniberg published an excellent case study on Scaling Agile @ Spotify. Though case study is specific to Agile scaling experiences at Spotify, some practices are equally important for smaller teams as well. This post tries to capture the essence from smaller team’s perspective.

Break Silos

A lot of organizations still works in functional silos.

For instance, in a bank, there may be one team for web banking, another team for home-loans and yet another one for mainframe based core-banking. Business features however in general cut across all these teams.

Continuous Inspection Session on YouTube

by ShriKant Vashishtha Leave a Comment

Last month I did a session on “Continuous Inspection – How to define, measure and continuously improve code quality?” in DiscussAgile conference.

The session is available on Youtube now. Enjoy and feel free to ask questions related to the subject.

Agile Thinking : How Can I Help You ?

by ShriKant Vashishtha 2 Comments

One of the key values of Agile is its focus on delivering working software or solution. This approach is the key catalyst of some behavioural, cultural, and structural changes.

The team members contribute to delivering working solution but their individual goals on their own don’t help the user much. For instance, just the UI part of a user-story is of no use to a user. If developers just focus on building the solution but not on the quality aspect, again it doesn’t result into product ready increment.

Essentially cross-functional team members have to collaborate and help each other to deliver the Sprint goal.
[Read more…] about Agile Thinking : How Can I Help You ?

Scrum Backlog: Epic, User Story, Acceptance Criteria

by Avienaash Shiralige 3 Comments

Often, I get to hear questions about level of details that need to go in the product backlog stories. How detailed should be the acceptance criteria? or how small the story should be? We all know stories matures with time. I really like this post on user story life-cycle. Please take time to read this. Let’s consider an example now.

User Story example: As a Project Owner(PO), I should be able to transfer complete project ownership to my connection, with my role remaining to be just a project creator(author) after transfer.

Note: At the first sight, it is tough to say whether this is a story or an epic. When this story comes up in backlog grooming meeting, teams might completely miss the magnitude of such stories. Hence, as the product becomes bigger it is wise to start detailing stories by adding acceptance criteria earlier in grooming meetings itself. Impact of every new story gets wider as product becomes bigger which often gets missed by the team.