Доклад посвящен вопросам разработки требований в проектах Business process automation и Research and development. На примере реальных кейсов будут рассмотрены инструменты и практики, позволяющие повысить эффективность процесса разработки требований, и снизить проектные риски

1. Разработка требований и управление
рисками в проектах BPA и R&D
Роман Кравченко
482.solutions

2. Spoiler

3. Project Manager @ITC R&D company
Co-Founder, Chief Technology Officer @Agri Eye startup
@482.solutions
Chief Technology Officer
@482.labs
About Me

4. About our Team

5. Internet of
Things
Data Science Big Data
Machine Learning
Strategic Directions

6. Research and developmentBusiness process automation
BPA vs R&D

7. Just Listen!

8. 1x $ 3X $
Software development vs Magic Box development

9. What we build?

10. “In product development, the
minimum viable product is the
product with the highest
return on investment versus
risk” [Wikipedia]
MVP: Minimum Viable Product

11. 1. A condition or capability needed by a user to solve a problem or achieve an
objective.
2. A condition or capability that must be met or possessed by a system or
system component to satisfy a contract, standard, specification, or other
formally imposed document.
3. A documented representation of a condition or capability as in 1 or 2.
[IEEE Standard Glossary of Software Engineering Terminology]
Requirements

12. The SRS is a specification for a particular software product, program, or set
of programs that performs certain functions in a specific environment.
[830-1998 — IEEE Recommended Practice for Software Requirements Specifications]
Software Requirements Specification (SRS)

13. Business
Requirements
User Requirements
Functional/System Requirements
Non-Functional Requirements
SRS Levels

14. Functional Requirements Non-Functional Requirements
Business Requirements
Vision and Scope
Document
User Requirements
Use Requirements Document
System Requirements Functional Requirements
Business Rules
Quality Attributes
External Interfaces
Constraints
Software Requirements Specification
SRS Model

15. Users
BA
Developers
QA
Technical Writer
PMCustomers
Lawyers
Engineers
Sales
“An individual, group, or organization, who may affect, be affected by, or perceive itself to
be affected by a decision, activity, or outcome of a project”
[Project Management Institute]
Requirements & Stakeholders

16. Requirements
Engineering
Requirements Development
Elicitation
SRS Model
Requirements Management
Analysis Specification Validation

17. Ninety-ninety rule [Tom Cargill, Bell Labs]

18. Last Edits
Project Risk
Finished Product Final Version of
Finished Product
+ =
x
[30-50%]*x
Requirements
Errors = 85%

19. Error Fix Cost
=1$ =1$+3$ =100$

20. Product Development: Cost & Risk

21. Change happens

22. Requirements development Tools

23. Requirements development tools
Elicitation Analysis Specification

24. Requirements development tools

25. MVP: Feature List
difficult
easy
not importantimportant
MVP

26. 1x $ 3X $
Big Challenge

27. roman@482.solutions
Have an idea?
romankrav4