This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
User Stories Usually Are the Items in Product and Sprint Backlogs Small enough to be accomplished within a sprint Groomed and refined Split as needed to get small enough
Two Types of Requirements:Business/User/Customer Product/System/Software Business/user/
stakeholder/ customer language & view, conceptual; exist within the business environment
Serves business objectives
What business results must be delivered to solve a business need (problem, opportunity, or challenge) and provide value when delivered/satisfied/met
Language & view of a human-defined product/system
One of the possible ways How (design) presumably to accomplish the presumed business requirements
Often phrased in terms of features/external functions each piece of the product/system must perform to work as designed (Non/Functional Specifications)
Guidelines for Getting the Problem Pyramid™ Right (1 of 2) Is the Problem really the problem?
– Do the measures fit it?– Does it provide REAL value when goal measures achieved?
Are the Causes in fact the causes of the Problem?– Do they reasonably explain why we have the Problem?– Have we identified all the likely key causes?
Does the Should Be solve the Problem?– Is it business whats likely to achieve goal measures?– Does it address (and reduce/eliminate) each key Cause?– What else to address that this affects or is affected by this?
What Should Be (Requirements) How (Design) Measure-Goal
Example(3 of 3)
Not reusing toadvantage
Lack of awareness No incentivesNot invented here Hard to find itemsLimited data access
(Low) X% reuseSpend Y dollarsTake Z monthsto build systems
(Hi) X+ reuseSpend Y- $Take Z- monthsto build systems
People understand how to do reuseand why it helps them get their jobs done quicker, easier, better.
People have meaningful support and encouragement to take the time to make relevant items reusable.People can easily access, identify, and retrieve relevant reuse items.
· President of Go Pro Management, Inc. consultancy since 1982, working directly with and training professionals in business engineering, requirements analysis, software acquisition, project management, quality and testing.
· Partner with ProveIT.net in REAL ROI™ and ROI Value Modeling™.· Previously a developer, systems programmer/DBA/QA, and project leader with the City of Cleveland, leading
financial institutions, and a “Big 4” consulting firm.· Degrees: Kenyon College, A.B.; Pennsylvania State University, M.S. in Psychology; Suffolk University, J.D.;
Boston University, LL.M. in Tax Law.· Published author and frequent speaker at leading professional conferences.· Formerly International Vice President of the Association for Systems Management and Executive Editor of the
Journal of Systems Management.· Founding Chairman of the New England Center for Organizational Effectiveness.· Member of the Boston SPIN and SEPG’95 Planning and Program Committees.· Attendee Networking Coordinator for STAR, Better Software, and Test Automation Conferences.· Chair of record-setting attendance BOSCON 2000 and 2001, ASQ Boston Section‘s Annual Quality Conferences.· Member IEEE Std. 829 for Software Test Documentation Standard Revision Committee.· Member IEEE P1805 working group to develop a standard for Requirements Capture Language (RCL).· Member IEEE P730 standard for Software Quality Assurance Revision Committee.· International Institute of Business Analysis (IIBA) Business Analysis Body of Knowledge (BABOK) subject expert.· TechTarget SearchSoftwareQuality.com requirements and testing expert.· Admitted to the Massachusetts Bar and licensed to practice law in Massachusetts.· Author of book: Discovering REAL Business Requirements for Software Project Success