|
|
|
|
|
|
|
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
|
|
|
|
CBAP and Agile Development (3/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 of age.Mike talked about his own experience discovering the CBAP […]
Agile Development and Requirements Documentation (10/5/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 best for them.At Red Rock Research, we show groups practicing Agile […]
Software Development Best Practices - Software Requirements Management (7/18/2009)
I recently hosted Red Rock Research’s second weekly software development best practices seminar for the general public. Our topic was Software Requirements Management.Requirements Management is perhaps the most controversial topic in software development. Everyone seems to have their own technique. It is also the most important skill-set–statistically more important than development skills–to the overall success of a software […]
Software Development Best Practices - Software Estimation (7/10/2009)
Red Rock Research held our first of a weekly series of seminars on software development best practices yesterday at the Miller Campus – Professional Development Center. Our topic was Software Estimation. We covered the typical informal methods: Fuzzy Logic, Wide-band Delphi, Planning Poker, and the primary formal methods: Function Point counting, the Putnam Model, COCOMO […]
A Free Software Requirements Specification Template (SRS)! (5/19/2009)
Need a good software requirements specification (SRS) template? Use an industry-standard SRS. Can’t find one? Well now you have-get it here for free. Enjoy! Mike J. Berry www.RedRockResearch.com Software Development Process Guidance
25 Most Dangerous Information Security Programming Errors (1/18/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) Programming Errors. Expect to see future government and big-money RFP’s mandate these items […]
Anatomy of an Execution Plan (1/11/2009)
Have you been challenged with performing a high-risk task like upgrading a prominent server, for example? Here’s an execution plan template that you can use to guide you. I. Executive Summary Brief overview of intended event. II. Review of Discovery Details of what efforts were made to research what is listed in the following sections. Meetings, […]
|
|
|
|
|
|
|
|