Role Pathable - Apollo Location

Charter Feature teams

Product Owner Davi Brasil Brazil

Scrum Master Romi Sayago Argentine
Developers
1- Frederico Meaia Brazil Dev lead
2- Arthur Pinheiro Brazil
3- Dyarlen Iber Italy
4- Nargis Suborna

QA
Manual QA Savita Dahake India

QA Auto

UX/Design Nargis Suborna India

Documentation
 TEAM N

Items
Sprint backlog no updated
Sprint backlog no prioritized

Open work items remain in previous sprints

The US & bugs don't have estimation

Artefacts
US does not have a good description and Acceptance Criteria
High estimations on US

Organize the Azure structure for Kanban projects

Migration to Azure

US, bugs, zendesk tickets were all over the place

Grooming session

Kanban Metrics

Retrospective and Stand up

Events
They don't have the Sprint review

Prioritezd tickets for Grooming session

Tickets with poor or no enough information to get the wrok done

Workload for the iteration is not transparent

Outdated tasks in the Board (Target Process)

Team
Estimation
They don’t have register the future PTOs or vacation days
DoD is not defined

Design US are not in our backlog

 Team does not have any metrics

Product Owners needs a bit of guidance about duties and

responsabilities
He needs to organized the requirements for the Team
Design priorities
PO
PO does not write all the user stories
The PO is not working ahead - creating the future user stories.
Looks like the PO is not committed with the team (Team say: PO is busy
because he has other teams)
 TEAM NEBULA

Action Items Status

reviewing and working with Team / PO In progress
Reviewing and working with Team/PO In progress
Reviewing with Davi & the team and move all of them to
current iteration Done

No estimation added on the stories or bugs To Do

Reviewing this with the PO In progress

To Do

In progress

In progress

Done

We are having these sessions 2 times a week because we Done

don't have a planning

To Do

Done
To Do
reviewing with PO / team

Review with Oli & Davi In Progess

To do

We have should have a raw estimation of the tickets before

going to the sprint backlog To Do

Done
Cosmos is the only team that estimates and the numbers are
crazy high, so hopefully with the Workshop this will improve
and also Nebula can start doing this right To Do
Team starting to use the vacation excel sheet In progress
Something to work with the PO To Do

Spoke with Adrian Pako In progress

 To Do

Product owners best practices workshop In progress

To Do
Working with PO In progress
To Do
To Do
Comments - Current status

We have weekly meetings with Davi to get this done

Planned Estimation Workshop

Most of the tickets are coming from other teams needs and
requirements to fix something so we nee to improve the detail
and scope of the work to be done

As we have a diferent structure that other teams, we are

grouping them by asociation

The remaining tasks are the Zendesk stories that are migrated
manually by me
I went trought each ticket to make sure that all the items sent
to Azure will be work and no deprecated US, bugs will be
added to our backlog

The team didn't do groomings before, so now we are having

