Product and Technical product backlog of pdf viewer

ProductandTechnicalbacklog
A point of ready reference to aspiring product managers
https://www.linkedin.com/in/manuswath

TREYresearch
The purpose of this slide set is to
come up with a product backlog
template that contains
requirements for viewing PDF in
applications.
• Atypically such product backlogs do not contain
technology specific requirements/product backlog
items, however this slide set showcases, how such a
requirement specification could possibly exist.
• This slide set hopes to get you started in thinking
about the different area’s that we need to take into
account while drafting such product backlog items.
About
Bring out a template that contains the
following kinds of product backlog items:
Product-level; Non-functional; Technical
https://www.linkedin.com/in/manuswath/

TREYresearch
Veryhighlevelabstract
Depicting what the product should do at the top most level, the level at which the user would see
Desktop Application
1. Select the file to be viewed.
2. View contents of the file in the app.
3. Ability to print the file.
Web based application
1. Select the file to be viewed.
2. View contents of the file in the app.
3. Ability to print the file.

TREYresearch
Introducingthe
problemspace
Taking an example and detailing out the problem space
Product backlog for the ability to
view pdf files stored on a local
computer.
• Integration into existing product.
• Functionality of viewing pdf files stored in the local PC
• Both via desktop and web application
• Users asking for this feature.

TREYresearch
Prominent
Exclusions
Detailing out what will not be covered as part of this slideset
The following are out of scope.
• Market ResearchAnalysisRequirements
• Positioning, Roadmap, Sales specific requirements.
• Balancing corporate goals with long-term market
trends and opportunities, SWOT
• Detailed workflows that handle negative scenarios
• Detailed UI/UX designs  Software language

TREYresearch
ListingouttheAssumptions
Data used in this artifact is constructed and is not
from any specific source.
Technology independent terminology and detailing
for functional requirements.
There are certain areas marked as <TBD> that indicate
areas that could be filled as per dataprofile.

TREYresearch
Persona’s
Indicative list of persona’s these could be
used while writing details in each of the
product backlog items.
7

TREYresearch
JohnSmith
Persona details of John Smith
28 years, 4 years experienced, cloud/web
based user
Moderately experienced in nuances of
the using the web browser to fulfill office
working needs
• Environment: Law office
• Attitude: Customer focused attitude; passion for
justice
• Goal: Looking for ease of use so as to finish work
fast.

TREYresearch
JaneSmith
Persona details of Jane Smith
26 years, 4 years experienced, desktop
application based user.
Has been using the software from the
past 4 years.
• Attitude: <TBD>
• Goal: Detail oriented worker, wants to put every
information in.

TREYresearch
JoeSmith
Persona details of Joe Smith
36 years, 14 years experienced, IT System
administrator.
Has been in the Sys Admin role from the
past 12 years, takes care of uptime,
backup, recovery, etc
• Attitude: <TBD>
• Goal: <TBD>

TREYresearch
BillSmith
Persona details of BillSmith
46 years, 24 years experienced. MD of the
firm
Runs the business, management
stakeholder
• Attitude: <TBD>
• Goal: <TBD>

TREYresearch
Workflows
Very high level depiction of workflows

TREYresearch
Authorizeduserlogin
Start Username
Password
If
valid
user
Display
PDF viewer
upon click
No
Yes

TREYresearch
PDFfilelifecycleworkflow
Start Choose file
Display PDF
viewer upon
selection
Click Print
Print/Email/Dele
te
Stop/Close

TREYresearch
NFRflowforITAdmin
Start
Keep looking for message that mentions that certain
thresholds have been crossed w.r.t HDD space and
performance parameters and unauthorized access,
possible DOS attacks
If occurs
Take defined course of
action and notify
Stop
No
Yes

TREYresearch
AuthorizedManagementUserLogin
Start Username
Password
If
valid
user
Display
Analytics
data
No
Yes

