Transcript Kano Analysis - אתר הידע P2080 למקצועני IT

Requirements Workshop Techniques
for
E-Business Projects
Prepared by
Bruce McGinley PMP
1
RUP Best Practices
2
Agenda
E-Business Development Overview
Roles, Activities, and Artifacts
The Workshop Process
How to Measure Success
3
Where are We in RUP?
4
E-Business Development - Overview
• E-Business is about building systems, sometimes
called business tools, that automate business
processes
• Typically the tools are the business and a way to
differentiate you from your competitor
• Categories – B2B, B2C, C2B, C2C
• Many more stakeholders are involved in the
development of business tools
5
E-Business Development - Overview
Characteristics in Common with complex IS
development
• Externally imposed rules and regulations, often of
high complexity, such as business rules.
• High complexity in data structures.
• Customer focus.
• Pressed time schedules.
• Performance and reliability of the final system is a
primary concern.
6
E-Business Development - Overview
Unique Characteristics
• More emphasis on business modeling.
• More emphasis on user-interface design.
• Use of e-business enabling technologies to define the
architecture.
• A greater focus on performance testing.
7
Roles, Activities, & Artifacts
Definitions
Role – An abstract definition of a set of activities
performed and artifacts owned.
Activity - A unit of work a role may be asked to perform.
Artifact - A piece of information that is produced,
modified, or used by a process, defines an area of
responsibility, and is subject to version control.
Scenario - A use-case instance; simply a specific "path"
through the possible basic and alternative flows.
8
Roles, Activities, & Artifacts
Customer Roles
Role
Attendance Participation
Executive Sponsor
Required
Active
Business Partner
Required
Active
Subject Matter Expert Required
Active
Observer
Passive
Optional
9
Roles, Activities, & Artifacts
Development Team Roles
Role
Attendance Part.
Artifacts
Facilitator
Required
Active
None
Project
Manager
Required
Scribe
Risk list, Software development
plan, Schedule, Iteration plan
Requirements
Specifier
Required
Scribe
Software requirements
specification, Use cases
UI Designer
Required
Scribe
Prototypes
Architect
Required
Passive
System architecture,
implementation model
Data Analyst
Required
Scribe
Entity definitions, Data model
Test Manager
Required
Passive Test plan, Review requirements
Observer
Optional
Passive None
10
The Workshop Process
Uses Facilitated Sessions
• Different from most meetings
– Structured in a manner proven to achieve preplanned
results
– Its structure can be customized to meet specific needs
– There are defined roles
11
The Workshop Process
Supplies in hand prior to the Workshop
•
•
•
•
•
•
•
Laptops with software for the development team
Local network with printer (and paper)
Easel with self-sticking flip charts
White boards everywhere
Dry erase marker sets
Small sticky notes
Masking tape
12
The Workshop Process
Wall Areas Reserved
Charts
Wall areas reserved
• Parking Lot
• Action Items
• Risks and Issues
•
•
•
•
•
•
•
Use case model
Screen flow diagrams
Activity diagrams
Sequence diagrams
Functional capabilities
Business rules
Glossary
13
The Workshop Process
Prepare for the Workshop
Ground Rules
ConductPlanning Session
• Work is time-boxed to four hours so that
SMEs can get back to work and designers
can document and organize work.
• Decisions will be forced as much as possible
to get to a system quickly.
• Avoid out-of-scope issues, excessive detail and
things that developers can work out later.
• Architectural artifacts are not normally
reviewed with SMEs as they may be
confusing to them and waste their valuable
time. The architect and the facilitator refine
the design during the reconciliation portion
of the sessions.
Define a Use Case
Reconcile the Use Case
Reviewthe Use Case
Capture Non-Functional
Requirements
Create Construction
Estimates
ReviewArtifactswith
Customer
14
The Workshop Process
Prepare for the Workshop
ConductPlanning Session
Define a Use Case
Reconcile the Use Case
Reviewthe Use Case
Capture Non-Functional
Requirements
Create Construction
Estimates
Prepare for the Workshop
•
•
•
•
•
•
•
•
Inception milestone reached
Participants identified and scheduled
Meeting room reserved offsite
Projector and other resources reserved
for the duration of the workshop
Availability commitments, SME’s
participation essential, development
team may work long hours
Artifacts and templates ready
Conduct a practice meeting for the
development team
Supplies in hand
ReviewArtifactswith
Customer
15
The Workshop Process
Conduct a Planning Session
Prepare for the Workshop
ConductPlanning Session
Define a Use Case
•
•
•
Reconcile the Use Case
Reviewthe Use Case
Capture Non-Functional
Requirements
Create Construction
Estimates
ReviewArtifactswith
Customer
•
•
•
Introductions, roles and
responsibilities, sign in sheet
Process and expectations explained
Define the Use Case Model
•No use case relationships
•Don’t consolidate use cases until
flows are discussed in later
sessions
Capture risks, issues, parking lot,
action items.
Explain the 4.4.2 model
Plan and create agenda for all other
sessions
16
The Workshop Process
Define a Use Case
Prepare for the Workshop
ConductPlanning Session
•
Define a Use Case
Reconcile the Use Case
•
Reviewthe Use Case
•
Capture Non-Functional
Requirements
Detail the use case by Storyboards,
Screen Flow diagrams or Activity
diagrams
Always model the primary scenario.
Also called the ‘happy path’, ‘happy
day’, or basic scenario.
Model alternate scenarios when they:
•Are not obvious
•Need additional definition
•Can be done in the allotted time
Create Construction
Estimates
ReviewArtifactswith
Customer
17
The Workshop Process
Prepare for the Workshop
Reconcile the Use Case
ConductPlanning Session
•Only the development team participates in
this session which immediately follows the
definition session.
•Document the work that was discussed
during the previous definition session.
•Discuss the information gathered and
determine whether there are additional
questions to answer gaps in understanding
necessary for completion. These questions
will be included in the review to follow.
•Print the documents and post them on the
walls for review.
•The details are documented or edited in the
best state possible based on the definitions
at hand.
Define a Use Case
Reconcile the Use Case
Reviewthe Use Case
Capture Non-Functional
Requirements
Create Construction
Estimates
ReviewArtifactswith
Customer
18
The Workshop Process
Prepare for the Workshop
ConductPlanning Session
Define a Use Case
Reconcile the Use Case
Reviewthe Use Case
Capture Non-Functional
Requirements
Create Construction
Estimates
ReviewArtifactswith
Customer
Review the Use Case
•All participants (including SMEs) review
the printed results of the previous session.
•The facilitator leads the team around the
room to all use cases that are being
reviewed.
•The screen flows are followed through the
entire use case.
• Sequence diagrams are followed to ensure
that the documentation of the findings are
accurate.
•Pencil in changes on the wall. If the
document does not have room or is not
conducive to this, use a Post-It note with
the changes described.
19
The Workshop Process
Prepare for the Workshop
ConductPlanning Session
Define a Use Case
Reconcile the Use Case
Reviewthe Use Case
Capture Non-Functional
Requirements
Create Construction
Estimates
ReviewArtifactswith
Customer
Capture Non-Functional
requirements
•General functionality
•Usability
•Reliability
•Performance
•Supportability of the system
20
The Workshop Process
Prepare for the Workshop
ConductPlanning Session
Define a Use Case
Reconcile the Use Case
Reviewthe Use Case
Capture Non-Functional
Requirements
Create Construction
Estimates
Create Construction
Estimates
•Create task by resource chart
ReviewArtifactswith
Customer
21
The Workshop Process
Prepare for the Workshop
ConductPlanning Session
Define a Use Case
Reconcile the Use Case
Reviewthe Use Case
Capture Non-Functional
Requirements
Create Construction
Estimates
Review Artifacts with
Customer
ReviewArtifactswith
Customer
•Get sign-offs where appropriate
22
How to Measure Success
Success Criteria
• Ensure that the architecture, requirements and plans are
stable enough, and the risks sufficiently mitigated to be able
to predictably determine the cost and schedule for the
completion of the development
• Maximize collaboration with the subject matter experts
early on in the process resulting in more complete
requirements and good project involvement throughout the
project lifecycle
• Shorten overall project length
• Target developing a system that truly meets the immediate
business needs
• Obtain solid closure on expectations in terms of business
requirements, schedules, and costs.
• Focus on only what is absolutely necessary
23
Thank You!
24