Download pptx - Smidig arkitektur

Transcript
Page 1: Smidig arkitektur

Johannes BrodwallChief Scientist

Smidigarkitektur

Page 2: Smidig arkitektur
Page 3: Smidig arkitektur

“How do you start a project and achieve

flexibility at the beginning?”

Page 4: Smidig arkitektur

“How do you {start a project} and achieve

flexibility at the beginning?”

Page 5: Smidig arkitektur

Keep it simple

Defer commitment

Inspect and adapt

It depends

Page 6: Smidig arkitektur

5 tools

Page 7: Smidig arkitektur

1. Discuss the problem

2. Describe the usage

3. Pick the technologies

4. Plan the show

5. Create the software

Page 8: Smidig arkitektur

When

Page 9: Smidig arkitektur

Monday Tuesday Wednesday Thursday Friday

Goal,Stakeholders

Dev baseline Dev baselineReview usage

Define progress,Stories

Wrap up docsDev baseline

Lunch Lunch Lunch Lunch Lunch

Look at what’s going on today

Stakeholder,Usage

Usage review,Context,Domain,Deployment

Refine models

Review,Retrospective

Typical plan for kickoff

Page 10: Smidig arkitektur

Discuss the problem

Page 11: Smidig arkitektur

The problem:

“A program to assign a worker to a client”

Page 12: Smidig arkitektur

The problem:

“A program to assign a worker to a client”

(yes, it’s unclear!)

Page 13: Smidig arkitektur

Form groups of 3 (or 2)

You will have five minutes to discuss

Page 14: Smidig arkitektur

For some user/stakeholder

Who wants to achive some goal

The name of the system

Is a type of system

Which lets them perform some operation(s).

Unlike most compelling alternative

This gives them some advantages.

Page 15: Smidig arkitektur

For workers

Who wants to get paid for good fun work

The Awesome work system

Is a digitial pimping system

Which matchers worker with a client.

Unlike the Excel file we’re using now

This automateted, online, easy to use and .

Page 16: Smidig arkitektur

Who?

Page 17: Smidig arkitektur

Who?# Clients do ??? every ??? via ???

# Dispatchers do ??? every ??? via ???

# Workers do ??? every ??? via ???

# Building Managers do ??? every ??? via ???

Page 18: Smidig arkitektur

Who?Tens of Clients sign up for service a few times every year

via meetings

Around 20 Dispatchers assign worker teams to maintainance tasks all the time via specialized application

Several hundred Workers accept tasks and confirm tasks a few times per day via mobile

Hundreds of Building Managers order maintenance tasks for their buildings every few days via web

Page 19: Smidig arkitektur

Who else?Payroll

Page 20: Smidig arkitektur

Describe the usage

Page 21: Smidig arkitektur

1. Need: Someone identifies a need

2. Trigger: Someone does something with the system

3. The system responds in some way

4. …

5. …

6. The goal has been fulfilled

Page 22: Smidig arkitektur

1. Building manager has works that needs done (e.g. change mats)1. Alternative: Periodic trigger

2. Building manager register works request on web site

3. Dispatcher lists unhandled work orders1. Alternative: Dispatcher filters, searches and sorts work orders

4. Dispatcher displays work order

5. Dispatcher assign tasks to workers based on skills registered in training system

6. Worker get notified of task on their mobile

7. Worker acknowledges task1. Alternative: If worker rejects task, system marks it as unassigned and

alerts dispatcher

8. Worker performs task

9. Worker registers the task as done

10. Worker registers time and materials spent on task on mobile

11. System notifies payroll of time spent

12. System submits invoicing data to accounting system

13. Building is in great shape!

Page 23: Smidig arkitektur

Worker

Mobile

Server

Payroll

Personell

Accounting

Dispatcher

Building manager

Page 24: Smidig arkitektur

Worker

Mobile

Server

Payroll

Personell

Accounting

Dispatcher

Building manager

Page 25: Smidig arkitektur

Pick the technologies

Page 26: Smidig arkitektur

Constraints:• Interact per user

