This class is taught by a Certified Scrum Trainer but is not a certification course.

Contact Citerus in Sweden to inquire about the last few spots in this. The company can be reached at  018-51  51 13.

Course Description

Projects start with their requirements. How those requirements are documented or expressed has a tremendous influence on the rest of the project. User stories originated in the agile processes but are useful even if you are not planning to use an agile process.

The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. However, user stories are an effective approach on all time-constrained projects. In this course, we will look at how to identify and write good user stories. We will see the six attributes all good stories must exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project's initial stories.

When you have the requirements down, you need some kind of plan. Planning is important, even for agile projects. Unfortunately, we've all seen so many worthless plans that we'd like to throw planning out altogether. The good news is that it is possible to create a project plan that looks forward six to nine months that can be accurate and useful. Too many teams view planning as something to be avoided and too many organizations view plans as something to hold against their development teams.

During this two-day workshop we will have the opportunity to practice identifying user roles and writing stories on a case study. You will learn how to break that cycle by learning and practicing skills that will help create useful plans that lead to reliable decision-making. You will leave with a solid understanding of and experience at agile release planning and iteration planning. We will look at various approaches to estimating including unit-less points and ideal time. The course will describe four techniques for deriving estimates, including how to use the popular Planning Poker technique. We will look at techniques to create a plan that dramatically improves the project's chances of on-time completion.

Participants Will Learn

  • The essential elements of Scrum
  • How to achieve potentially shippable software each sprint
  • The responsibilities and characteristics of the Product Owner and Scrum Master
  • What happened to the project manager
  • How to properly stock a product backlog
  • The benefits of user role modeling
  • How to write user stories that conform to the six attributes of a good product backlog item
  • Scaling the product owner role on large, multiple-team projects
  • The difference between estimating size and duration and how to do both
  • The user of Planning Poker for estimating
  • Four techniques for prioritizing the product backlog
  • How to estimate velocity when the team hasn't yet run a sprint
  • Release planning including on fixed-scope and fixed-date projects

 

What’s Provided

Participants will receive printed and bound course materials at the start of class. Continental breakfast, lunch, snacks and drinks will be served.

Professional Development Units (PDUs)

PMPs: You can receive 16 PDUs for this course.
Dates:

28-29 May 2008
Location:

Stockholm, Sweden

Venue:

World Trade Center
Klarabergsviadukten 70 / Kungsbron 1
Stockholm, Sweden
http://www.wtc.se/wtc_eng.aspx

Price:

SEK 14. 500

  • It's a communication problem
  • What user stories are
    • Card, conversation, confirmation
    • Some examples
    • Adding detail
    • The product backlog iceberg
    • Augmenting user stories
  • Users and user stories
    • Proxy bias
    • User roles
    • User role modeling
    • Personas
    • Extreme characters
  • Gathering stories
    • Questionnaires
    • Observation
    • User interviews
    • Story-writing workshops
  • INVEST in good stories
    • Independent
    • Negotiable
    • Valuable
    • estimatable
    • Sized Appropriately
    • Testable
    • Additional guidelines
  • A tools interlude
  • Created case studies
    • Creating and selecting case studies
    • Writing the product backlogs
    • Lessons Learned
  • What user stories are not
    • Use cases
    • IEEE 830 Software Requirements Specs
  • Why user stories
  • Why not user stories
  • The Purpose of Planning
  • Estimation Units
    • Desirable attributes
    • Estimate size, derive duration
    • Estimating in story points
    • Estimating in ideal time
    • Debating the merits
  • Techniques for Estimating
    • Triangulation
    • Effort vs. accuracy
    • Planning poker
  • Re-estimating
    • Three re-estimation scenarios
  • Sprint Planning
    • Velocity-driven
    • Commitment-driven
  • Release Planning
    • How to estimate velocity
    • Velocity as a range
    • Predicting project completion
    • Rolling lookahead planning
    • Fixed-date projects
    • Fixed-scope projects
    • Fixed-everything projects
  • Twelve Final Guidelines

This course is equally suited for managers, programmers, testers, or anyone involved in estimating or planning a project. Participants will be able to return to their jobs with specific recommendations and actions they can perform to improve their current plans and projects.