POLITECHNIKA WARSZAWSKA AGILE. GAME OVER”.okulewiczm/downloads/io/... · clarified by business...
Transcript of POLITECHNIKA WARSZAWSKA AGILE. GAME OVER”.okulewiczm/downloads/io/... · clarified by business...
© Copyright 2019 Netcompany. All rights reserved.
Date:Version:Author:Contact:
AGILE. GAME „OVER”.GAME OF IDEAS IN AGILE PROJECTS
POLITECHNIKA WARSZAWSKA
22.11.20191.0Jakub [email protected]
.
2
Kuba
• 6 years of professional experience in IT (3 companies, 8 projects)
• certified Java Professional and Scrum Master (scrum.org), DevOps and Agile practicioner
• I work for Netcompany, and I’m representing the company here
• currently manager in the clarification phase of Digital Post project for Denmark
• member of Space for Dream association
3
NETCOMPANY
Netcompany is the fastest growing and most successful IT services company in the Nordics, aiming to become a Northern European market leader.
We are committed to lead the way showing how digital transformation can create strong, sustainable societies, successful companies and better lives for all of us.
Netcompany was founded in 2000.
2bnRevenue (DKK) in 2018
+20%Average revenue growth for +10 years
6Countries of operation
+2000No. of employees year-end 2018
.
4
Netcompany – Meet Your Employer Event
Kiedy? Tuesday, Nov 26th, 11:00-18:00
Gdzie? Puławska 182, Warsaw, Netcompany office
Po co?
11:00 - 11:30 Morning coffee11:30 - 13:00 Scrum in practice by Adam Stankowski, Senior Consultant13:00 - 13:30 Lunch13:30 - 14:30 How to develop a successful IT career: Netcompany approach by Steffen14:30 - 15:00 Office tour15:00 - 16:30 Functional programming in Java by Marcin Czarnak Senior Consultant16:30 - 18:00 Beer & Pizza
Register here:
https://www.netcompany.com/pl/events/2019/PL-Meet-Your-Employer
.
5
And You?
• What year of university are you in?
• Do you have any experience in IT?
• Do you know Scrum basics?
• Do you know Agile basics?
.
6
Which option do you prefer?
1. We’ll finish at 13:40 (the lecture will take 1h 25min), no breaks
2. Brake in the middle and the lecture split into two parts:
• 12:15 – 13:00
• 13:10 – 13:55
No matter what is your choice do not hesitate to come to me after the lectureand talk, if only you need ;)
.
8
Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it.Through this work we have come to value:
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
https://agilemanifesto.org/
.
9
Principles behind the Agile Manifesto
12
.
11
CASE STUDYYour Hospital Online
.
12
Our company: Poliviera
• Founded by students of Warsaw University of Technology at Riviera academic in 2012
• Phenomenon on a national scale
• International consulting company specializing in software development for public and private sector clients
• Leading technologies: Java, .NET
.
13
Case study: Your Hospital Online
• The Ministry of Health announces a tender for a national registration system for medical visits via the Internet: Your Hospital Online
• Supported facilities: all hospitals and public clinics in Poland
• Goal: to increase the quality of medical services and the level of patient satisfaction
• Users:
• Patients - booking and canceling visits to doctors, online consultation, viewing visit history and medicaltest results, online prescriptions, assessing patient satisfaction
• Doctors - online consultations, online prescriptions, recommendations for patients
• Local administration - management of appointment schedules, patient and physician data entry, offline patient registration
• Central administration - monitoring, collective data analysis, technical support
Patient
Patient
Patient
PhysicianLocal
Administrator
CentralAdministrator
Physician
.
15
Phase 0: Before the project starts…
• Preparation of the tender offer
• Business solution proposal
• Technical analysis
• What competencies do we need?
• How many people do we need?
• What will the client cooperation process look like?
• How soon can we get it?
• How much does it cost?
• People - preparation for work in case of winning
• Securing the allocation to the project
.
16
• The process is extended by another month
• Keeping people allocated to the project becomes cumbersome
• Appeal denied. Get Ready!
Yes! Our company Poliviera has won!
• The competition submits an appeal
.
17
Project phases – does it look ok?
.
18
What does Agile Manifest say?
(1)
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
(2)
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
(3)
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
.
19
Project timeline
22-11-2019 22-03-202101-01-2020 01-04-2020 01-07-2020 01-10-2020 01-01-2021
MAINTENANCECLARIFICATION (OPTIONAL) POC AGILE DEVELOPMENT
Today
04-02-2020
MILESTONE 1
12-06-2020
MILESTONE 2
14-10-2020
MILESTONE 3
.
20
Phase 1: Clarification
1. Business teams clarify the requirements with the client and prepare documentation for developers.
2. Project management prepares the structure of the organization for the next phases.
3. There is no point in involving technical teams yet - this is just a clarification phase that is short. It will be much more effective to start development work when the requirements are clarified by business teams.
4. Good cooperation with the client is important from the very beginning. Therefore, it is recommended to ensure customer representatives can use video conferencing (e.g. Skype, MS Teams), so that business teams can communicate freely with the customer regardless of where they are. Thanks to today's technology, we can easily locate colleagues from business teams in any office (even in different countries). However, it is important to follow certain rules of agile remote communication.
22-11-2019 22-03-202101-01-2020 01-04-2020 01-07-2020 01-10-2020 01-01-2021
MAINTENANCECLARIFICATION (OPTIONAL) POC AGILE DEVELOPMENT
Today
04-02-2020
MILESTONE 1
12-06-2020
MILESTONE 2
14-10-2020
MILESTONE 3
.
21
What does Agile Manifest say?
(4)
Business people and developers must work together daily throughout the project.
(5)
Build projects around motivated individuals.Give them the environment and support they need,
and trust them to get the job done.
(6)
The most efficient and effective method ofconveying information to and within a development
team is face-to-face conversation.
.
22
Phase 1: Clarification
1. Business teams clarify the requirements with the client and prepare documentation for developers.
2. Project management prepares the structure of the organization for the next phases.
3. There is no point in involving technical teams yet - this is just a clarification phase that is short. It will be much more effective to start development work when the requirements are clarified by business teams. What about infrastrcture, DevOps, security setup?
4. Good cooperation with the client is important from the very beginning. Therefore, it is recommended to ensure customer representatives can use video conferencing (e.g. Skype, MS Teams), so that business teams can communicate freely with the customer regardless of where they are. Thanks to today's technology, we can easily locate colleagues from business teams in any office (even in different countries). However, it is important to follow certain rules of agile remote communication.
23
Clarification phase
Architecture
DevOps
Infrastructure
Workshops
with the client
Documenting
requirements
Securing exit
criteria
Education
Onboarding
procedures
Defining
organizational
structure
Project
management
tools setup
.
24
Phase 2&3: Agile development
22-11-2019 22-03-202101-01-2020 01-04-2020 01-07-2020 01-10-2020 01-01-2021
MAINTENANCECLARIFICATION (OPTIONAL) POC AGILE DEVELOPMENT
Today
04-02-2020
MILESTONE 1
12-06-2020
MILESTONE 2
14-10-2020
MILESTONE 3
.
25
Principles behind the Agile Manifesto
(7)
Working software is the primary measure of progress.
(8)
The best architectures, requirements, and designsemerge from self-organizing teams.
(9)
Continuous attention to technical excellenceand good design enhances agility.
.
27
• What are roles in Scrum?
• What Scrum Evants do you know?
• What Scrum Artifacts do you know?
Scrum
Product Owner
Scrum Master Team Member
Team Member
Customer
Stakeholder
Stakeholder
User
Team Member
Team Member
Team Member
Team Member
Scrum TeamStakeholders
.
31
Principles behind the Agile Manifesto
(10) Agile processes promote sustainable development.The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
(11) At regular intervals, the team reflects on howto become more effective, then tunes and adjusts
its behavior accordingly.
.
3232
Kanban
1. Flow visualization
2. Limiting work in progress
3. Flow management
4. Policy transparency
5. Effective feedback channels
6. Kaizen - continuous improvement
.
33
Principles behind the Agile Manifesto
(12)
Simplicity - the art of maximizing the amount of work not done - is essential.
.
34
Phase 2&3: Agile development
Goal
Continuous delivery of working, valuable and high quality software:
1. by self-organizing teams of motivated people regularly tuning their way of working to increase productivity and overall team satisfaction
2. in close cooperation with the client
3. taking into account changing priorities (but also contractual arrangements)
4. while minimizing the amount of work needed
22-11-2019 22-03-202101-01-2020 01-04-2020 01-07-2020 01-10-2020 01-01-2021
MAINTENANCECLARIFICATION (OPTIONAL) POC AGILE DEVELOPMENT
Today
04-02-2020
MILESTONE 1
12-06-2020
MILESTONE 2
14-10-2020
MILESTONE 3
.
35
Organizational structure
• The increase in the number of people in the project implies the need to establish a transparent organization structure, including the way development teams work
• Development Team in Scrum should consists of 3 to 9 people (optimally 5-7)
• There are no hard limits in Kanban, but the 5-7 range will also work
.
36
Your Hospital Online – 7 consultants
Product OwnerIT Projects Manager
Scrum MasterProject Manager
Team Member
Team MemberTester
Team Member
Team MemberTech Lead
Team Member
Team MemberDevOps
StakeholderDomain Expert
StakeholderProject Manager
UserAdministrator
UserPatient
.
37
Your Hospital Online – 16 consultants
Product Owner
StakeholderStakeholder
Scrum Master Team Member
Team Member
Team Member
Team Member
Team MemberUX Designer
Team MemberOps
Scrum Master
Team Member
Team MemberTester
Team MemberTeam Member
Tech Lead
Team MemberMobile Apps Dev
Team MemberDevOps
Project Manager
Team MemberArchitect
StakeholderProject Manager
UserPatient
UserAdministrator
StakeholderDomain Expert
Team Member
.
38
Your Hospital Online – 29 consultants
Product Owner
Stakeholder
Stakeholder
Scrum Master Team Member
Team Member
Team Member
Team Member
Team MemberUX Designer
Team MemberOps
Scrum Master
Team Member
Team MemberTester
Team Member Team MemberTech Lead
Team MemberMobile Apps Dev
Team MemberDevOps
Project Manager
Team MemberArchitect
StakeholderProject Manager
UserPatient
UserAdministrator
StakeholderDomain Expert
Team Member
Operations Manager
Team Member
Team MemberTester
Team Member
Team MemberTech Lead
Team MemberMobile Apps Dev
Team MemberDevOps
Scrum Master
Team Member
Team MemberOps
Team MemberArchitect
Managing Architect
Team Member
StakeholderDomain Expert
Product Owner
Product ManagerStakeholder
Domain Expert
UserDoctor
Team MemberDomain Expert
.
39
Scaling Scrum
For larger projects (around 40+), it's a good idea to scale Scrum to introduce organizational order. We don't have to reinvent the wheel. We have several proven models to choose from:Nexus
• LeSS
• Scrum at Scale
• SAFe
• Model Spotify
.
40
More people = higher complexity
1 + 1 = 2
1 + 1 < 2
X
.
41
Final project release
• Customer approval needed
• Good documentation
• Transfer of the project to a maintenance team
• Party!
.
42
• Gradual decrease in project allocation
• Bug fixing, sometimes development of minor functionalities
Phase 4: Maintenance22-11-2019 22-03-2021
01-01-2020 01-04-2020 01-07-2020 01-10-2020 01-01-2021
MAINTENANCECLARIFICATION (OPTIONAL) POC AGILE DEVELOPMENT
Today
04-02-2020
MILESTONE 1
12-06-2020
MILESTONE 2
14-10-2020
MILESTONE 3
.
43
What are key Agile values?
Simplicity
Open mind
People
45
Q/A