working on requirements with lego™ - pm & ba 2016
TRANSCRIPT
IIBA®, the IIBA® logo, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis. Certified Business Analysis Professional, Certification of Competency in Business Analysis, Endorsed Education Provider, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
T
IIBA Italy Chapter Milan 5TH March 2016
Prassede Colombo, President
Third edition
2
Goal & Objectives
Engaging
• Volounteers and members
• Professionals
• Organizations
• University
• Orders (i.e. engineering)
• Other Associations
• New Sponsor
Growing of the BA Community in Italy
Through:
• High Quality Events and workshop to share knowledge (See Calendar)
• Services of Value for Members asGroup of Studies, News, Articles, Happy Hours, Projects
• Best Practices promotion and sharing knowledge, results, trends
• Branches Development to Boostingthe IIBA Italy Chapter mission locally (Rome + Genova + Verona)
• Corporate membership and Cooperation (Ex. Canon Italia, NTT Data)
IIBA®, the IIBA® logo, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis. Certified Business Analysis Professional, Certification of Competency in Business Analysis, Endorsed Education Provider, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
PM-BA WORKSHOP – 2016Key Concepts of BA for Value
Milan 5TH March 2016
Prassede Colombo, President IIBA Italy Chapter
4
BA & BABOK V3 Framework
BA
The practice of ENABLING CHANGE in an enterprise by defining needs and
recommending solutions that deliver VALUE to stakeholders
5
From IIBA’s BA Framework to Actions for Delivery Value
Define the Right Strategy
Monitor Solution Implementation – Traceability
Finalize Requirements Analysis & Design
Validate Implemented Solutions – Monitor Results in Field
Address the Right Solution
6
Business Analysis Value
Structuring and organizing REQUIREMENTS and DESIGNS
discovered during elicitation activities, evaluating the VALUE of the
Solution options and recommending a SOLUTION
The spectrum of value as business analysis activities progress from delivering potential value to actual value – BABOK V3
7
Requirement & Design Cycle
“Why is either the requirement or design necessary to provide value and to
facilitate the realization of an enterprise’s goals and objectives” – BABOK V3
IIBA®, the IIBA® logo, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis. Certified Business Analysis Professional, Certification of Competency in Business Analysis, Endorsed Education Provider, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
PM-BA WORKSHOP – 2016Business Analysis Technics
Milan 5TH March 2016
Carlo Liberale, VP Education IIBA Italy Chapter
9
2016 PM-BA Workshop
OBJECT
To highlight some typical technics used to capture requirements and describe a sequence of actions and tasks involving different actors
TECHNICS
1. Non functional requirement analysis2. Scope modeling
3. Use cases and Scenarios
4. User Stories
5. Lessons learned
NOTE: This list does not cover all technics that can or must be used. The references are either the BABOK V2 & V3 or both.
10
2016 PM-BA WorkshopNON FUNCTIONAL REQUIREMENTS
Purpose
The purpose of non-functional requirements is to describe the required qualities of a
system, such as its usability and performance characteristics. These supplement
the documentation of functional requirements, which describe the behavior of the
system.
Category Description
Reliability
include the ability of the application to recover from errors, uptime,
or failures in the interfaces
Performance Efficiency
include the time taken to perform activities and the resource
utilization levels
Operability can users understand how to use it and satisfy their needs?
SecurityDoes the application prevent intentional misuse?
Compatibility
include the ability to co-exist with other applications, and the ability
to interact with other applications.
Maintainability
Can the application be effectively modified after implementation to
meet changing needs?
Transferability Can the application be installed and used in another environment?
Sources: BABOK Guide V2 & BABOK Guide V3
11
2016 PM-BA WorkshopSCOPE MODELING – Context Diagram
Purpose
Scope models are used to describe the scope of analysis or the scope of a solution
and to define the boundaries.
ESTERNAL EVENTS
ACTING TO
EXTERNAL ENTITIES
MAY BE CONSIDERED
IF A RESPONSE IS
NEEDED
USE CASE DIAGRAMS
BUSINESS PROCESS
USEFULL TO MODEL THE SCOPE
Sources: BABOK Guide V2 & BABOK Guide V3
12
2016 PM-BA WorkshopUSE CASES AND SCENARIOS
Purpose
Scenarios and use cases are written to describe how an actor interacts with a
solution to accomplish one or more of that actor’s goals, or to respond to an event
Flow of Events
Describes what the actor and the system do during the execution of the scenario
or use case. Most use case descriptions will further break this down into a basic,
or primary flow (representing the shortest successful path that accomplishes the
goal of the actor) and a number of alternate flows that show more complex logic or
error handling. Sources: BABOK Guide V2 & BABOK Guide V3
13
2016 PM-BA WorkshopUSE CASES AND SCENARIOS
Sources: BABOK Guide V2 & BABOK Guide V3
It is used to show how end users interact with the solution.
It includes both a schema and a text description, called scenario.
Sign up for Member Account
Account Management
Nonmember
Use Case Title Sign up for a Member Account
PreconditionThe Nonmember does not already have a
Member Account
PostconditionThe Nonmember has a valid Member
Account
Main Scenario
1. This begins when the Nonmember
requests to sign up for a new Member
Account.
2. The System asks the Nonmember to
choose username and password.
3. The Nonmember provides username
and password.
4. The System validates the
Nonmember’s username and
password.
Use Case Scenario
14
2016 PM-BA Workshop
USER STORIES – Key Features
• A user story represents a small, concise statement of functionality or quality needed to deliver value to a specific stakeholder.
• User stories capture the needs of a specific stakeholder and enable teams to define features of value to a stakeholder using short, simple documentation.
• User story can serve as a basis for identifying needs and allow for the prioritizing, estimating, and planning of solution(s).
USER STORIES include:
• Who (Stakeholder): a user role or persona
• What (description): a necessary action, behavior, feature, or quality.
• Why (Benefit): the benefit or value received by the user when the story is implemented.
14
16
2016 PM-BA Workshop
LESSONS LEARNED
Purpose
The purpose of the lessons learned process is to compile and document
successes, opportunities for improvement, failures, and recommendations for
improving the performance of future projects or project phases.
Advantages
• Useful for identifying opportunities for process improvement.
• Can help build team morale after a difficult period.
Disadvantages
• All participants must be prepared to avoid any urge to assign blame during
these sessions or honest discussion may not occur.
• Participants may be reluctant to document and discuss problems
• May risk becoming a “gripe” session and improvement opportunities may be
neglected.
Sources: BABOK Guide V2 & BABOK Guide V3
18
Upcoming Events 2016
• PM&BA: Working on Requirements with LegoTM – 5th March 2016
• First Italy Chapter event free for members, with pay entrance for non members (20€) - Scheduled on Saturday morning!
• Happy Hours, not only in Milan! (Rome, Genova, Verona,…)
• GEI – Tests for Exam BABOK® V2 – 16th March
• Happy Hour Genova – 20th April
• CCBA/CBAP Study Groups – September (Webinar)
• Innovation Challenge 2016 – New Formula! May & July
• BARM 2016 (Rome Branch Main Event) – 8th June
• Happy Hour Verona – September
• BAWI 2016 (Annual Chapter Event) – 24th October
19
Jan Feb Mar Apr May Jun Jul Sep Opt Nov Dec
PMBA 5/3
Happy
Hour
Milan
4
GEIWebinar
16/3
Happy
Hour
Genova
20/4
Happy
Hour
Milan
3/5
Innovation
Bootcamp
May
BAWI
24/10
Happy
Hour
Milan
15/11
AGM
11/2
IIBA® Italy Chapter 2016,an agenda rich of events!
Happy
Hour
Verona
(Sep)
BARM
8/6
Innovation
Final Event
JulyStudy
Group
Webinar
(Sep)
20
Our Contacts
• Join us, contact us: you can participate to our initiatives
• www.italy.iiba.org
http://goo.gl/q5sYt
www.slideshare.net/IIBA-IT
https://twitter.com/iiba_italy
http://www.facebook.com/ItalyIIBA