USER GROUP MEETING
Wednesday, March 17, 2010
5:30 PM to 8:00 PM, Room B141
Fox Valley Technical College, Appleton, WI
The Agile Classroom
Session 2: Requirements (1)
Creating the Product Backlog
Moderators:
Duncan Kinchen, Red Fox Consulting, LLC
Duncan Kinchen is a Senior Project Manager and a Certified Scrum Master (CSM) with over 26 years of experience. Based in Green Bay, Duncan has led projects of all sizes in a broad range of industries. Starting with Rapid Application Development in Europe before graduating into Scrum, Duncan has followed the increasing implementation of Agile methodologies for years and is committed to the advancement of Agile principles wherever possible. He is currently one of the Program Directors for the Northeast Wisconsin (NEW) Agile Users Group.
Sandi Kappus, Air Wisconsin, Inc.
Sandi Kappus is an Applications Manager and a Certified Scrum Master (CSM) with Air Wisconsin Airlines the largest independently held regional airline in the United States, Air Wisconsin Airlines Corporation (AWAC) performs flying services for US Airways, and ground handling services primarily for United. Sandi has over 10 years of experience in business analysis, project management and portfolio management spanning the financial sector as well at the airline industry. Sandi currently sits on the board for the NorthEast Wisconsin Chapter of the International Institute of Business Analysis (IIBA). Sandi has actively been practicing the agile methodology as a business analyst, product owner and scum master and is committed to the development of business analysis and Agile methodologies.
======
The Agile Classroom (Program Overview)
The goal of this program is to stimulate discussion on relevant topics related to implementing and executing Agile methodologies. At the same time, for new or perspective Agile Users, we hope that the program will also provide a bridge between “traditional” and “agile” paths and techniques. The format for each classroom will be:
· Introduction of the topic (15-20 minutes)
· Group discussion (40-45 minutes)
These sessions are not intended to be pure lectures; the goal is to promote an environment where everyone can learn from each other’s successes and failures. The following overview is intended as a proposed outline for future topics – the actual content as well as sequence will be discussed at our meetings.
SESSIONS / DISCUSSION POINTSSession 1: Getting Started - Introducing Agile into your Organization
January 28, 2010 / · Selecting the appropriate Agile Methodology
· Top-Down or Grass Roots
· An organization-wide change
· The importance of a continuous improvement mindset
· Adoption strategies
· Your first agile project
· Impact on people and roles
Session 2: Agile Planning (1) Requirements
(Creating the Product Backlog)
Wednesday, March 17, 2010 / · Epics, features and user stories
· Principles for Agile Requirements
· Acceptance criteria
Session 3: Agile Planning (2) Estimating and Prioritizing Requirements
(Delivering Value from the Product Backlog)
Thursday, May 20, 2010 / · Story points and other estimating techniques
· Team Velocity
· Priorities and Sprint (Release) planning
JULY 2010 – SUMMER BREAK
To help plan for future classroom sessions following the summer break, please share your preferences
Preferred Topics for Future Meetings: Please list your top choices from the proposed list on the back page or other topics of your choice (in the order that you would like to see them presented).Please complete and return (or email to )
Topic: / Desired Content:
1)
2)
3)
4)
Potential Topics
Session Proposal 4: Agile Planning (3)
( Iteration Planning) / · Establishing the team environment
· Capacity planning
· Iteration duration
· Building the iteration backlog
· Decomposing features
· Defining “done”
Session Proposal 5: Iteration Execution / · Daily meetings
· Iteration burndown charts
· Team interactions
· Dealing with iterations that are tracking ahead or behind plan
· Removing impediments
Session Proposal 6: Establishing Iteration Quality / · Test case development from acceptance criteria
· QA as members of the team
· Defects and the product backlog
Session Proposal 7: Technical Considerations / · Continuous builds
· Test driven development
· Pair programming
Session Proposal 8: Ending the Iteration / · Iteration reviews
· Grooming the product backlog
· Embracing changes
· Team retrospectives
· Setting up for the next iteration
Session Proposal 9: The Product Release / · Preparing the product for release
· Training
· Product Owner acceptance
· Post-Production support
Session Proposal 10: The Agile “Project Manager” / · Project Manager Vs. ScrumMaster
· Coach, Facilitator, Enabler, Protector
· Eliminating impediments
Session Proposal 11: Other Agile Roles / · Product Owner
· Team Members – Developers, Business Analysts, Testers, Infrastructure, Database Analysts, etc.