Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Goal

  • E.g. Simplify the user experience, reduce friction etc...

Background and strategic fit

Why are you doing this? How does this relate to your overall product strategy?

Assumptions

  • List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).

Functional Requirements 

#RequirementsShort descriptionType*

Business Value

(0-less 5-higher)

Effort needed

(in hours)

Timeline

(2015 or 2016)

1      
2      

* TYPE: New feature; Improvement; Bug Fix; 

 

  • Beyond Patient Summary and ePrescription use cases
#RequirementsShort descriptionType*

Business Value

(0-less 5-higher)

Effort needed

(in hours)

Timeline

(2015 or 2016)

1      
2     

* TYPE: New feature; Improvement; Bug Fix; 


Non-Functional Requirements 

#RequirementsShort descriptionType*

Business Value

(0-less 5-higher)

Effort needed

(in hours)

Timeline

(2015 or 2016)

1      
2      
       
       
      

* TYPE: New feature; Improvement; Bug Fix; 

 

  • No labels