Presentation is loading. Please wait.

Presentation is loading. Please wait.

[Spec Title] Proposal for [release name] [DATE], 2015 [Date][TITLE] 1/6.

Published byJason Gaines Modified over 9 years ago

Similar presentations

Presentation on theme: "[Spec Title] Proposal for [release name] [DATE], 2015 [Date][TITLE] 1/6."— Presentation transcript:

1 [Spec Title] Proposal for [release name] [DATE], 2015 TEAM-EMAIL@RIVERBED.COM [Date][TITLE] 1/6

2 [Date][TITLE] 2/6 PM[name]Approved Date/Not Approved UX[name]Approved Date/Not Approved Engineering[name]Approved Date/Not Approved Front-end[name] Back-end[name] QA Front-end[name] QA Back-end[name] UX[name] UX Strings[name] Approvers Dev Primes Stakeholders PM[name] Eng[name]

3 Design Brief Background Why is this project being requested/worked on? Problem State what the problem is that the spec is trying to solve. Who is affected? Why is this problem important to them? Justification Why should we do this ? Justification may include vision fit, customer testimonials, user tests etc. 12/19/2014QOS FOR USDA RVBD-UX@RIVERBED.COM 3

4 12/19/2014QOS FOR USDA RVBD-UX@RIVERBED.COM 4

5 Prioritized Requirements 12/19/2014QOS FOR USDA RVBD-UX@RIVERBED.COM 5 RequirementsPriority

Download ppt "[Spec Title] Proposal for [release name] [DATE], 2015 [Date][TITLE] 1/6."

Similar presentations

Use Case: Use case title Submitter(s) Submitting Company #1 – Submitter 1, Submitter 2 Supporters(s) Supporting Company #1 – Submitter 1, Submitter 2 Use.

Use Case: Use case title Submitter(s) Submitting Company #1 – Submitter 1, Submitter 2 Supporters(s) Supporting Company #1 – Submitter 1, Submitter 2 Use.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 1.

Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 1.
Title Presented by: For: Date:. Summary The summary is intended to provide the audience with a quick overview and basic understanding of the essential.

Title Presented by: For: Date:. Summary The summary is intended to provide the audience with a quick overview and basic understanding of the essential.
INFORMATIVE SPEECH Seminar on Tuesday, Nov. 9 th, 2010.

INFORMATIVE SPEECH Seminar on Tuesday, Nov. 9 th, 2010.
1 Pramerica Systems Ireland Lean Principles for Systems Development Pramerica’s Journey to eliminate waste Mary Howick 8 th October 09.

1 Pramerica Systems Ireland Lean Principles for Systems Development Pramerica’s Journey to eliminate waste Mary Howick 8 th October 09.
Agile Software Engineering Frank Maurer Agile Software Engineering Lab, University of Calgary

Agile Software Engineering Frank Maurer Agile Software Engineering Lab, University of Calgary
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
Commonwealth of MA - ITIL Implementation Government Technology CTO Conference March 20, 2006 Bethann Pepoli, Deputy CIO.

Commonwealth of MA - ITIL Implementation Government Technology CTO Conference March 20, 2006 Bethann Pepoli, Deputy CIO.
Thunderdome Project Process Planning Channel Kick-Off Meeting Review Editorial Requirements Document and map out plan for channel: initial roadmap (minimum.

Thunderdome Project Process Planning Channel Kick-Off Meeting Review Editorial Requirements Document and map out plan for channel: initial roadmap (minimum.
Software Waterfall Life Cycle Requirements Construction Design Testing Delivery and Installation Operations and Maintenance Concept Exploration Prototype.

Software Waterfall Life Cycle Requirements Construction Design Testing Delivery and Installation Operations and Maintenance Concept Exploration Prototype.
Software Project Planning Chapter 2 Applied Software Project Management, Stellman & Greene.

Software Project Planning Chapter 2 Applied Software Project Management, Stellman & Greene.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.

ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Presentation to the “Board of Education” Assuming different Roles: Board members, administrators, teachers, business, and parents.

Presentation to the “Board of Education” Assuming different Roles: Board members, administrators, teachers, business, and parents.
Improving Accessibility of Mobile Phones Petteri Alinikula.

Improving Accessibility of Mobile Phones Petteri Alinikula.
Applied Software Project Management

Applied Software Project Management
So You Want to Research Handout for MA 4. Proposal Identifying the problem Understand the issue Cause and effect relationship Develop strategies/solutions.

So You Want to Research Handout for MA 4. Proposal Identifying the problem Understand the issue Cause and effect relationship Develop strategies/solutions.
Business Plan Your Proposed Company Name Here. Mission / Purpose of Your Business Give an overview here.

Business Plan Your Proposed Company Name Here. Mission / Purpose of Your Business Give an overview here.
Social Media Icons. Background The University of Waterloo wordmark does not work well in the small-and-square format of social media icons. As part of.

Social Media Icons. Background The University of Waterloo wordmark does not work well in the small-and-square format of social media icons. As part of.
IT Challenge Tutorial. What is the IT Challenge Business strategy IT Know-How Creativity Application of skills Industry, customer and problem analysis.

IT Challenge Tutorial. What is the IT Challenge Business strategy IT Know-How Creativity Application of skills Industry, customer and problem analysis.
Ch. 6.  How did this problem come about?  Why does it need to be solved?  Try to limit the objective so that it can focus on finding a specific solution.

Ch. 6.  How did this problem come about?  Why does it need to be solved?  Try to limit the objective so that it can focus on finding a specific solution.

Similar presentations

Ads by Google