How Codesion Does Agile Development!

Willie Wang, VP Products and Services!

Agile in Action!

Agile in Action!

•  Goals!– Quick Intro of Agile SCRUM Methodology!

– How Codesion uses SCRUM to build great products!

•  Takeaways!– Basic SCRUM knowledge!– Manage Product Backlog!– Run a Sprint!

Codesion Cloud Services!

•  Codesion FrogSAFE V4 Platform!

•  Distributed Product Management and Engineering Team!

•  Self-Organization is Key!

•  Multiple Methodologies!

•  Product has multiple themes!

Agile SCRUM!

Artifacts – Product Backlog, Sprint Backlog, Burn Down, Shippable Increment!

Meetings – Sprint Planning, Daily SCRUM, Sprint Review, Sprint Retrospective!

Roles – Stakeholders, Product Owner, Scrum Master, Team!

Product Backlog"(Product Owner)!

The Product Backlog (PB)!

•  List of prioritized features, PBI!

•  Prioritized using stack ranking!

•  Answers the question, what will be built!

Three C’s of User Stories!

Card!used for planning, notes reflect

priority & cost (story points)!

Conversation !follow up cards with a discussion

& documents!

Confirmation!acceptance test that outlines how the

product owner & team knows something is done!

User Story Example!

As a user, I want to be able to pick and choose resources from multiple pages and then save so

that I can save time!

Acceptance Criteria!

•  The user selects one, or many or all resources from any results page!

•  The users' selections persists as the user navigates from page to page!

•  If user does not click on any result and clicks "Save" then it saves resources only the current page!

•  If the user selects something in any of the results pages and click save on any of the pages, it saves only the selected results!

Codesion Product Backlog!

•  We keep both user stories and defects in the same PB, they are both PBIs!

•  We use planning folders to categorize our PB!

•  PB with more than 100 PBIs becomes unmanageable!

Manage PBI!

•  Associate detailed documents to PBI!

•  Discussions and mailing list for PBI!

Product Backlog Grooming!

Product Backlog (PB) Grooming!

•  PB Grooming happens before a Sprint can start!–  Product Owner (PO), Scrum Master (SM)!

•  PB Grooming results in Sprint Backlog for the team to work on!–  PO, SM!

•  PB Grooming requires participation of stakeholders, product owner, scrum master, and the team!–  All!

When to Start Grooming!

GROOM!

4 week sprint – start mid-end of 3rd week!

2 week sprint – start beginning of 2nd week!

Key Concepts!

•  Product Backlog!

•  PBIs!

•  Sprint Backlog!

•  Story Points!

•  Fibonacci Numbers (1, 2, 3, 5, 8, 13, 21, 34)!

•  Affinity Estimation Technique!

Sprint Planning!

Sprint Planning Meeting!

•  Team decides tasks required!

•  Scrum Master facilitates the meeting!

•  Product Owner clarifies user stories!

Task Management!

•  Assigned Team Member fills out estimated effort!

•  Sprint Starts – fill out remaining effort on a daily basis!

Sprint Starts!

Sprint Starts!

•  Set Planning Folder Status (SM)!

•  Set Start and End Date (SM)!

•  Update Task Status (TM)!

•  Update Remaining Effort (TM)!

Sprint In Progress!

•  SVN Commit Association (TM)!

•  Track Knowledge via Discussions (ALL)!

•  Add Tasks and Defects as children of PBI (TM)!

Impediments!

Team!Product!

Organization!

Reporting!

Remaining Effort!

Burn Down Chart!

Try It Yourself!

codesion.com/teamforge-trial!

training videos at help.codesion.com!

Questions?"

visit blog.codesion.com!