Projects - from idea to realization. How are teams formed and what is the structure in a big company.

1. Development process
FFW
This presentation and its contents are property of FFW.

2. Miroslav Banov / Toni kolev
FFW
This presentation and its contents are property of FFW.

3. today’s agenda
01
02
03
04
05
Corporate structure
Waterfall vs Agile methodologies
Projects workflow
Tasks workflow
Version control

4. Corporate Structure
What is it to be part of a big company?

5. Corporate environment

6. Departments and teams
CEO
Open Source Project Management Front-End Quality Assurance Human ResourcesSystem Administration
T1 T2 T3 T1 T2 T3 T1 T2 T3

7. Waterfall vs Agile
Pros and Cons

8. Waterfall
model

9. Schedule

11. Scrum
practices

12. Scrum Roles
who is who

13. Activities

14. Product backlog

15. Sprint characteristics

16. Sprint planning

17. Product owner

18. Product owner responsibilities

19. Scrum Master responsibilities

20. Sprint lifecycle

21. Projects
from idea to realisation

22. Business needs
tender and requirements

23. Sales and legal procedure
offer and contract

24. Design and UX team
wireframes, design and prototype

25. Technical leader
architecture and technical description

26. Product/project owner
create features and backlog

27. Team
groom backlog and give estimates

28. Task workflow
how teams manage to work synchronously

29. Task is assigned
Comprehending the task
As a consumer, I want shopping cart
functionality to easily purchase items online.

30. Set up
environment

31. Implement

32. Documentation

33. (As far as I’m concerned)

34. Tech leader
takes over

35. Code can
be scary

36. Hand it over
to QA

37. Works

38. Or not…

39. OK now it’s done.

40. We forgot about
UAT!

41. Version control
You need it for serious development.

42. Branches of
development

43. When was a bug
introduced?