SpecMyApp – An Overview
Get your specifications right and
make your project a success
Root cause of software project failure
61% of projects since 2004 to
2012 fail or are challenged
(Chaos Report from the St...
“Require multiple tools to
do the job”
“Unstructured and
scattered”
“Too technical for
business users”
“Does not facilitat...
The Specifications Chasm
Development
Testing
DocumentationDeployment
DesignBusiness
Requirements
Delivery centered
around
...
and expectations are growing …
“We expect very user
friendly interfaces”
“Shorter improvement
cycles which deliver
busines...
The Solution
Development
Testing
DocumentationDeployment
Design
Structured
Business
Requirements
Effective
Results
Process...
Capability Summary
Project Setup &
User Configuration
Requirements Process Modeling
Wireframing
Team
Collaboration
Reports...
Can be used for …
Recording
Requirements
Model Business
Processes & Use
Cases
Structured
Specifications
Capture
Wireframe ...
Expect big benefits…
Time to MarketExecution Costs
Complexity Project Loop backs
Source the best
execution resources
Effor...
Typical Users
User Organization
• Business Analysts
• Project Managers
• User Champions or Key
Users
• Process or Business...
The next ‘ innovation leap’ in application
development outsourcing
Offshoring
& Near
shoring
Agile
Collab-shoring
using to...
Bottomline …
Project
Modules
Processes ReportsScreens
Elements
Sections
Approval
Workflow
Process Use
Cases
Process
States...
Try and experience it …
www.SpecMyApp.com
Visit
And signup for a
free trial
Upcoming SlideShare
Loading in …5
×

How to specify software correctly, and avoid the common reasons for project failure

922 views

Published on

Studies and real experience have brought out the critical importance of requirement specifications in the success of any software project. Get the specifications right, and the project usually will be on time, on budget and used by users. Get it wrong, or iterate too many times and the project will go wrong on all aspects of delivery. Yet, good tools for specifications are lacking, especially on the Cloud

This presentation shows you how to get your specifications right using SpecMyApp.com.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
922
On SlideShare
0
From Embeds
0
Number of Embeds
24
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

How to specify software correctly, and avoid the common reasons for project failure

  1. 1. SpecMyApp – An Overview Get your specifications right and make your project a success
  2. 2. Root cause of software project failure 61% of projects since 2004 to 2012 fail or are challenged (Chaos Report from the Standish Group) 40-50% of the budget is consumed by rework (Boehm and Basili) 75-85% root causes of rework is from poor requirements (Dean Leffingwell) The companies using poor requirements practices will … be on budget less than 20% of the time. 50% of time, the overrun on the project both in time and budget will be massive. (Boehm and Basili)
  3. 3. “Require multiple tools to do the job” “Unstructured and scattered” “Too technical for business users” “Does not facilitate feedback and collaboration” “Not updated once development starts and hence thrown away” “Everyone does it differently” “Mostly re-written for the next version” “Leads to too many iterations in development” “Don’t know when specifications are complete” Typical opinions on Specifications
  4. 4. The Specifications Chasm Development Testing DocumentationDeployment DesignBusiness Requirements Delivery centered around incomplete documents and images Highly deviated output Unstructured, Incomplete Requirements The specifications chasm
  5. 5. and expectations are growing … “We expect very user friendly interfaces” “Shorter improvement cycles which deliver business value” “Virtual collaborative teams, not outsourced development” “Want to review interface & specifications before development starts” “We have to get it right even if it means multiple prototypes” “We want perfect quality before we go live” “Processes should be specific to our needs” “With development getting automated, specifications is the key” “You have to deliver what the business needs, and avoid any deviation”
  6. 6. The Solution Development Testing DocumentationDeployment Design Structured Business Requirements Effective Results Process Modeling Screen Modeling Wireframing Business Rules Extract for Execution Delivery centered around accurate logical model
  7. 7. Capability Summary Project Setup & User Configuration Requirements Process Modeling Wireframing Team Collaboration Reports & Notifications Modeling Detailed Specifications & Rules Extract for Project Execution Account Control Panel
  8. 8. Can be used for … Recording Requirements Model Business Processes & Use Cases Structured Specifications Capture Wireframe or Prototype Capture Functional Specifications Specifications for development outsourcing Inputs for detailed testing & documentation Versioning of specifications Application Capability Repository
  9. 9. Expect big benefits… Time to MarketExecution Costs Complexity Project Loop backs Source the best execution resources Effort & Stress
  10. 10. Typical Users User Organization • Business Analysts • Project Managers • User Champions or Key Users • Process or Business Owner Delivery Organization • Delivery Managers • Business Consultants • Product Managers • Team Leaders • Functional Consultants • System Analysts • Application Architects • Designers • Development Heads • Testing Consultants
  11. 11. The next ‘ innovation leap’ in application development outsourcing Offshoring & Near shoring Agile Collab-shoring using tools like SpecMyApp
  12. 12. Bottomline … Project Modules Processes ReportsScreens Elements Sections Approval Workflow Process Use Cases Process States Get your specifications right, and make your project a success
  13. 13. Try and experience it … www.SpecMyApp.com Visit And signup for a free trial

×