Agile Buddha
Demystifying Agile, Getting to its Core
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.
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.
[Read more…] about Spotify Scaled Agile Case-Study – Lessons For Smaller Teams
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.
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 ?
Recently I got interviewed by DiscussAgile on a topic known by several names, i.e. Specification by Example, Behavior Driven Development or Acceptance Test Driven Development.
Here’s the Google Hangout recording available on YouTube.
Following topics got discussed as part of interview:
Enjoy and provide your feedback.