|
|
|
|
|
|
|
Course Overview
|
|
|
Did you know that requirement management skills are more important--statistically--than
development skills to the overall success and timeliness of a software project?
Our three day seminar trains attendees to follow the iEEE SWEBOK best practice requirements
process of elicitation, analysis, specification, and validation. We provide methods for identifying actors, identifying their needs, data-flow tracing, and then capturing
the requirements baseline into a Software Requirements Specification (SRS) document.
We cover managing requirement changes via proper change control. Finally, we review
effective interviewing techniques and group collaboration strategies. Be sure your team is equipped with these skills. |
|
|
Benefits
|
|
|
- Learn to identify requirement sources
- Learn to overcome common requirements errors
- Learn various ways to write requirements
- Learn elicitation goals and techniques
- Learn Use Case diagramming using free UML tools
- Learn to construct data-flow diagrams
- Learn to prioritize project requirements
- Learn to identify and qualify project risks
- Learn to create a Work Breakdown Structure (WBS)
- Learn how a project progresses
through the PRD to HLA to SRS
- Learn to create a High Level Analysis (HLA) document
- Learn to create a Software Requirements Specification (SRS) document
- Learn to build a product roadmap
- Learn the five types of software estimates
- Learn to align project requirements with business goals
- Learn about upstream and downstream traceability
- Learn to manage scope creep via change control
- Learn to conduct proper requirement approvals, and effectively
manage approval noise
- Learn effective interviewing techniques for in-house and off-site
stakeholders and subject matter experts
- Learn the value of a requirements showcase
|
|
|
|
|
 |
 |
Software Requirements Course Overview
|
 |
|
|
|
|
|
|
Our course contains the following program:
Part I - A Business Case for Improving Requirement Skills
- How critical are requirements development skills to the overall success of a software
project?
- Software project success rate trends.
-
Common challenges facing requirements management.
- What you should know about requirements errors.
- Ten unavoidable truths about software requirements.
Part II - Understanding Software
Requirements
- Who gathers requirements?
- What is the role of the requirements gatherer?
- Sources of requirements.
- What is a requirement?
a. PMI� definition
b. iEEE� definition
- Domain, Problem Space, Solution Space
- What a requirement isn't!
- Types of requirements:
a. Governing requirements
b. Emergent requirements
c. Component requirements
- Business Rules:
a. Sources of Business Rules
- Parts of a requirement:
a. The Identifier
b. The Classifier
c. The Description
d. The Constraint
- Example Requirement
- Test-driven requirements
- Requirement Traceability
- Some common ways to write requirements:
a. Natural form
b.
Formal form
c. Use cases
d. User stories
- What to do with unknown requirements.
Part III - How to structure software requirements documents
- Survey of software project types.
- Documentation Audiences.
- Documentation and Trust.
- How much time is typically spent on Requirements?
- How to speed up the requirements process.
- How to structure requirement documents.
Part IV - A requirements baseline development framework
- A Process for gathering requirements:
a. Elicitation
b. Analysis
c. Specification
d. Validation
- Requirements elicitation.
- Requirements analysis.
a. Prioritizing requirements:
i. Risk driven prioritization
ii. Critical path prioritization
iii. Strategic prioritization
- Requirements specification.
a. HLA, SRS, SDD, COO
- Requirements validation.
- Requirement �baseline� approval.
- The approval process.
PART V - After the baseline
- Triple constraint project dynamic
- Managing change: Change Control
- Keeping a change history log
- Managing schedule impact
Part VI - Collaboration
- Interviewing etiquette
- Questioning techniques
- Active listening
- Group dynamics
- Five dysfunctions of a team
- Meeting etiquette
- Facilitation and facilitative workshops
- Negotiation
- Handling special situations
Part VII - Improving your skills going forward
- Four strategies to improve your requirements management performance going forward.
|
|
 |
|
 |