TREYresearch
SampleUI
Section to store and depict basic Low-fidelity
wireframes to enumerate what the product
manager is thinking about.
17

TREYresearch
LandingscreenormainpageofPDFviewerapp

TREYresearch
Uponclickofbutton

TREYresearch
ViewPDFwireframe

TREYresearch
Myfiles

TREYresearch
Requirements
Product backlog depicting Functional requirements.

TREYresearch
Login(Commontobothdesktopandwebapproaches)
Authorized User must be able to log into the system.
PR_ID <Unique Prod_reqt_id>
MRD_ID <Unique_Mrkt_reqt_id>
Details <Detailed description>
Constraints <Any constrained condition that needs
documentation>
Prerequisites <Any prerequisites that need to have happened
before the requirement can be fulfilled>
System Messages <details of any system message or prompts that
need to be put specifically in>
Priority <Must-have or nice-to-have, etc>
Risk Low

TREYresearch
DisclaimerandConfidentialitystatement
The disclaimers and confidentiality statements that need to be put in the web application
documentation>
Risk Low

TREYresearch
AbilitytoopenlocallystoredPDFfiles
The ability to choose and open specific pdf files that have been stored in the local computer from where the user is
trying to access the app
documentation>
Risk Low

TREYresearch
AbilitytoviewPDFfiles
The ability to view selected pdf files that have been stored in the local computer from where the user is trying to
access the app
documentation>
Risk Low

TREYresearch
AbilitytoviewmultiplePDFfiles
The ability to view multiple pdf files that have been stored in the local computer from where the user is trying to
access the app
documentation>
Risk Low

TREYresearch
AbilitytoprintthePDFfiles
The ability to print the selected pdf files that is currently open
documentation>
Risk Low

TREYresearch
AbilitytoemailthePDFfiles
The ability to email the selected pdf files that is currently open
documentation>
Risk Low

TREYresearch
AbilitytodeletethePDFfiles
The ability to delete the selected pdf files that is currently open
documentation>
Risk Low

TREYresearch
AbilitytoclosetheopenedPDFfiles
The ability to closed the selected pdf files that is currently open
documentation>
Risk Low

TREYresearch
AbilitytosendthePDFfilefromlocalsystemtoserver
The ability to send the PDF file to the server when the user is using the web app or cloud application.
documentation>
Risk Low

TREYresearch
Abilitytoviewallthefilesupdatedtilldatetotheserver
The ability to view all the files that have been updated to the server by this specific user and perform “Open” “Print”
and “Delete” on them
documentation>
Risk Low

TREYresearch
ITAdminspecificEpic
The cloud based web application software should keep looking for situations that identify when certain thresholds
have been crossed w.r.t parameters like HDD space, performance parameters and unauthorized access, possible DOS
attacks. In case of any threshold being breached the appropriate rules should be triggered.
documentation>
Risk Low

TREYresearch
ITAdminspecificEpic
The cloud based web application software should be able to prepare and present monthly health-check reports of
how the application is performing on the cloud.
documentation>
Risk Low

TREYresearch
NFRequirements
Product backlog depicting Non-Functional requirements.

TREYresearch
Shouldbeabletofunctionasbefore.Backwardcompatible
Upon adding the new feature, the existing features should not break, this functionality must be added as a new
functionality on top of the existing functionality
NFPR_ID <Unique Prod_reqt_id>
documentation>
Risk Low

TREYresearch
Sizespecific
The application must be able to open pdf files ranging in the following size range 10 KB to 250 MB
documentation>
Risk Low

TREYresearch
SizeandSpeedspecific
The application must be able to open a pdf file of 250 MB in less than 12 seconds.
documentation>
Risk Low

TREYresearch
Content,SizeandSpeedspecific
The application must be able to open a pdf file that contains a lot of HD grapical images of 250 MB in less than 12
seconds.
documentation>
Risk Low

