Scribd
Upload
17 views48 pages

Webinar 7 BA Agile Best Practices Final

Uploaded by

dinhnguyenngoc
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views48 pages

Webinar 7 BA Agile Best Practices Final

Uploaded by

dinhnguyenngoc
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 48

7 Agile Best Practices for BA’s

Jiri Walek Clara Vincenc Cismaru


VP Product Management Product Manager
Agenda

01 02 03 04
How BA fits 7 Agile Conclusion Questions &
into Agile Best Practices Answers
+ Best Practices
+ Solutions to Challenges
 2004 Founded with Disruptive Vision
 2005 First Unified, 100% Browser-Based ALM
 10 Years Focus on Unlocking Synergies:
Full Traceability, Real-Time Collaboration, Intuitive UI
 10 Years Customer Satisfaction & Growth

250+ 2.5+M 200+ 15K


Registered
Fortune 1000
Deployments Users Extensions Community
Members
How BA fits into Agile
7 Agile Best Practices for BA’s
1
Specify Requirements
Progressively
WASTE
Progressive Requirement Specification

Requirements Backlog Product Documentation


Epics User Stories Component Specifications
Think Critical

Under Agile, technical debt piles up and is not addressed because the
business people will not see a problem until it’s far too late or, at
least, too expensive to fix it.

Agile forces developers to work on atomized, feature-level “user


stories” and developers are often disallowed to work on
improvements/defects/issues that can’t be related to short-term,
immediate business needs
Product Owner is Facilitator

http://www.scaledagileframework.com/
Right Tools
2
Evolve Planning & Prioritization
Prioritize Backlog Continuously
Evolving Roadmap 3-6 months
Heap vs Backlog

Focusing on continuous delivery has the effect of creating


an unmanageable defect backlog while developers work to
put something in front of the customer.
YES or NO ?
Transparency / Workflow
Multi-Dimensional Prioritization
Priority = Occurrence * Detection * Workaround * Severity
3
A Picture’s Worth 1000 Words
“We are visual creatures. When you doodle an image that captures the
essence of an idea, you not only remember it, but you also help other
people understand and act on it - which is generally the point of meetings
in the first place.”
- Tom Wujek

Studies show that people remember:

  
10% 20% 80%
of what they hear of what they read of what they see
4
Enhance Communication
Reduced Daily
feedback scrum
loop

Sprint
Involve review
Agile
customer
Communication
early

Sprint
Team retrospective
collaborati
on
Challenges
Use Tools for Real-time Collaboration
Think Widely

Customers

DevOps

Technology Sales
Operations
Early Validation
Process Plan Feedback

Dedicated Value Stream


(25% capacity)
5
Embrace Change Smartly
Eliminate Waste

1. Continuous Backlog Prioritization


2. Early and Frequent Product Review & Validation
3. No Heavy Up-front Specification
Impact Analysis

Large Data Scale


50k Requirements
20mil LoC
Regulatory Compliance

Demonstrate that the software units fulfill the


software specifications and do not contain
undesired functionality.
 Requirements are documented
 Verification Scenarios are
documented and results traceable
 Source code changes are verified
and traceable
Customers don’t know what they want …

They DO!
Architecture

Design & Refactor


- for extensibility
- for flexibility
Maintenance Paralysis

- Developers
- Maintainers

(c) http://www.projekt-inlive.de
Variants Management
Degree of Commonality and Variability

Common solutions Common and shared Common, shared and


only solutions only specific solutions
6
Quality is Queen
Verify Validate
You built You built
IT THE
RIGHT RIGHT THING
Acceptance criteria & test cases

Continuous integration / testing

SW V&V during each iteration

Maintain traceability

 Validation iteration
Traceability Reports
What is your schedule to update Polarion software?

84 % on latest major release

iOS 8 final score:


87% of users upgraded
Once per Major release 40
(31%) Less often 21 (16%)

Twice annually 23 (18%)


Every Service release 46
(35%)
Ensure Release Adoption

• Agile Release Train – same QA gateway for all releases


• Web technology - make it easy to update
• Backward Compatibility
7
Do Risk Management
Risk Management
Conclusion
7 Agile Best Practices for BA’s
Specify Requirements Progressively

Evolve Planning & Prioritization


A Picture’s Worth 1000 Words

Enhance Communication

Embrace Change Smartly

Quality is Queen
Do Risk Management
Questions
Next Steps
Visit www.polarion.com:
► Watch Product &Tutorial Videos

► Download FREE 30-Day Trial / Try Online

► Request Proof Of Concept (POC)


Thank you.

www.polarion.com
www.polarion.com

You might also like