Udacity Nanodegree Product Manager - Project. Development blue print for agile software development.

1. DOORDASH
Project Blue Print
Product Manager: Benjamin Hülsen

2. Blueprint

3. Project Blueprint

4. Preperation

5. Sprint Meeting Preparation
Sprint Goal
Sprint Backlog
Sprint Prioritization Logic
1
2
3
4
5
Remote conrtrolling the robot
These are the key features to move the drone through the city.
As an operator I want to be able to take over control of the drone, so I can manually navigate it.
As an operator I need live video streaming, so I see where the drone is driving.
The drone needs GPS localization, so it can easily been found.
The Operating Software must collect navigation data, so the autonomous driving KI can be improved.
As an operator I need to be able to remotely reset the drone, as a first major error fix attempt.

6. User Story 1
User Story
Acceptance
Criteria
Assumptions
As a control center team member, I need to immediatly see the exact situation the
robot is in, via live video streaming.
A logged in user can find the newly added feature from each drone information
panel.
4 video streams parallel: front, back(will be changeable to GPS view), left, right.
Videos are recorded and saved in the cloud for later analysation.
If connection fails, a reboot should build a better connection.
Product is available in U.S only and the MVP will be launched in English only
The video stream lack has to be < 0.1s, 60 fps, resolution: 2160p, codec: H.265.

7. User Story 1
User Story
Design
As a control center team member, I need to immediatly see the exact situation the
robot is in, via live video streaming.
Operator: BenCologne
Front
Left
Right
Carl 133

8. User Story 2
User Story
Acceptance
Criteria
Assumptions
As a control center team member, I need to alway see the exact position of the
robot, via GPS localization.
A logged in user can find the newly added feature from the home screen.
In the 4 video streams panel: the back view can be switched to GPS view.
Tracking is recorded and saved in the cloud for later analysation.
Product is available in U.S only and the MVP will be launched in English only
The signal lack has to be < 0.08s, accuracy by 1 sqm
Every drone in control of the user has its own GPS panel/stream.

9. User Story 2
User Story
Design
As a control center team member, I need to immediatly see the exact situation the
robot is in, via live video streaming.
Operator: BenCologne
Charging 82%
Charging 56%
Charging 23%
Trinity
Alpha
Max_B
John 8 Omega
Eve 357 Skywalker
Flubber
Neo 5Eve 553
Carl 133 John 875 John 2223
Frank 11
John 13
Cookie
Arrival
Caution Caution
Caution

10. API

11. DoorDash API
by developers.google.com/maps
Based on the API
documentation how
would you update your
solution and design?
Are there any details that
you want to discuss with
engineering to refine
solution and/or determine
feasibility?
• The service does not return detailed route information.
Combinig travel mode walking + bicycling and traffic_model: best_guess +
pessimistic for reliable time calculation.
• Review the usage and billing page for details on the quotas and pricing set
for the Directions API.
• Use of the Directions API must be in accordance with the API policies.
• Use https over http.
• Caution: Requests using traffic information are billed at a higher rate.
Do we need traffic information? How do we limit costs?
• To use the Directions API, you must first enable the API and obtain the
proper authentication credentials.
• What client do we use? (python / java / js / go?)

12. Reprioritize

13. Issue 1
Landing Page loading too slow
Determine criticality to
prioritize issue
Next Step
Additional steps
• try it myself
• read bug ticket
• read customer feedback
• compare loading time to acceptance criteria
I would reprioritize to 2 since the Page is working and the delay not critical.
• Talk to QA: An issue on all systems? Sice when? Ask for suggested fix.
• Prepare Jira ticket for next sprint
Trying to figure out what happend and how to avoid it in the future.
• Together with the developers I would update the definition of done to
ensure the loading time will be checked regulary and will not drop again.
(Testing loading time for each featurea added)

14. Issue 2
Misaligned in the Profile Settings
Determine criticality to
prioritize issue
Next Step
• As technical issue the bug has a prio of 4 - low.
• Relevance for most user is prio 4 - low, since they will not visit the panal.
I would prioritize to 3 - normal. The options panal looks broken and the
customer might lose trust in the functionality, our quality or security.
• Let UI and UX designer check and update the screens.
• Prepare Jira ticket for an upcoming sprint