TREYresearch
TestingspecificrequirementsEPIC
The application must be completely tested for all known run time memory leaks.
documentation>
Risk Low

TREYresearch
MiscNF
Requirements
Product backlog depicting Testing, L10N, Section 508,
Usability, Performance, Availability, Backup and
Recovery, Security, Compatibility, Documentation,
Distribution, Training, License, Analytics requirements.

TREYresearch
L10Nsupport
The application must be able to open up the UI on the basis of the set locale of the computer.
documentation>
Risk Low

TREYresearch
Section508Support
The application must be fully capable of section 508 guidelines
documentation>
Risk Low

TREYresearch
TheUIshouldmentionthe%offilethathasbeenuploadedintheweb
applicationAs part of Usability, the UI should mention the % of file that has been uploaded to the server and during that time, the
UI should be modal.
documentation>
Risk Low

TREYresearch
TheruntimememoryandCPUconsumptionofthedesktopapplication
The memory and CPU consumption of the desktop application should not be greater than 50% of the available CPU
and memory. The desktop being Dell Latitude series desktop.
documentation>
Risk Low

TREYresearch
Webapplicationmustbeavailable95%ofthetime
The web application should be available without facing any period of downtime for 95% of the time.
documentation>
Risk Low

TREYresearch
BackupandRecovery
Upon facing any kind of crash, the system including files uploaded should be up and running within 6 hours.
documentation>
Risk Low

TREYresearch
BackupandRecovery
Files that have been uploaded to the server need to be stored for a period of 8 years in archival mode. 8 years from
the termination of contract with the customer.
documentation>
Risk Low

TREYresearch
SecurityRequirementspertainingtofiles
Care must be taken by the application and it should never show up on screen those files that have not been uploaded
by the logged in user.
documentation>
Risk Low

TREYresearch
Browsercompatibilityforweb/cloudbasedapplication
The application should work seamlessly on the latest versions of the following browsers: Chrome, Safari, Firefox
documentation>
Risk Low

TREYresearch
MultipletabsofsameURLindifferentbrowsertabs
The application need not support multiple tabs of the same URL of the same logged in user.
documentation>
Risk Low

TREYresearch
OpeningmultiplewindowsofthesameURLusingthewebapplication
withthesameusercredentialsIf the user opens multiple windows of the same URL of the web application, then he should be prompted saying that
a previous session has already been opened and a prompt with “OK” button should be displayed, upon clicking the
newly opened window/tab should be closed.
documentation>
Risk Low

TREYresearch
OScompatibilityfordesktopbasedapplication
The application should work seamlessly on the latest versions+service packs of the following Operating systems:
Windows 10, Suse Linux, Redhat, Centos
documentation>
Risk Low

TREYresearch
Openingmultipleinstancesofthedesktopapplicationinthesame
systemIf the user tries to opens multiple instances of the same application, then he should get redirected to the already
opened instance and a new instance should not be opened.
documentation>
Risk Low

TREYresearch
DocumentationRequirements
The following documents will be needed as part of product rollout: User Manual, Release Notes, FAQ
documentation>
Risk Low

TREYresearch
DistributionRequirements
The new functionality will have to get rolled out with the next major release in a seamless manner without
inconveniencing the user.
documentation>
Risk Low

TREYresearch
TrainingRequirements
The new functionality should be seamless in showcasing, guiding, prompting the user so that no specific training is
needed.
documentation>
Risk Low

TREYresearch
LicensingRequirements
No specific license requirements, this feature should get rolled out as part of update of product.
documentation>
Risk Low

TREYresearch
AnalyticsRequirementsEPIC
This section is to add a huge number of analytical requirements that I can think of, for e.g Time taken to load file into
server. Exceptions that have occurred, etc
documentation>
Risk Low

TREYresearch
Acceptance
Criteria
Lorem ipsum dolor sit amet, consectetur
adipiscing elit
63

