Introducing 

Prezi AI.

Your new presentation assistant.

Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.

Loading…
Transcript

Ideas for Tribe planning and collaboration

Our Aim

Our Aim

We want to achieve that our tribe:

- Moves together as one ship

- Knows where we are heading

- Knows how fast we're moving

- Knows what's most important for both us and our customers

What do we want

In order for us to move in the same direction while creating an outcome with max. business value

1

Why does it matter?

Why does it matter

2

WE NEED A GUIDING STAR

Can be a vision like this...

"Deliver superior service through our solutions. Our people understand your needs and are committed to your success.'

This is just an example for what could be the F&T vision and guiding star

With values like these...

  • Customer Driven
  • Continuous improving
  • Performance Culture
  • Open and Honest

How we act to achieve this...

3

We care - we serve our customers with passion - we listen before making decisions- we do what we say we'll do - If we see a problem we fix it. We learn, develop, and improve every day

Our challenges

Our challenges

Lack focus on ROI

1

Not utilizing our AWS components

We have some fantastic new components on our shelf but we don't use them enough...

Freight Booking Component

Notification Component

Customer Component

Routes Component

Schedule Component

And more great components are on the way...

Expensive legacy systems

2

Expensive legacy systems

MyFreight

Info-Bridge

Phoenix Web

Create Booking

Select Route

Choose Unit Type

Including our new components we now have a multitude of systems that needs to be maintained and supported and we don't seem to have focus on getting enough return of our investment.

No common standard

3

... additional challenges

Unclear priorities - lack of direction

Multiple teams create components and it's unclear which team is responsible for what

What's the definition of a component?

No common standard. We create new tech debt every day

Components being build is not used in Phoenix nor for any of the API's (e.g. channel bookings via EDI, and the API for Turkish Agents to create bookings etc. etc.) So the challenge of supporting and maintaining all these solutions grows exponentially over time

The opportunities

Our opportunities

One common backlog above them all ->

OKR's and Epics

Common goals

1

Pros and Cons

Maximize Business Value - focus on highest priority in ALL teams

Data driven culture and alignment on priorities, move as one

Rethinking collaboration: freedom to pull high priority tasks

Both Technical and Business: Epics and OKR's

Pros and Cons

Scalable model for planning across tribe, teams and even EMT

We need to create new processes

We have to meet to collaborate and coordinate more

Continuously need to inspect, adapt and improve

Common WoW for scaling agile

Common WoW

2

Pros and Cons

Cross team collaboration with easy-to-use agile scaling model

Unified Way of Working: easy to navigate and boost across teams

Pick up speed and together remove blockers for momentum

Pros and cons

New processes needs to be established

We need to meet to collaborate better together - 15 minutes

Continuously need to inspect, adapt and improve

Don't break up HIGH performing semi cross-functional teams...

Freight Component Team

Co-located in Grimsby, UK: collaborate many times a day

Goal

2 times a week collaboration

Better to collaborate than restructure

Freight Squad

Co-located in Cph, DK: collaborate many times a day

Goal

... in order to follow Spotify rigidly...

Common future

Common future

3

Our journey there

  • Align with Rune, Tribe leads and PO's

  • Kick-off the future together in the tribe

  • Implement bit by bit, inspect and adapt often

  • Plan and manage the change e.g. using ADKAR:

Our journey there

Learn more about creating dynamic, engaging presentations with Prezi