these meetings, and learning the dinamyc at the same time/
We need to define the aproximated amount of tickets that we
can handle in a sprint timeframe in order to get a Velocity &
Capacity of the Team (Priority changes accordinly
Both teams agreed to have these meetings
We are waiting to get a complete develop so we can have a
review of this with all the teams.
We started to add this sessions, now we have to have those
prepared beforehand, so the dev's can start to see the tickets
before the grooming.
We need to define a strategy with the PO to get this filtered
before the dev's take these kind of tickets.

Sometimes the developers do a lot and this is not reflected on

the board
Sometimes the developers do a lot of work but this not
reflected on the board. Now in ADO this changed

The US will remain in nova backlog and we will have to drag

these top our backlog
Set up a weekly meeting
Role Pathable - Nova
Charter Feature teams Location
Product Derek Nickell
Manager USA
Product Owner Davi Brasil / Brazil PO of 2 Teams
Scrum Master Nibeth Mena BO
Developers
1- Foysal Ahamed (.75) Italy Dev Lead
2- Matheus Castro Brazil
3- John Nelson USA
4- Rezwan Niloy Italy
5- Ruither Borba Brazil
6- Andrew Deibel USA
7- Luiz Carlos Lopes Brazil

QA
Manual QA Dragos Tita (.5) Romania
Imran Ambekari India
QA Auto

UX/Design Adrian Pako Romania

Documentation

Other
 NOVA TE
Items
They have a good organizacion in Target process

Not all stories have an estimation

US has a good description and Acceptance Criteria

US does not havet a responsible person assigned in whole sprint

Artefacts
Internal bugs are not linked to respective US or feature

Team does not have a bug backlog

Team did not had the Grooming session

Sprint planning:
It is not clear what is the goals of the plannning
They don’t have the sprint backlog defined and prioritized
Not using team capacity and velocity
Events

Stand up are happening just Monday, Wednesday and Friday

Retrospective is happening like the Stand up

They don't have the Sprint review

They don't know the scope of grooming preview of the meeting

Workload for the iteration is not transparent

Team does not using the task board and update their task status
Team It is not clear at the end of the sprint what was the work planned versus
added

ESTIMATION - are not using any reference with time

They don’t have register the future PTOs or vacation days
Team needs to use DOR - DOD
 HE IS PART of ALL scrum events like: Stand up, sprint review,
retrospective, etc. and main dev stand up (Like SoS)
He is involved in the change priorities like regression bugs
Design priorities
PO
PO writes the user stories

The PO is working ahead - creating the future user stories and updating
the backlog
PO is VERY committed with the team!
 NOVA TEAM
Action Items Status
Done
Explain to team the significant of estimation and work with
them in the planning session To Do
reviewing and working with PO
PO needs to understand his responsabilities as PO of the
team To Do
Explain to team why we must use the field and work with
them in the planning session In progress
Explain to team the benefit of to link the bugs to respective
user story In progress

I reorganized the structure in Target process.

Now team has a bug backlog Done

reviewing and working with Team In progress

In progress

reviewing and working with PO / team

reviewing and working with team, we need to discuss and

change this To do

reviewing and working with team Done

reviewing and working with PO / team In progress
reviewing and working with PO
PO needs to prioritized the scope for the grooming Done

It is necessary in the planning session to have all items

assigned To Do

I am showing the board during the Stand up

In progress
I started to use the tags: Planned, Added work to difference
the work In progress
With all teams we need to define how we will work, if the SP
will have a reference time like 1 SP - 1 Day To Do
Team starting to use the vacation excel sheet In progress
It is needs to review across of team To Do
Working with PO Done
Done
Working with PO and Designer In progress
Follow up the INVEST method, create small stories and
testeable In progress

Done
Done
Comments - Current status

Still working on this - have all items assigned at the end

of the planning is very new for the team
QA is still forgetting to linked the new bugs to the
respective Feature and US

Team has a recurring meeting scheduled. But it's

happens every weeks
Team has a recurring meeting scheduled.
Right now: PO in charge of this session WHERE needs
some improves
Team needs to know why is important to use the team
capacity
QA is part of the planning

Team has a recurring meeting scheduled

Team has a recurring meeting scheduled and now is
working properly the SM is in charge of this
Agreement: We started to have the sprint review
PO is in charge of the session. He is sending to team
one day before the scope of grooming
 SCRUM EVENTS

Grooming Planning (2w)

Thursday Wednesday 10.30 EST

10.00 - 11.00 EST 1hr
NOVA

Wed 12pm EST /

Wed 12pm EST
1hr
APOLLO

Apollo needs to
change to other
day to have one
session every
week
 SCRUM EVENTS

Sprint Review & Retrospective (2w) Stand Ups

Tuesday 10.00 EST M-W-F

1hr at 9.40 am EST

Tuesday at 12.00 EST M- F

9 am EST
Story points Hours ( Dev +QA) Days T- shirt sizing
0.5 1 - 4 hours 0.5 Small
1 5 -7 hours 1 day Small
2 8 - 14 hours 2 Days Small - Medium
3 15 -22 hours 3 -4 days Small - Medium
5 23 - 30 hours 5 -6 days Medium - Large
8 31 - 40 hours 7 - 8 days Large -XL
13 (Should not have any --anything above an 8 must be broken down more)

Note.- We need to discuss with PM/ PO and decide

how we are going to handle the estimation across
the teams
 Developed To Deve
#User
Team Feature Status #Bugs Comments Feature
stories
Hydrid Public meeting
Attendee Column
NOVA

Matchmaking
Zoom dashboard
Maps
APOLLO

IN PROGRESS
 To Develop
Status #User stories Comments

Grooming

Grooming