PGP 1 Case Study

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 3

PGP 1

Case study and rules


Helping users manage their personal info
For an increasing number of users who access digital products and services on the internet,
username and password is usually the only security measure. However, remembering
passwords or storing passwords safely is hard, often leading users to unsafe practices. Users
usually resort to using the same or similar passwords on multiple sites or storing passwords
where they can be read or compromised.

To address the above problem, Microsoft has announced capabilities to capture and autofill
username and password across devices and platforms. This capability is available on iOS and
Android as a part of Microsoft Authenticator, and automatically syncs with Microsoft Edge. It
is also available on other browsers as Microsoft Autofill extension.

Besides passwords, Microsoft is also adding support for payments and addresses, providing
convenience of secure capture and recall.

Microsoft is committed to building products that add to a user’s peace of mind by letting
them securely access what they care about, no matter where they are. Microsoft Autofill is one
pivotal step towards it, and has already gained significant market share.

Problem Statement

As a PM in Microsoft Autofill team, define the next set of scenarios and types of data that
Microsoft should pursue to boost user adoption, and identify scenarios that can be
monetized.

PGP 1 M I C R O S O F T C O N F I D E N T I A L – I N T E R N A L O N LY
Case study submission guidelines

Teams are expected to submit one functional spec in .doc or .pdf format, covering
the solution to the case.

How to form a team? Please note that you should form a team of 2 along with your
batchmate from the same college.

What’s not allowed:


• Team of 1
• A team with participants from 2 different colleges or batches
Where can I submit the functional spec – details will be shared soon.
By when should I submit the functional spec- 6 th Sept 2021
Which email ID can I write to incase I have doubts [email protected]

What should a functional spec (max 1750 words) contain?


o Problem Definition (approximately 400 words – focus on why – problem, customer value, business
value)
o Goals & Non-Goals (approximately 200 words – focus on what – requirements & user scenarios
that you aim to solve/not solve)
o Feature Description (approximately 900 words – focus on how – features leading to solutions for
user scenarios)
o Success Metrics (approximately 200 words – how to evaluate success for the features planned and
the overall product)
o Workflow (max 1 page (2 slides) – UX design, flow charts etc.)

M I C R O S O F T C O N F I D E N T I A L – I N T E R N A L O N LY

You might also like