Hands-on Agile Development, Planning, Requirements and Peer Reviews Workshop
Class Coordinator Preparation Notes
Some simple preparation is required before the class. If you have any questions, please call Neil Potter 972-418-9541, neil at processgroup dot com, or use our contact page.
- Each student connects with audio and video
- Students can log in a second time with a phone for video if their laptop video is disabled
- Please have each student test his/her hardware and software before the event.
Bring project work to develop requirements for
This workshop provides you with skills to develop, write and manage software requirements.
Each project team needs to bring one of the following (whichever you have, or would like to work on):
- A project description or project goal that you would like to create software requirements for
- An existing software requirements document that you would like to refine
The project you bring might be a small section of a larger project.
The requirements section of the workshop consists of the following topics:
- Define user classes and customer champions
- Define business and system requirements (Epics)
- Define vision statement (context diagram)
- Define user stories
- Define Use Cases
- Define quality attributes
- Define business rules
- Define functional requirements (system behavior not necessarily stated by the customer)
- Define compatibility requirements
- Define external interfaces
- Define data
- Define additional constraints
During the class you will be applying some of these ideas to your current project.
Bring project work to develop estimates for
The estimation section of the workshop will cover:
- Release planning
- Story point and effort estimation
You can either apply the estimation exercise to the scope defined in the requirements portion of the class or you can select a different scope of a current/future project to estimate.
Bring project work to review for defects
In the class we will be practicing peer reviews. To do this we need example documents to review. You should bring a real, living, current document from your work.
This class will consist of individuals with a variety of technical backgrounds. Please bring a document that at least a few others will be able to read and understand.
You must be the owner (or author/reworker) of the document
The document could be:
- Something being developed that you would like to find defects in, e.g., a project plan, requirements specification, code, design, test procedure or user guide
- 6-10 pages (or approximately 200-300 lines of code, not including comments) – if the document is large, choose one section
- Page and line or paragraph numbered (either by hand or printed) so that defects can be located easily
Suggested criteria for selecting the document / code are:
- The most critical to the project or program’s operation
- The most used section in the product
- The most costly if defects were to exist
- The most error-prone section (determined from current usage)
- The least well-known section
- The most frequently changed section
Bring something important and relevant to your current work.