Program Analyst Days
/
10
Make an individual timetable, ticking off the talks in the programme that you plan to attend
24.05.2019 – First Day
| Section A (330 people) | Section B (300 people) | Section C (250 people) | Section D (100 people) | |
|
09:00
|
Registration, morning tea/coffee | |||
|
09:30
|
Opening ceremony | |||
|
10:00
10:40
|
|
Talk language:
Cases of non-effective using of analyst's skillsRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Facilitation of working meetings: creative and effectiveWorkshop (1h 30 min)
I'll go
Give feedback
|
|
|
10:55
11:35
|
Talk language:
Development games. Raiting analysts' skillsRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
The role of a Business Analyst in solving non-standard problems in complex projectsRegular Talk (40 min)
I'll go
Give feedback
|
|
|
|
11:50
12:30
|
|
Lunch. 1st shift
|
Talk language:
Storytelling in business communications (team building, promotion, negotiation, sales). StorybanksRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Why single document doesn't work for all stakeholdersRegular Talk (40 min)
I'll go
Give feedback
|
|
12:45
13:25
|
Talk language:
Tales from The Bank. How did the User Stories approach help usRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Requirements gathering in Data Science ProjectsRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Storytelling in business communications (team building, promotion, negotiation, sales). StorybanksWorkshop (1h 30 min)
I'll go
Give feedback
|
Talk language:
Evolution of the product development: analyst roleLightning Talk (20 min)
I'll go
Give feedback
Talk language:
Work of the analyst in the medical companyLightning Talk (20 min)
I'll go
Give feedback
|
|
13:40
14:20
|
Talk language:
Analysts horde. How to capture stakeholder's "Kozelsk" without casualtiesRegular Talk (40 min)
I'll go
Give feedback
|
Lunch. 2nd shift
|
Talk language:
Why do you need software. Drama in three partsRegular Talk (40 min)
I'll go
Give feedback
|
|
|
14:35
15:15
|
|
Talk language:
Analyst 2.0. How information that analyst owns impacts team motivationRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
System decomposition or "well, let it be integration subsystem!..."Regular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Integration and Void. Let's look inside the mocksLightning Talk (20 min)
I'll go
Give feedback
Talk language:
Non-standard approach foe development through testing. Practical caseLightning Talk (20 min)
I'll go
Give feedback
|
|
15:30
16:10
|
|
Talk language:
Сhecklist for describing system integration requirementsRegular Talk (40 min)
I'll go
Give feedback
|
|
Talk language:
Analyst's diary or terrible practices to write on gherkinLightning Talk (20 min)
I'll go
Give feedback
|
|
16:10
|
Coffee break | |||
|
16:40
17:20
|
|
Talk language:
How to deal with scope creep using concept statementRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Automation of business processes in constructionRegular Talk (40 min)
I'll go
Give feedback
|
|
|
17:35
18:15
|
|
|
Talk language:
Anti-crisis analyst: how to catch up the project and not overdo itRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Influence of the Company’s Strategy on Optimising of Business ProcessesRegular Talk (40 min)
I'll go
Give feedback
|
|
18:15
|
Analyst Days Party | |||
25.05.2019 – Second Day
| Section A (330 people) | Section B (300 people) | Section C (250 people) | |
|
09:30
|
Morning tea/coffee | ||
|
10:00
10:40
|
|
Talk language:
Learn to PLAY Business Analysis (workshop)Workshop (1h 30 min)
I'll go
Give feedback
|
Talk language:
The influence of analysts on the development of the companyRegular Talk (40 min)
I'll go
Give feedback
|
|
10:55
11:35
|
Talk language:
UX dashboard of dream. How to turn chaotic data into one beautiful dynamic screenRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
"Write-Simplify” - Requirements: how make it easier for understanding Lightning Talk (20 min)
I'll go
Give feedback
|
|
|
11:50
12:30
|
Talk language:
The evolution of the integration system in the internal developer portalRegular Talk (40 min)
I'll go
Give feedback
|
Lunch. 1st shift
|
Talk language:
Limitations as a source of inspiration. System engineering based on the ideas of inclusive designWorkshop (1h 30 min)
I'll go
Give feedback
|
|
12:45
13:25
|
|
|
|
|
13:40
14:20
|
Talk language:
Verify UI/UX hypothesis with Customer Journey Map toolLightning Talk (20 min)
I'll go
Give feedback
|
Lunch. 2nd shift
|
Talk language:
Requirements Management when Working with a Remote TeamRegular Talk (40 min)
I'll go
Give feedback
|
|
14:35
15:15
|
|
Talk language:
Use Case VS User Story. Select requirement specification techniquesRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Road from business customer to product ownerRegular Talk (40 min)
I'll go
Give feedback
|
|
15:30
16:10
|
|
|
Talk language:
10 advices about an analyst’s remote workLightning Talk (20 min)
I'll go
Give feedback
Talk language:
TM Forum API Model: purpose and reason to useLightning Talk (20 min)
I'll go
Give feedback
|
|
16:10
|
Coffee break | ||
|
16:40
17:20
|
Talk language:
Four rules for archaeologist: how to dig out an IT systemRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Immersion in a new domain, analyst checklistWorkshop (1h 30 min)
I'll go
Give feedback
|
Talk language:
Monitoring system: advanced set of technical metrics or a panorama of success?Regular Talk (40 min)
I'll go
Give feedback
|
|
17:35
18:15
|
Talk language:
The practice of architectural design of IT solutionsRegular Talk (40 min)
I'll go
Give feedback
|
Talk language:
Protected area where the product lives in peace with the state orderRegular Talk (40 min)
I'll go
Give feedback
|
|
|
18:15
|
Closing ceremony, award speakers, raffle prizes | ||