• Portability• Supported platform

Page 27: Smidig arkitektur

Example:• Dispatcher: ____

• Building manager: ____• Worker: ____

• Supported platform: Java stack

Page 28: Smidig arkitektur

Example:• Dispatcher: Web or desktop

• Building manager: Web or any mobile• Worker: Provided mobile

• Supported platform: Java stack

Page 29: Smidig arkitektur

Example:• Dispatcher: “HTML5”

• Building manager: Responsive web• Worker: Android

• Supported platform: Java stack

Page 30: Smidig arkitektur

Example:• Dispatcher: Responsive web SPA

• Building manager: Responsive web SPA

• Worker: Responsive web SPA

• Supported platform: Java stack

Page 31: Smidig arkitektur

Frameworks:• What can the team support

• Max one: Project risk or tech risk

Page 32: Smidig arkitektur

Example risky project:• New team

• New supplier• New domain

• New codebase

Page 33: Smidig arkitektur

Example risky tech:• New database system

• New framework• New programming

language

Page 34: Smidig arkitektur

Plan the show

Page 35: Smidig arkitektur

1. Building manager has works that needs done (e.g. change mats)1. Alternative: Periodic trigger

2. Building manager register work order on web site

3. Dispatcher lists unhandled work orders1. Alternative: Dispatcher filters, searches and sorts work orders

4. Dispatcher displays work order

5. Dispatcher assign tasks to workers based on skills registered in training system

6. Worker get notified of task on their mobile

7. Worker acknowledges task1. Alternative: If worker rejects task, system marks it as unassigned and

alerts dispatcher

8. Worker performs task

9. Worker registers the task as done

10. Worker registers time and materials spent on task on mobile

11. System notifies payroll of time spent

12. System submits invoicing data to accounting system

13. Building is in great shape!

Page 36: Smidig arkitektur

Stories

0. (Mock work orders)

1. Complete list of work orders

2. Simple work order filter

3. Placeholder display work order

4. Placeholder assign task

Page 37: Smidig arkitektur

Demo script

Page 38: Smidig arkitektur

1. Preconditions

2. Start up the system

3. What do you see?

4. Activate a function

5. What do you see?

6. Activate variations of function

7. Thus we demonstrate that we have delivered x

Page 39: Smidig arkitektur

Example: Dispatch a task

1. Faked: Building manager registers a work order

2. Dispatcher “logs into” web admin at http://test.workers.com/admin

3. Dispatcher sees a list of missions (future: sort, filter list)

4. Dispatcher selects a mission

5. Mission will display the type of tasks associated with the mission type

6. Dispatcher clicks a task

7. Application lists all the workers that can be assigned to the task (for now, all workers are listed)

8. Dispatcher selects a worker

9. Dispatcher is returned to mission screen and the worker is listed next to the task

Page 40: Smidig arkitektur

Stories – sprint 2

1. Polished list of work orders

2. Complete display work order

3. (Placeholder worker import)

4. Simple assign task

Page 41: Smidig arkitektur

Create the software

Page 42: Smidig arkitektur

Example:• Feature: Dispatch task

• New codebase• 5 developers

Page 43: Smidig arkitektur

Solo programming

Page 44: Smidig arkitektur

Solo programming• Integration issues

• Inconsistent coding• Merge conflicts

Page 45: Smidig arkitektur

Mob programming

Page 46: Smidig arkitektur

Pair programming

Page 47: Smidig arkitektur

Resource utilization

vs

Knowledge sharing

Page 48: Smidig arkitektur

5 tools

Page 49: Smidig arkitektur

1. Discuss the problem

2. Describe the usage

3. Pick the technologies

4. Plan the show

5. Create the software

Page 50: Smidig arkitektur

1. Describe stakeholders

2. Usage flow => context diagram

3. Use technologies you know

4. Demo script

5. Mob programming

Page 51: Smidig arkitektur

Conclusion:

Page 52: Smidig arkitektur

When you return:Create a elevator pitchwith your

customerCreate a context diagram

Create a demo script for next sprint