|
|
|
|
Software Requirements
Activities
|
|
|
|
Attendees perform the following:
- Requirements skills evaluation
- Identify sources for requirements
- Define problem space
- Build a Product Roadmap
- Identify requirement categories
- Create an Enterprise Business Rule repository
- Document requirements in various formats
- Overview of requirements documents
- The requirements management process
- Create a User Needs Model with UML
- Create a Data-Flow Model with UML
- Risk-driven prioritization worksheet
- Business Goals/Requirements alignment worksheet
- HLA Template examine & discuss
- SRS Template examine & discuss
- SDD Template examine & discuss
- COO Template examine & discuss
- Requirements traceability matrix worksheet
- Create a Work Breakdown Structure
- Create a change control agenda
- List requirements packages
- List showcase items
- Complete course takeaway list
- Create a back-to-work plan
|
|
|
|
|
|
|
|
|
Software Requirements
Posts From Our Blog . . . more at
Blog.RedRockResearch.com
|
|
|
|
The Stable FrameworkT: Empowering Information Technology Organizations to Shift Left (Jul 09, 2023)
In today’s fast-paced and competitive digital landscape, information technology organizations are constantly seeking ways to improve software quality, accelerate time-to-market, and enhance customer satisfaction. One powerful tool that enables organizations to achieve these objectives is The Stab [...]
PMI’s Process Owner vs. Process Manager (Mar 22, 2023)
PMI (the Project Management Institute) has recently introduced new content into it’s curriculum....the Process Owner and Process Manager. The distinction between these two roles seems to originate from ServiceNow’s influence.
In small organizations the same person wears both hats, but in larger [...]
How to Best Manage Project Risks and Issues (Feb 24, 2023)
Managing project risks and issues is an important aspect of project management. Here are some best practices to help you manage project risks and issues effectively:
Identify and assess risks: Identify potential risks that could impact the project and assess their likelihood and potential im [...]
How to Manage Project Scope Changes (Feb 21, 2023)
Managing project scope and change is a critical aspect of project management. Here are some best practices to help you manage project scope and change effectively:
Define the project scope: Clearly define the project scope, including what is included and what is excluded. This will help you [...]
Where did the term "Gherkin" originate and get used with Agile User Stories? (Feb 17, 2023)
The term "Gherkin" is associated with Agile user stories because it is the name of a specific format for writing user stories that was introduced by the Cucumber testing framework. Cucumber is a popular open-source tool for Behavior-Driven Development (BDD), which is a software development method [...]
PMI Announces the PMI-PBA Certification! (Mar 31, 2014)
The Project Management Institute (PMI) announced a new certification for Business Analysts. Called the Professional in Business Analysis, the PMI-PBA is a program for business analysis, and many other professionals who perform business analysis activities.
Think of Business Analysis as what [...]
One or Two Day Tasks (Dec 09, 2012)
Recently while coaching Agile to a large client in the Salt Lake City area one of the developers on one of the teams asked me why an Agile team should decompose features into one or two day units of work. It seems, he said, the particular unit of work he was considering could not be broken down [...]
CBAP and Agile Development (Mar 17, 2011)
I attended an excellent presentation hosted by the Northern Utah PMI Chapter, featuring Mike Sandberg, Novell’s Chief Business Analysts. Mike spoke to a room of well over 200 folks about the CBAP certification. This is the Certified Business Analysis Professional credential that us now coming o [...]
Agile Development Requires Documentation (Oct 05, 2010)
I keep hearing horror stories from managers about how their teams that have adopted Agile Development insist there are no documented requirements necessary when using the Scrum framework.This is wrong.
Scrum is intentionally quiet about software requirements so that groups can use what works b [...]
25 Most Dangerous Information Security Programming Errors (Jan 17, 2009)
Want to visit ground-zero for data security? Experts from SANS, MITRE, SAFECode, EMC, Juniper, Microsoft, Nokia, SAP, Symantec, and the U.S. Department of Homeland Security’s National Cyber Security Division last week presented a listing of The Top 25 Most Dangerous (Information Security) Progra [...]
Book Review: Reinventing Strategy (Nov 27, 2007)
I just finished reading Willie Pietersen’s book, Reinventing Strategy: Using Strategic Learning to Create and Sustain Breakthrough Performance.Pietersen first sets the stage for the rest of the book by underscoring the need for organizations to be adaptable. He paraphrases Charles Darwin, conclu [...]
Agile Development and Government Contracts (Nov 13, 2007)
So I attended our SLC-based agile development forum yesterday. Alistair Cockburn was there, along with some other associates from around the valley. We discussed various successes and challenges with using the Agile Development Model for software development.
One particular topic that became a [...]
|
|
|
|
|
|
|
|