Новицька Дар’я: Що робити, якщо Ваш проект божественно документований”, або “Документацiя на этапi iнiцiaцiї проекту

1. Дар'я Новицька, Project Manager
ЩО РОБИТИ, ЯКЩО ВАШ ПРОЕКТ
«БОЖЕСТВЕННО»
ДОКУМЕНТОВАНИЙ?
ДОКУМЕНТАЦІЯ НА СТАДІЇ ІНІЦІАЦІЇ ПРОЕКТУ
АБО

2. I.
II.
III.
IV.
Початкова фаза (concept phase)
Фаза розробки (development)
Реалізація (implementation)
Завершення (closure)
ЖИТТЄВИЙ ЦИКЛ ПРОЕКТУ

3. ПОЧАТКОВА ФАЗА CONCEPT PHASE
Ініціація (initiation)
Передконтрактна фаза (pre-sale)
Контрактування (sale)

4. ...we cannot wait that long. ...Therefore we would like to
begin development for iOS mobile IMMEDIATELY.
(С) PO OF PROJECT TARGET FOR IOS APP
ЧОМУ CONCEPT PHASE
БУВАЄ ОБДІЛЕНА УВАГОЮ?

5. ЦІНА ПОМИЛКИ
LOW
HIGH
Stakeholder Influence, risk, and uncertainty
Cost of changes
Project Time
Degree

6. БОЖЕСТВЕННО ДОКУМЕНТОВАНИЙ...

7. ЩО ВАЖЛИВО ВИЯВИТИ
Чого саме не вистачає?
Чому саме цого документу?
Навіщо він потрібен, взагалі?
Хто з команди має над ним працювати?
Як, та ким цей документ буде опрацьований?

8. ІДЕАЛЬНИЙ ПРОЕКТ: АРТЕФАКТИ
Стек документів

9. АРТЕФАКТИ ЗГІДНО З PMI
Функціональні вимоги до кінцевого продукту
Нефункціональні вимоги
Бізнес канвас проекту
Специфікація
Беклог

10. PRESALE
Цілі Очікуваний результат

11. СТЕК ДОКУМЕНТАЦІЇ
Специфікація до продукту v.1.0
Функціонільні вімоги оформлені як User Stories
Source файли надані Замовником

12. НА СТАРТІ ПРОЕКТУ
Project Road
Map
Sprint Planning
Meeting
Iterations
Milestones

13. 12/15/2015 12/16/2015 12/17/2015 12/18/2015
12/21/2015 12/22/2015 12/23/2015 12/24/2015 12/25/2015 12/26/2015
12/28/2015 12/29/2015 12/30/2015 1/4/2016
Wireframes
UX PHASE
Week 1: Review, Ideation
Week 2: Detalization
Wireframes
Week 3: Finalization
Summing up - Project Closure
Meet the project
Sketches
Wireframes

14. ЩОСЬ ПІШЛО НЕ ТАК?
Scope of RisksTeam Meeting Brainstorming

15. SCOPE OF RISKS
There were few cases when
third-party
API worked incorrectly, after
integration
with our system.
There is a hing chance that
feature
<example_name> will fail
because of
incorrect work of third party
API.
This may lead to incorrect work
of
developed <example_name>
feature
Cause Risk Impact

16. ЩОДО ЗМІН
Relax. Everything Changes!

17. CHANGE REQUEST FORM
ID
Creation
Date
Project
Version
Status Description Module
Previous
State
New State ETD
Comment
if CR was
rejected - required
reason of reject
v.1.0.0.CR1
Change logo
to bigger one
Login Screen
Link to Login
screen with old
logo
Not available yet
8 hours
(dev)
+ 2 hours
(QA)
Logo is too big
for small
Android devices
6/3/2016
v.1.0.0.CR2 6/3/2016
v.1.0.0.CR3 6/3/2016
v.1.0.0.CR4 6/3/2016
v.1.0.0.CR5 6/3/2016
Rejected
Waiting for
Dev Approve
Waiting for
QA Approve
Approved!
Done

18. РАЗОМ НАС БАГАТО!
Як коммуніціювати?

19. COMMUNICATION PLAN
What Who How When Follow Up
Kick-Off Meeting
Sales Manager +
Client + PM +
Technical Specialist
Skype Call 04.06.2016
Agenda
Summary email
Project Team
Meetings
Project Team + PM Face 2 Face 04.06.2016 Summary email
Monthly Report
Status Meetings
Project Team +
PM + PO
Skype Call 04.06.2016 Summary email
Project Status
Reports
PM Email 04.06.2016
Project status Report
Summary email

20. ОСТАННІЙ ШТРИХ
Project Business Canvas

21. Participants Goals Users Activities Deliverables
Risks Milestones Constraints Scope
PROJECT:
CREATED BY:
There is a lack of simple and easy for understanding tools for editing metadata.
PO wants to create light and clear application to offer iOS/Android smartphone users.MOTIVATION:
PROJECT END:
MetaData editing app
Daria Noviskaya, v.1.0
Note: list the team members,
stakeholders and third parties
involved into project. You can also
show dependencies.
Product Owner
Project Manager
Android Developer
Tech Leader
QA Specialist
Designer
Note: Identify possible future events
that could have a negative impact
on the project.
Note: List the key dates and
events that frame the overall
timeline of the project.
Note: Identify the limits and conditional requirements that
directly affect the deliverables, activities or project as a
whole.
Note: Indicate the breadth of the
product or service to be included for
consideration for this project,
including what is out of scope.
Note: indicate the primary
objectives of the project,
including success metrics.
Distinguish between program
goals in separate list of
necessary
1) Create a simple tool to
manage metadata
2) Offer users a tool with
clear and light interface
3) Make work with metadata
intuitive and easy
Note: list the users of product
or service as target groups or
segments. Also indicate more
specific information about
users, such as persona
names, if available.
* travelers
* bloggers
* users of social networks
(e.g. facebook, vk)
* users of photo-sharing
apps (e.g. instagram)
* ordinary users
* Project Manager
* Product Owner
* QA Specialist
* existing and new users
Note: List the concrete tasks
and actions the team will take
to reach the project goals.
* create design mock-ups
* develop a simple
click-through prototype
* click-through prototype
* sliced .psd files
* style guide
* hold the iteration planning
meeting, assign tasks
* plan and conduct tests
* iterations plan
* project road map
* bugfixes for iOS
* implement 'add metadata'
feature
* replicate iOS app for
Android
* set up Jenkins for Android
build
* tested iOS build
Note: Indicate the outcomes and
documents that will be shown to
stakeholders or to customers. This
doesn't include working documents,
project plans and similar.
Project end up with release of v.1.0
CORE TEAM
TARGET GROUPS PHASE I: CONCEPT AND DESIGN
PHASE II: PLANNING
PHASE III: DEVELOPMENT
FOR UX TESTING
STAKEHOLDERS
None
INTERESTED
MobiDev Company,
Project Team

22. Дар'я Новицька, PM MobiDev
d.novitskaya@mobidev.biz
ДЯКУЮ ЗА УВАГУ!
ПИТАННЯ?