�ݺ�ߣ

Agility is all about driving value!Vibhu Srinivasan vibhu@agilefaq.net “Its important to be agile not to do agile”

AgendaVisiting the Agile Manifesto.Product Owner Team.MetascrumUser stories What are they .Your role on Agile team.Planning and estimation.Next Steps.

Agile ManifeSTOWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

Core Values/ PrinciplesOur highest priority is to satisfy the customerthrough early and continuous deliveryof valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. CommitmentFocusOpennessRespectCourage

ExerciseWhich of these values matter to you a lot?

Approaches to developmentPredictive approach– Heavy-weight;– Process-oriented;– Plan-driven;– “Waterfall”.Adaptive approach– Light-weight;– People-oriented;– Value-driven;– “Agile” and “Lean”

Agility is all about delivering value

Scrum – A tool to help you succeed

Scrum DefinedRoles– The Team– ScrumMaster– Product OwnerArtifacts– Product Backlog– Sprint Backlog– Sprint/Release BurndownChartMeetings (ceremonies)– Sprint Planning– Daily Scrum (“Stand-Up”)– Sprint Review (Demo)– Retrospective

Product Owner Team AKA Product Definition TeamNone of us is as smart as all of us – Ken Blachard

Scaling ScSScaling rum – Issues Scaling Agile IssuesParallel teams Multiple goals Shared resourcesProduct owners are tasked with carrying the product backlog and be always prepared for all sprint planning meetings.

Scaling Agile - Agility Defined

Product Owner – give me all the requirements now

Product Definition TeamAn agile team responsible for keeping your product backlog in good shape ( well groomed). Sprint ReadyStory Sizes

Your PDT is now meeting many times a week 100 Percent CommittedABC– Chief Product Owner XYZ– Area Product OwnerAGS– Area Product OwnerADF– Area Product Owner - Area Product Owner.This group clearly are the product managers and own the backlogAround 30 percent Developers ,Testers, architects, UX etc. This group is primarily to help the backlog be more accurate.

A few changes !!PDT will keep the various backlogs constantly groomedThey own the roadmap , but the teams directly add a realistic view to the roadmap by doing release planningScrum masters need not have to schedule repeated grooming sessions. The PDT should be doing this.As always this group will inspect and adapt.

Metascrum- What another meeting!

Metascrum DefinedAttended by key stakeholders, product definition team, scrum masters and architect and sometimes team membersThis meeting has a strategic intent unlike the tactical intent of daily scrum. In a Metascrum you discuss where all these features are in flight as compared to the overall roadmap for that group. This is a place to resolve any impediments the teams have not been able to resolve on their own.This group meets every two weeks now on a thursday

AgendaVisiting the Agile Manifesto.Product Owner Team.MetascrumUser stories.Your role in your agile team.Next Steps.

User story A piece of functionality that is needed to add value to the product. A good story has well defined acceptance criteria.The three C’s of a User StoryC = CardC = ConversationC = Confirmation

More on user storiesUser stories bring in the notion of just in time requirementsYou don’t need use cases. Stories are enough if you have a good product owner.Stories are only complete with acceptance criteria. You can say “NO” to working on stories if the team does not get what the story means. You should give input to the order the stories are built. You may know of dependencies that product owners don’t.

Every story you take should pass the invest model test.I – IndependentN – NegotiableV – ValuableE - EstimableS - SmallT - Testable

User story - what it does not have!Technical specificationsAll the details up front like in a use case or functional specification.Database fieldsProduct owners should tell the “what” not the “how”

What about technical stories ? The shiny bunny problemEvery sprint the team could buy certain story points to work on technical stories, like enhanced logging, implementing a MVC etcArchitects may have some points too for some of their larger initiatives. But always show value in your stories – Write them as abusive stories, word them in a way a product owner will see value.

Product Backlog A collection of user stories, well prioritized by the product owner is a backlogPlease ask your product owner or your PDT about where your backlog isBacklog never ends, the product owners can choose to ship at any point they see value.

“Customers have the right to demand working software but they should respect your estimates”

Roadmap and release plan Teams should know what their roadmap is. Ask your product owner where the roadmap is?You should know the product vision, the roadmap, when your next release plan is or where it is?

Your role is an agile team What you need is testing not tester. Developing not developer.The shift from I – We – Us is very toughRemember the art of active listening.

Agile team characteristicsSelf organizingInspect adapt natureDeliver FrequentlyCommunicate and listen well They believe in testing well.They always can show value in work they doThey keep an eye on the baton not the runners.

�ݺ�ߣ

Scaling Agile - Agility Defined

More Related Content

Scaling Agile - Agility Defined