TREYresearch
AcceptanceCriteria
PR_ID Acceptance Criteria
Details <Different AC on the basis of each requirement
Detailed description TBD>
documentation>

TREYresearch
UserStorydescription
PR_ID User Story
documentation>

TREYresearch
Technicaldebts
Tech_Debt_Id Handling technical debt. The accumulated
technical debts will be updated and revisited in this
section
PR_ID <Applicable product requirement id where this
could possibly be used>
documentation>

TREYresearch
ExitCriteria
Mutually decided exit
criteria after performing
UAT.

TREYresearch
Solution Architecture

TREYresearch
Dummy slide that shows
pre-existing product
architecture.

TREYresearch
Requirements
Product backlog depicting Technical requirements.

TREYresearch
Technicalrequirements
This section is about possible situations that could arise up in
the implementation of the above stated business requirements.
This section contains possible technical implementations that
will need to be looked into or taken care off during the
implementation.
This section is to bring such matters into notice upfront and
discuss with the technical solution architecture team on the
way forward and the implementation that can be used.
Please note: this is not a full-scale implementation in any
language. It is an initial collection of tech-know-how

TREYresearch
Makeoptimaluseofcaching,pre-fetchingandbackgroundservicesto
quickenupresponsetimeoffetching/opening/renderingPDFfiles
<Description if needed>
documentation>

TREYresearch
StartupShutdownhooksforthedesktopbasedapplication
documentation>

TREYresearch
OptimumuseofAJAXbasedrenderingofthewebapplication,i.esayfor
example,performingadeleteoperationshouldnotresultintheentire
pagegettingreloaded
documentation>

TREYresearch
IfincasethereareanyListeners/Connectionsthathavebeenopenedto
theserver,theapplicationshouldmakeuseofanexistingpoolof
connectionsandmakemaximumreuseofthepoolratherthancreating
newconnections.
documentation>

TREYresearch
ThemaximumnumberofListenersthatcanbeenopenedtotheserver
shouldbepresentinaconfigurationfile.
documentation>

TREYresearch
Allconfigurationsspecifictothresholds,limits,responses,
people_to_be_notifiedetcshouldbepresentinaconfigurationfile.
documentation>

TREYresearch
Absoluteminimumnumberofnetworkcallsshouldexistandtranspire
betweentheapplicationandtheserver.
documentation>

TREYresearch
Atthetimeofopeningafile,atthetimeofprocessingalogin,amodal
loadershouldbepresentonthescreen,thatdisallowstheuserfrom
pressingorperforminganyotheractions
documentation>

TREYresearch
Preprocessmetadataofimages,takecarenottoloadthewholeimage
togetthemetadata.
documentation>

TREYresearch
Followingcodingperformancebest_casesmentionedinofficial
documentation
documentation>

TREYresearch
Priorityinmessagehandling
documentation>

TREYresearch
Requirements
Product backlog depicting Process requirements.

TREYresearch
Thecodeshouldhaveatleast80%ofcodecoverage.Thecodemust
havehadcompiletimetestingofmemoryleaksusingbuiltintesting
toolsintheIDEandthereportshouldberepopulatedforeverybuildand
checkedintoSourcecontrol.Javadocbaseddocumentationforevery
classandmethod.Updateddesigndocumentsatendofevery
phase/sprint
documentation>

TREYresearch
Alldependent/referencedpackages/libraries/frameworkshavetobe
listedandcompatibilitycheckswithsuitableupgradeshavetobe
performedbeforereleaseofeverymajorversionofproduct.
documentation>

TREYresearch
ThankYou
Manuswath K.B
manuswath@yahoo.com

Product and Technical product backlog of pdf viewer

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Product and Technical product backlog of pdf viewer

Similar to Product and Technical product backlog of pdf viewer (20)

More from Manuswath K.B

More from Manuswath K.B (20)

Recently uploaded

Recently uploaded (20)

Product and Technical product backlog of pdf viewer

Editor's Notes