15. Issue 3
Email from Customer Service Manager
Determine criticality to
prioritize issue
Next Step
Sample Email Response
• Its frustrating for the customer. 12h is failing acceptance criteria by 900%
• It takes lots of our human rescources.
• Depending on the total number, lots of customers are affected - 1.4%
It is very critical - prioriziation 1.
• Freeze current sprint.
• Emergency meeting with devs and QA.
• Make a plan to handle the situation right now and how to fix it.
Dear XY (Customer Service Manager),
we are aware of the importance of this issue. We have shifted all our
rescource to solve the problem. For now please do yz, while we do the work
around zy. I will keep you updated of our progress.
Please let me know if you have more critical issues.
Best regards

16. Difficulties

17. Situation 1
Respond to CEO or GM’s request via email
Assessment and result
Sample Email Response
• one day before regular review - I will negotiate and invite to official review
• inform devs and QA
• as PM I prepare for the event using storytelling and sync with devs about
the presented features
• as a scrum team we produce shippable features after each sprint, so a
review in front of the CEO/ GM at this time is not much of a problem
Dear XY (CEO/GM ),
we will be glad to present you our work. I would suggest you to join our
regular review on (one day later). That way we can keep our timetable and
dont lose tracktion. Keep in mind that you will see latest work in progress and
bugs are inevitable at this state.
We are looking forward for your feedback. Please let me know if the
alternative date works for you.
Best reagards.

18. Situation 2
Guide scrum team stand up meeting
Video response
• A daily stand up meeting is not a status meeting. It is a meeting of the devs
to organize themselves. As a Product Owner I will only join/speak if asked.
• Since it is a professional scrum team, members are aware of the situation.
• I ask if the 2 back-end tickets need support and point out the imortance.
• I announce that I will downgrade 2 tracking requirements to ‘nice to have’.
• We negotiate a plan together and commit to the sprint goal once again.
- one team member will commit to the ticket review
- one team member will take responsibility of the analytics ticket
- the two remaining requirements tickets are shared

19. Hello everyone :)
Our Scrum Master Sebastian called in sick today.
Since the sprint end is near and we still have some urgent task ahead, I m stepping in.
Whats on your agenda? What have you planned for today?
Are you facing any obsitcles? - listen...
Remember there are still tasks we have to tackle until the end of the sprint:
- I need one of you to take care of the 2 back-end ticket reviews, so QA can move on with the these 2
front-end tickets. Who will do it? (Back-End Engineers Name: Frank)? Wait for reaction... (find a solution if
he is blocked)
- And someone has to do analytics requirements ticket. Its time-critical and needs to be done in this sprint.
I think 2 of the 5 tracking requirements tickets are not that vital. I will reprioritized them to ‘nice-to-have’.

20. Situation 3
Handling Resource Constraints
List 2- 3 activities that you
would carry out as a PM to
unblock the scrum team
immediately ?
How would you coordinate
with other PMs to de-risk
your project and raise
appropriate visibility ?
Since there is a potential
risk, it is important to raise
visibility amongst
appropriate stakeholders
• Manual verification and regression for the user stories that have been
completed by then can be done by the PM.
• Ask the team for test automation experience/ knowledge.
• Ask the Head of QA for support - there might be another tester.
• Talk with all PMs that are affected. Maybe there is an easy agreement.
• Explain the importance of my project.
• All PMs rank the projects criticality together and prioritize tests, share tester
• If no compromise, next in hierachy is asked to decide.
• All stakeholders should be identified from the beginning of the project:
Head of QA, PMs involved, team members, person accountable
• a scrum team should bear all knowledge to not be dependent of others -
team members (me included) should be trained
• My communication would not differ. I stay professional. I express my
dissatisfaction calmly with the outcome and organize a meeting with the
other PMs upon how to handle upcoming situations like this.

21. Situation 4
Stakeholder Feedback in Public
Feedback Assessment
Video Response
• What do you think will happen if we do not send notifications?
• Why do you think the product will not succeed without notifications?
• Do you think it is reasonable to launch the MVP to help us understand the
customer-journey and add notification later?
• I can understand your concern/ I am glad to see you want it to succeed.
• Remember it was not part of the MVP. The reason for that is, that we do
not understand the user journey just yet
• We will concider if daily notification a apropiate way to support user
journey 2 sprints from now.
• until then we will be looking forward to work on a notification concept
with you

22. Ok let me first try to understand your concerns correctly:
You are concerned that users will not use the feature because they will not think of it.
But that does not mean the feature is not good enough. It means the usage should be enhanced.
For now, we want the MVP to help us understand the user and its journey.
If we go live early on and see how the feature is being used,
it enables us to define a much more precise concept on how to trigger usage.
We will work on notification after our questions have been answered.
We introduce notification later and with more other details.
What do you think, is it a comprehensible decision?