Are you failing at being agile? #digitallabin

Slide 1

Slide 1 text

Are you failing at being agile? Antonio Perić-Mažar, Locastic 28.09.2019. - #digitallabin

Slide 2

Slide 2 text

Antonio Perić-Mažar CEO @ Locastic Co-founder @ Litto Co-founder @ Tinel Meetup Co-founder @ Blockada t: @antonioperic m: [email protected]

Slide 3

Slide 3 text

Locastic Helping clients create web and mobile apps since 2011 • UX/UI • Mobile apps • Web apps • Training & Consulting www.locastic.com @locastic

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

“We do a daily standup in the morning; we are an Agile shop”.

Slide 6

Slide 6 text

“We do a daily standup in the morning; we are an Agile shop”. - no, you are not

Slide 7

Slide 7 text

• Software development agency • 20+ employees • More than one project running at same time • Different clients, different locations of clients Context

Slide 8

Slide 8 text

We stared with the waterfall.

Slide 9

Slide 9 text

We stared with the waterfall. And we fall. Hard.

Slide 10

Slide 10 text

Let’s go AGILE!

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

Let’s do SCRUM!

Slide 13

Slide 13 text

Well, this is fun and ok, but still… results are better, but…

Slide 14

Slide 14 text

1st problem:  we focused to much on framework

Slide 15

Slide 15 text

Scrum is a great option when you’re a team at a software vendor with a clear focus to deliver a specific product.

Slide 16

Slide 16 text

Scrum is a great option when you’re a team at a software vendor with a clear focus to deliver a specific product. External dependencies (clients)

Slide 17

Slide 17 text

AGILE !== SCRUM

Slide 18

Slide 18 text

AGILE > SCRUM

Slide 19

Slide 19 text

If you are doing SCRUM, you are not Agile company, you need to have Agile mindset.

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

We cannot sell the waterfall and do it agile!

Slide 22

Slide 22 text

Ideal project: - time&materials - no budget - no deadlines - no/flexible scope

Slide 23

Slide 23 text

Ideal project: - time&materials - no budget - no deadlines - no/flexible scope doesn’t exist

Slide 24

Slide 24 text

• Flexible budget + Project idea • Fixed budget + Project idea • Flexible budget + Project specification (and/or wireframes/ prototypes) • Fixed budget + Project specification (and/or wireframes/prototypes). Type of projects

Slide 25

Slide 25 text

• Flexible budget + Project idea • Fixed budget + Project idea -> AVOID! • Flexible budget + Project specification (and/or wireframes/ prototypes) • Fixed budget + Project specification (and/or wireframes/prototypes). Type of projects

Slide 26

Slide 26 text

If the scope, the deadline and the price have already been set at the beginning, it no longer makes sense to try and implement an agile framework such as Scrum.

Slide 27

Slide 27 text

Time&Materials model

Slide 28

Slide 28 text

• Huge level of trust • Easily overcome as soon as one has completed an agile project together • Requires education of the client and huge level of empathy on both sides • Today is much easier to sell it then 5 years ago, it is almost a standard • Empathy, understanding and patience on both sides Time&Materials model

Slide 29

Slide 29 text

Clients still want estimates

Slide 30

Slide 30 text

Involve the project team in the acquisition phase as early as possible

Slide 31

Slide 31 text

UX/UI first development

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

#1 value Customer collaboration over contract negotiation

Slide 35

Slide 35 text

Forget the service provider role (and work as a team with your client) - add empathy

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

Product Owner

Slide 38

Slide 38 text

Implement one measure at a time

Slide 39

Slide 39 text

#2 value Individuals and interactions over processes and tools

Slide 40

Slide 40 text

#3 value Working software over comprehensive documentation

Slide 41

Slide 41 text

• It should be clear at first glance what feature the task is related to • Description of a task should always begin with its purpos • A task should always be written in a way that is relevant for the whole tea • A task should list all important steps for completing it • Criteria should be very specific and related to the task, and should contain real testable example • Each task should contain a direct link to a wireframe and/or design view Anatomy of a Task

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

#4 value Responding to change over following a plan

Slide 44

Slide 44 text

The Law of the customer an obsession with delivering value to customers as the be-all and end-all of the organization.

Slide 45

Slide 45 text

The Law of the small team a presumption that all work be carried out by small self -organizing teams, working in short cycles and focused on delivering value to customers—and

Slide 46

Slide 46 text

The Law of the network a continuing effort to obliterate bureaucracy and top-down hierarchy so that the firm operates as an interacting network of teams, all focused on working together to deliver increasing value to customers

Slide 47

Slide 47 text

#bestAdviceEver Stop being heroic command giver, and start being humble gardener

Slide 48

Slide 48 text

• People and project are more important then process (methodology) • Scrum is just a framework that we adjusted to ourself • It is a philosophy not a process • It is probably the best solution at the moment for chaotic systems • It is easy to learn in theory, but it is very hard to practice it, especially with external parties (clients) How we see Agile today

Slide 49

Slide 49 text

• Agile is way of thinking, and it should be integrated to each part of the team/company: • it should be a way of thinking • a way of writing the tasks • a way of signing the contracts • a way of doing business development • and etc. How we see Agile today

Slide 50

Slide 50 text

• it is good for organisation and task management • it delivers new features constantly, client can see the progress and client is more involved in entire process • usually clients are more happy • if everything is setup well, it is very easy to rotate team members Advantages

Slide 51

Slide 51 text

• client is part of development process, and software development is no longer strange thing for them • there is no bunch of documentation • entire team is more focuses on delivering high quality product Advantages

Slide 52

Slide 52 text

• It is very hard to get client on location all the time • Product owner role is very hard, and usually clients don’t have person who is ready to take that role • in this situation team need to have one more person who will do training and consulting to help client with assignments • Client almost always wants to know price and deadlines • in this case sometimes SCRUM/AGILE is not possible and it becomes just a show Disadvantages

Slide 53

Slide 53 text

• Sometimes clients don’t get the concepts of agile, as they are used in traditional processes • If team and client are not on the same location, it makes process slower • Client is usually more involved in the beginning • It is not for inexperienced teams Disadvantages

Slide 54

Slide 54 text

• Lean Development • Extreme programming, pair programming • BDD, TDD, DDD… • CI/CD • Automation of processes (testing, deploying, etc) Agile is not just SCRUM

Slide 55

Slide 55 text

Where we are going with agile today?

Slide 56

Slide 56 text

Moving to Kanban more!

Slide 57

Slide 57 text

Be Agile with Agile!

Slide 58

Slide 58 text

• increased number of releases • reduced number of bugs • better and more quality metrics per teams • design process are drastically improved • moral of teams and people is increasead • clients are more happy Results

Slide 59

Slide 59 text

“I’m sick of it. I can’t wait for the day when everyone realises how much of a fad-diet, religious-cult-inspired, money-making exercise it is for a group of consultants. I can’t wait for people to wake up to the fact that the only good parts of Agile are just basic common sense and don’t need a ‘manifesto’ or evangelists to support them.”. - the rant of Luke Halliwell some ten years ago