Project Pitch ( Software Engineering)

Everything is in the file please it is makeup assignment. Each Proposal should contain (minimum 4,000 words):? An Elevator Pitch (~half page)? Motivation (why do you want to make this software, why does the world need it) (~halfpage)? Comparable Products (what else is out there) (1 page)? Feature Description (~ 2-3 pages)? Technical specs (what languages and skillsets would be needed) (~ half page)
screen_shot_2017_12_13_at_2.13.17_pm.png

project_pitch.pdf

Don't use plagiarized sources. Get Your Custom Essay on
Project Pitch ( Software Engineering)
Just from $13/Page
Order Essay

project.pdf

Unformatted Attachment Preview

Project? ?Pitch
This? ?semester? ?we? ?will? ?be? ?conducting? ?a? ?3,? ?week? ?long? ?scrums.? ?The? ?class? ?will? ?be? ?split? ?into? ?teams? ?of
4.? ?This? ?will? ?allow? ?each? ?team? ?member? ?to? ?practice? ?a? ?different? ?team? ?role? ?each? ?Sprint? ?(a? ?week).
Each? ?team? ?will? ?be? ?developing? ?a? ?piece? ?of? ?software? ?in? ?a? ?language? ?of? ?their? ?choosing? ?or? ?through
interactive? ?prototyping.? ?Everyone? ?in? ?the? ?class? ?has? ?their? ?own? ?background? ?and? ?expertise.? ?You? ?may
be? ?a? ?good? ?Java? ?programmer,? ?a? ?web? ?developer,? ?a? ?graphic? ?artist,? ?or? ?a? ?mobile? ?programmer.
Everyone? ?will? ?be? ?assigned? ?to? ?a? ?team? ?project? ?in? ?which? ?they? ?will? ?be? ?able? ?to? ?contribute? ?fully.
The? ?projects? ?will? ?come? ?FROM? ?YOU.? ? ?In? ?this? ?assignment,? ?every? ?student? ?individually?? ?will
prepare? ?a? ?project? ?proposal.? ?The? ?proposals? ?will? ?be? ?made? ?available? ?for? ?everyone? ?to? ?review? ?after
the? ?final? ?submission.? ?Each? ?student? ?will? ?vote? ?for? ?their? ?top? 3
? ? ?proposals? ?(not? ?your? ?own).? ?The? ?top
proposals? ?will? ?get? ?made? ?this? ?semester.? ?Each? ?group? ?will? ?then? ?be? ?assigned? ?a? ?proposal? ?that? ?is? ?fitting
for? ?that? ?group.? ?Each? ?team? ?will? ?also? ?have? ?the? ?option? ?of? ?doing? ?interactive? ?prototypes? ?if? ?they? ?do? ?not
wish? ?to? ?code.? ?Each? ?team? ?will? ?not? ?necessarily? ?finish? ?their? ?project? ?but? ?you? ?will? ?complete? ?4? ?full
weeks? ?of? ?Software? ?Engineering? ?including? ?implementation.
Each? ?Proposal? ?should? ?contain? ?(minimum? ?4,000? ?words):
? An? ?Elevator? ?Pitch? ?(~half? ?page)
? Motivation? ?(why? ?do? ?you? ?want? ?to? ?make? ?this? ?software,? ?why? ?does? ?the? ?world? ?need? ?it)? ?(~half
page)
? Comparable? ?Products? ?(what? ?else? ?is? ?out? ?there)? ?(1? ?page)
? Feature? ?Description? ?(~? ?2-3? ?pages)
? Technical? ?specs? ?(what? ?languages? ?and? ?skillsets? ?would? ?be? ?needed)? ?(~? ?half? ?page)
Page? ?limits? ?are? ?only? ?a? ?rough? ?estimate? ?(but? ?you? ?must? ?reach? ?4,000? ?words? ?one? ?way? ?or? ?another).? ?I
am? ?mainly? ?concerned? ?that? ?you? ?get? ?the? ?idea? ?for? ?your? ?project? ?across? ?in? ?a? ?clear? ?and? ?professional
fashion.? ?Depending? ?on? ?the? ?project,? ?this? ?may? ?take? ?many? ?more? ?pages? ?of? ?writing? ?to? ?fully? ?flesh? ?out
your? ?idea? ?and? ?you? ?might? ?need? ?additional? ?sections.
During? ?the? ?project? ?you? ?will? ?be? ?using? ?interactive? ?paper? ?prototypes? ?so? ?please? ?feel? ?free? ?to? ?use? ?your
imagination? ?to? ?come? ?up? ?with? ?interactions? ?and? ?software? ?ideas? ?that? ?have? ?not? ?been? ?created? ?before.
First? ?Draft? ?Due? ?Date:? ?10/29/17
Draft? ?Returned:? ?11/05/17
Optional? ?1-1? ?meeting:? ?11/06/17
Final? ?Submission:? ? ?11/12/17
IT 210
Project ends on December 9th 2017
Scrum Project
You will be assigned a project based on the submitted options. You and your team will read the
proposal and create a backlog and get the product owner’s approval (me). Following that, you have
3 weeks until the project is done. This will allow you 3 Sprints. Your team will consist of two main
roles. 1 person each Sprint must be the Scrum Master. As Scrum Master, they are responsible
that the team follows the correct scrum process, and as such they will be graded on the team’s
performance. They may also accept a reduced amount of development work. The other 3 people
will be on the development team. Roles within the development team are up to you to decide each
week. The Scrum Master should change each Sprint. Each Sprint you should follow a complete
Sprint cycle.
• Groom the product backlog: Refine each item in the log. Add more details where they
are known and reassess how long each task will take through planning poker or your own
mechanism.
• Plan your sprint: Pick out which items you can complete during the sprint. This may involve
refining each item in the product backlog into individual tasks.
• Daily Scrum: I expect each team member to spend between 6 and 9 hours a week outside
of class time working on their assignments. This development time will be broken down into
daily Scrums. A daily scrum includes a stand up meeting where everyone answer 3 questions
1. What did I accomplish since the last daily Scrum?
2. What do I plan to work on before the next daily scrum?
3. What are the obstacles or impediments that are preventing me from making progress.
• At the end of the Sprint you will have a potentially shippable product (see below for what
that includes).
• Sprint Review: This will include the product owner. As a regularly scheduled meeting (invite
me, can be during class). You will conduct the Sprint review and get feedback from the
product owner.
• Sprint Retrospective: The development team along with the Scrum Master, will fine tune
their Scrum process.
Grading:
• Initial Team Product Backlog (Due November 19th)
• You will be graded based on how well you perform the Sprint cycles. For example, how close
your planning matched your shippable product.
• You will also be graded relative to other teams in terms of expectation of how much should
be included in a Sprint (so estimate your time correctly). Include your team roles in each
Sprint’s documentation.
• Artifacts required each Sprint: Product backlog, Sprint Plan, Use Cases, Sprint Retrospective.There will be not late assignments in this. Sprints are a fixed length.
• Final Report (Due Dec 9th): At the end of the class you will submit a final report that details
what was accomplished in the product, what did not get completed, what areas of Scrum were
successful, what areas fell short.
Percents:
Project Proposal (individual): 30% Initial Backlog: 5%
Sprint 1: 20%
Sprint 2: 20%
Sprint 3: 20%
Final Report: 5%
Problems:
If your team runs into problems with team work, contact me as soon as you can so it can be
resolved. If I do not hear of any issues with a team member, I will assume things are working as
your intend.
I reserve the right to cause you “Problems” as a bad Product owner who changes his mind. If I
change a requirement on the project or on your product backlog, it should be addressed by the team.
Potentially Shippable Product:
As a team you will have the option of developing (coding) or paper prototyping each feature. If
you code I do not expect as many items to get done each Sprint. If you do prototyping I’d expect
much more progress to be made.
If you are coding, you may use any language you feel appropriate for the project. If you do paper
prototyping I expect full interactive paper prototypes where I as the product owner can “click” on
the paper and the next screen will appear simulate functionality.
As part of the shippable product each week I expect full artifacts submitted.
1. Product backlog (story points should be done via planning poker or other technique)
2. Sprint Plan (indicate which items to be done and by which person)
3. Use Cases (every thing in your Sprint Plan for that week should get a Use Case)
4. Burndown Chart
5. Sprint Retrospective (1-2 Paragraphs)

Purchase answer to see full
attachment

Order a unique copy of this paper
(550 words)

Approximate price: $22

Basic features
  • Free title page and bibliography
  • Unlimited revisions
  • Plagiarism-free guarantee
  • Money-back guarantee
  • 24/7 support
On-demand options
  • Writer’s samples
  • Part-by-part delivery
  • Overnight delivery
  • Copies of used sources
  • Expert Proofreading
Paper format
  • 275 words per page
  • 12 pt Arial/Times New Roman
  • Double line spacing
  • Any citation style (APA, MLA, Chicago/Turabian, Harvard)

Our guarantees

Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.

Money-back guarantee

You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.

Read more

Zero-plagiarism guarantee

Each paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.

Read more

Free-revision policy

Thanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.

Read more

Privacy policy

Your email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.

Read more

Fair-cooperation guarantee

By sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.

Read more

Calculate the price of your order

550 words
We'll send you the first draft for approval by September 11, 2018 at 10:52 AM
Total price:
$26
The price is based on these factors:
Academic level
Number of pages
Urgency

Order your essay today and save 15% with the discount code ESSAYHELP