Relevance of the '12 principles' through project lifecycle - A Practitioner's ViewSridharan Vembu
schedule 2 years agoSold Out!
This talk is about taking a closer look at how one or more of the 12 principles behind Agile Manifesto are closely connected to the different stages of the project lifecycle and how they impact the right choice of practices and tools at each stage.
Few sample scenarios:
1. Major change in the way iteration planning was done - common backlog for the platform (comprising of different application teams), think each 'iteration' as a 'release' - deployment of business features to production end of each iteration - resulted in greater collaboration, no separate integration/stabilization phase towards major commercial launch
Relevant Principle: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale
2. Reflecting on team organization - one large team (or) multiple smaller teams and / or feature teams, concepts like Mountaineers-Divers, Navigators-Drivers -> effective and easy context sharing, no stepping-into-each-others-shoes, efficient balance between big picture view and attention to details and such.
Relevant Principle: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
3. Feature kick-offs, analysis volleyballs, need basis Dev/QA/BA huddles, vide calls with distributed teams, subject-specific-google-hangouts -> Effective communication and fewer email conversations
Relevant Principle: The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
Experience clearly suggests that following the right principle at the right time for a specific situation ensures successful outcome, while ignoring one or many of these principles often results in failure.
4. Adverse effects of measuring the delivery team's efficiency of the team one-dimensionally based on the Story Points delivered
Relevant Principle: Working software is the primary measure of progress.
In this talk, through specific practical examples, I would be explaining
- identifying the right principles for each life cycle stage of the project/program
- deriving the right practices based on the principles and following them effectively to deliver value to customer
- business and delivery constraints that prevented us from adhering to some of these principles, resulting in not-so-desired outcomes
In summary, I would like to emphasis the importance and relevance of the 12 Agile Software Principles behind Agile Manifesto in everyday life of a Agile Practitioner.