Rakuten Project dashboard
Rakuten Project dashboard
A dashboard to track you and your team's work.
A single page to help you and your team team stay on top of all the moving parts. Take a look around, then clear the sample tasks, projects, updates, and team members so you can get started with a fresh template.
Clear sample data
Not started
12 of 13
12 of 13
On-track
1 of 13
1 of 13
At risk
0 of 13
0 of 13
Completed
0 of 13
0 of 13
📊 Task tracker
Click on any card to view and update details. Click + New card to add tasks. Drag and drop cards to move tasks through the stages. Click the down arrow at the top of any stage to expand/collapse it.
Not started
Release schedules for new features, bug patches, and security vulnerability upgrades must be followed in order to meet the committed deadline
One of the comments from the customer - In spite of sharing required logs, engineering asks the customer for the calls and checks similar things on the call, which is frustrating for the customer.
One of the learning is that when we don't have the answer, we shouldn't take calls from customers unless we have a solid solution, majorly in the production issues
Engineering IST support - Sometimes we aren't sure what to respond to the customer in troubleshooting production issues. When there are production issues, it has been noticed that no one from engineering joined the call to understand the issue and made excuses about not being the right person to investigate the issue
Load testing test cases with larger databases are needed to incorporate in the Testing Suite
Product upgrade support matrix should be available on the YB documentation. I had a talk with the SDET team and shared the expectation, need to follow and get it done
Sometimes the US Support team and IST Support team need to be aligned when handling production issues, as the IST team works with the customer on Viber and sometimes if updates are not available US support team don’t have the updates. This is something issue at the customer end as well, as the customer expects everything to be handled through Viber, this is something we need to set the correct process.
Zendesk ticket updates - Need to educate the customer on providing details on the ticket instead of raising the ticket with a single line.
We have already communicated this to the customer multiple times however this is not yet followed properly
YB training - Since there are 3 new people joining the customer DBaaS team, we need to have high-level YB training scheduled and also need to give YB troubleshooting sessions. Rakuten is already running the internal KT but that is more specific to the Rakuten environment. This will help indirectly YB in avoiding getting involved in small issues in the Rakuten environment.
Start to share biweekly/monthly YB highlights on the issues, customer onboarding, current activities, and upcoming activities to give a clear picture on YB involvement with the multiple Rakuten DBaaS team and application teams
Start to continue on customer onboarding success stories, we have the initial draft of the presentation ready however we need to work more on this
Streamline/format the documentation with the proper templates so that we can move the existing documents
Establish an escalation policy for severity 1 issues
In-progress
At risk
Complete
Status
1
Not started
2
In-progress
3
At risk
4
Complete
There are no rows in this table
💬 Weekly stand-ups
What we’re working on this week
Who
Updates
There are no rows in this table
Tasks by owner
🤝 Project teams
To quickly color-code a team name, select the team name text from the teams list column, then choose a font and/or highlight color.
Teams
1
2
3
4
5
6
Team List
Engineering
Customer Success
Pre Sales/Solution Architecture
Support Leadership
Support
Account Leadership Team
There are no rows in this table
Team members
1
2
3
4
5
6
Full name
Team
Role
Account Leadership Team
Sr. Solution Architect
Customer Success
Sr. Technical Account Manager
Pre Sales/Solution Architecture
Sr. Director,ATS
Support
Support Engineer
Support
Support Engineer
Support Leadership
Support Manager
There are no rows in this table
No need to get fancy. Keep all your team notes organized in a single doc by duplicating this page for each meeting.
Clear sample data
Running Meeting Notes from Account Planning Cadences
Tuesday, February 7th,2023
Attendees:
@Vish Phaneendra
@Amol Bhoite
@Adhikarla Jagdish Rao
Discussion topics ←——— Pre Fill topics for discussion
Notes
@Amol Bhoite
@Adhikarla Jagdish Rao
@Adhikarla Jagdish Rao
@Vish Phaneendra
@Amol Bhoite
@Amol Bhoite
@Adhikarla Jagdish Rao
Tuesday, February 14th,2023
Attendees:
@Vish Phaneendra
@Amol Bhoite
@Adhikarla Jagdish Rao
@Kapil Maheshwari
@Yogesh Jadhav
@Mayur Parik
@Adhikarla Jagdish Rao
@Tyler Ramer
@Amol Bhoite
@Amol Bhoite
@Adhikarla Jagdish Rao
@Kapil Maheshwari
@Yogesh Jadhav
@Mayur Parik
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.