A Toolset for Creating a Potentially Releasable Product Increment

Working software is one of the four Agile values. However, Agile practitioners today are seen following anti-patterns like special sprints for integration, leaving regression testing to special QA focus groups etc. This talk will set the stage by defining the context leading to such decisions. and indicative symptoms. This talk will conclude with recommendations to address the anti-patterns described earlier. Narratives, real-world examples and lessons learned from actual experience would be provided for the audience as key takeaway.

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Outline
Context of Modern Software Development 8-10
Symptoms to lookout for 5-7
Recommendations 25-35

Learning Outcome

Working software is one of the four Agile values, gets mentioned twice in Agile Principles and is more elaborately described as "potentially releasable product increment" in the Scrum Guide repeatedly as well. However, Agile practitioners today are seen following anti-patterns like special sprints for integration, leaving regression testing to special QA focus groups at the later end of release cycle etc. This 45 minute talk will set the stage by defining the context and market trends that usually leads to such decisions. A set of symptoms will be described to suggest the practitioners that a deeper analysis of practices is required. This talk will conclude with recommendations to address the anti-patterns described earlier. The recommended set of practices is based on good old Agile principle of 'continuous attention to technical excellence'. Narratives, real-world examples and lessons learned from actual experience would be provided for the audience as key takeaway; to go back and start creating a potentially releasable increment, every Sprint!

Agile/Scrum adoptions are simple in the beginning and (mostly) everyone sees the benefits. However, the biggest hurdle in having a successful adoption over a sustained and longer period of time is negligence of technical excellence by the teams. They become unable to deliver what they promised or what they used to in the beginning due to cutting corners and not upholding the code quality.

With this session, I am attempting to bring to foreground the practices that are practiced at successful Agile shops but are still far from being ubiquitous world-over. Not only this is aligned with the Craftsmanship aspect of the conference but i also hope that this will set the attendees on a journey and some of them will take away the best practices, read more about them and will, eventually, help their companies deliver products that customers love.

Target Audience

Development Team Members, Scrum Masters, Product Owners, Functional Managers, Architects, Testers, Business Analysts

Prerequisite

None

schedule Submitted 2 weeks ago

Comments Subscribe to Comments

comment Comment on this Proposal