 |
|
|
|
|
|
|
|
|
|
|
|
REQUIREMENTS ENG
Education Roadmap
Course Catalog
Public Course Calendar
Onsite Training
Courseware Licensing
Related Courses
Writing Requirements
Agile Development with Scrum
Agile Development with MSF Agile
Agile Software Testing
Agile Project Management
Scrum Planning and Estimating
|
|
|
|
|
|
|
|
|
| Agile Requirements Modeling - Personas, User Stories and Use Cases |
|
|
Public courses in Seattle - San Francisco - Boston - New York City - Chicago - Houston (USA), Vancouver - Toronto - Montreal (Canada), Guadalajara (Mexico) - Santiago (Chile) - Sao Paulo - Rio de Janeiro (Brazil) - Dublin (Ireland) - London (UK) - Amsterdam (Netherlands) - Brussels (Belgium) - Paris - Nice (France) - Zurich (Switzerland) - Barcelona (Spain) - Moscow (Russia) - Tel Aviv (Israel) - Riyadh (Saudi Arabia) - Dubai (UAE) - Delhi - Mumbai - Bangalore (India) - Seoul (Korea) - Shanghai (China) - Kuala Lumpur (Malaysia) - Singapore - Tokyo (Japan) - Sydney - Melbourne (Australia) - Auckland (New Zealand)
Onsite training worldwide | E-learning available | Courseware licensing available |
|
This workshop training course teaches students how to perform business analysis for agile projects. The course includes best practices for eliciting, analyzing, specifying and verifying requirements. Students learn how to model users, write user stories, and derive use cases. For evolving requirements, this course shows how to perform just-in-time elaboration of features, and how to incorporate late changes during agile iterations.
|
|
|
|
|
|
Code |
|
R20
|
|
|
|
Discipline |
Requirements Engineering |
|
|
Duration |
2 days |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Course Information
Audience | At Course Completion | Prerequisites | Course Materials | Course Outline | Pricing | TAKE THIS TRAINING |
Audience
| √ |
|
Software Process Architects |
|
√ |
|
QA/Test Managers |
|
√ |
|
Development Managers |
| √ |
|
Business Analysts |
|
√ |
|
QA User Testers |
|
√ |
|
Software Developers |
| √ |
|
Project Managers |
|
X |
|
QA Code Testers |
|
X |
|
User Education Specialists |
| |
|
|
|
|
|
|
|
|
|
|
at course completion
After completing this course, participants will be able to:
| » |
|
Recognize stakeholder patterns |
|
» |
|
Review and update user stories |
| » |
|
Define vision and scope |
|
» |
|
Estimate user stories |
| » |
|
Elicit and write user stories |
|
» |
|
Negotiate at the Sprint Planning meeting |
| » |
|
Analyze and prioritize |
|
» |
|
Incorporate changes |
| » |
|
Create user proxies |
|
» |
|
Derive use cases |
prerequisites
| » |
|
Intermediate knowledge of software engineering |
course materials
A comprehensive workbook with knowledge material, examples, case studies, lab exercises, and references.
| course outline |
|
|
 Module 1: Introduction to Requirements Engineering
| » |
|
Problems, objectives, requirements and specifications |
| » |
|
Classification of requirement types |
| » |
|
Business requirements |
| » |
|
User requirements |
| » |
|
Software requirements |
Module 2: Agile Projects
| » |
|
The requirements development pipeline in agile projects |
| » |
|
Integration of requirements in the SDLC |
| » |
|
Dealing with unknown needs |
| » |
|
Tailoring the process for Agile environments |
| » |
|
Traceability and metrics |
Module 3: Project Scope and Business Requirements
| » |
|
Defining the business context |
| » |
|
Breaking the scope into logical sets of capabilities |
| » |
|
Assigning and agreeing upon stakeholder roles |
| » |
|
Building the business case |
| » |
|
Establishing business areas, goals and requirements |
| » |
|
Framing requirements to support business strategy and customer justification |
Module 4: Writing User Stories
| » |
|
Identification of sources |
| » |
|
Identification of stakeholders |
| » |
|
User stories |
| » |
|
User profiles |
| » |
|
The voice of the customer |
Module 5: Elaboration and Estimating of User Stories
| » |
|
Requirements prioritization and scrubbing |
| » |
|
Improving requirements through prototyping |
| » |
|
Bridging from existing to new functionality using a gap analysis |
| » |
|
Estimating User Stories |
Module 6: Creating Use Cases
| » |
|
Use case development |
| » |
|
Requirements for multiple audiences |
| » |
|
Document layout and structure |
| » |
|
Non-functional requirements |
Module 7: Validation and Verification
| » |
|
Review sessions and fit criteria |
| » |
|
Dealing with dependencies and inconsistencies |
| » |
|
Verification through test case design |
| » |
|
Negotiating conflicting requirements |
Module 8: Requirements Management
| » |
|
Storage and privileges |
| » |
|
Linking and accessing requirements |
| » |
|
Version control and addendums |
| » |
|
Making requirements traceable |
Module 9: Requirements Breakdown
| » |
|
From requirements to feature breakdowns |
| » |
|
Scrum Sprint Planning Meeting |
| » |
|
Organization of spec items |
| » |
|
Committing features to releases |
Module 10: Change Management
| » |
|
Dealing with new ideas |
| » |
|
Sources of requirements changes |
| » |
|
Controlling and enabling change |
| » |
|
Mechanisms to support triaging |
Module 11: Tools Support
| » |
|
Available tools |
| » |
|
Evaluation criteria |
| » |
|
Case: Atlassian Confluence wiki |
Certificate
Participants receive an industry recognized SoftO2 Education Certificate upon completion of the course.
pricing
Please refer to the pricing chart.
take this training
Contact SoftO2 Education or send the following form to pre-register or request information.
|
|
|
