Login
pay invoice online
|
remote assistance
|
INTERNET APPLICATION DEVELOPMENT
Services
Web Application Development
Mobile Applications
Integration Solutions
Staff Augmentation
Technologies
How we work
About us
Success stories
Blog
MID MARKET ERP DEVELOPMENT
Intacct
Sage CRM
Sage
Sage Component Catalog
How We Work
About Us
Success Stories
Blog
Blog
CodePartners Blog
CodePartners Methodology: the Statement of Work
SHARE THIS
Print
Email
By Brian Terrell
Often I am asked by a prospect or client “What is your process?” or “What are next steps?” Everyone wants to know what CodePartners will do to create a software automation to help increase revenues, decrease costs, or achieve some other measurable business objective. All significant rewards necessarily include some risks, and our clients deserve to know how we manage those risks. As I discussed in this blog recently, that process begins with a Requirements Analysis followed by a Design Document. Once the client or prospect approves the Design Document, then CodePartners drafts the Statement of Work (“SOW”).
A Statement of Work usually begins with an executive summary on the history, background and objectives of the proposed project. This section in the SOW introduces the project and allows the reader to get quickly up-to-speed about the project and the ensuing Statement of Work.
A detailed Scope of Work follows this introductory portion of the SOW. It includes the action steps CodePartners will take to achieve the project’s objectives, and this section makes up the major portion of the document. Many details from the Design Document are included here, and references to the Requirements Analysis or Design Document may be directly or indirectly made. It’s hard to have too much detail in the Scope of Work, so there is no doubt as to what success looks like. Documentation, testing, training, deployment and support requirements are written out, and a timeline for accomplishing each phase of the project is included.
Some Statements of Work include the business details of the engagement, such as invoicing and payment terms as well as non-disclosure agreements and other legal agreements. Or, we include these details in a Master Services Agreement, which is attached to the SOW. When a Master Services Agreement governs the basic business relationship the Statement of Work becomes much more compact and easy to read.
An SOW concludes with a signature page, where both parties note their acceptance of the project’s Scope of Work. When both parties complete the SOW our CodePartners development team takes over. They’ll take the Requirements Analysis, Design Document, and Statement of Work and begin the actual creation of software code, and the client is one step closer to achieving a business objective through software automation!
Next time, we’ll review the details of the development phase in the software development lifecycle and the different methodologies of managing that effort. Writing code is less like building a house or some other manufacturing process and more like creation or research. Chances are, the objective has never before been accomplished, and that means more risks to manage and more rewards to share. And, there is always more than one way to do things, and I’ll look forward to sharing more about that soon!
Comments are closed.
Tagged With:
project development
,
project management
/ 2527 Views
Search
Categories
General (166)
Development (158)
Success Stories (40)
Products (29)
Uncategorized (18)
BTerrell Group (5)
Project Management (22)
Web Development (57)
Web application (33)
Integration (19)
Mobile Development (7)
Archives
2015
January (5)
February (7)
March (6)
April (5)
May (2)
2014
January (13)
February (12)
March (13)
April (12)
May (11)
June (12)
July (11)
August (13)
September (10)
October (8)
November (6)
December (4)
2013
April (73)
May (22)
June (20)
July (20)
August (22)
September (19)
October (13)
November (12)
December (7)
Tags
.NET
Accpac
app development
application customization
application development
automation
Azure
C#
cloud
components
Crystal Reports
customization
development
ERP
general ledger
HTML5
Intacct
Intacct Platform Services
integration
JQuery
load balancer
mass update
mobile development
OCR
Order Entry
outsourcing
PO
pricing
product development
project management
REST
Sage 300 ERP
Sage CRM
software integration
trigger
user interface
Visual Studio
web application
web development
website development
Workforce Go!
.NET
ACA
accpac
Ajax
Amazon
AP invoices
application development
Arxis
ASP.NET
automation
Axure
BTerrell Group
C#
Cloud computing
CodePartners
Constant Contact
credit card processing
CRM
crystal reports
custom software
Customer Service
Customization
Delete team project
design phase
Development
doc-link
DRILLDWNLK
ERP
event
Excel
GLAFS
Intacct
Intacct Advantage
Intacct Platform Services
Integration
Java script
JavaScript
jQuery
Kerr Consulting
LinkedIn
Microsoft
MSSQL
Offshoring
outsourcing
payroll
PCI compliance
PCI-DSS
Pivot
PJC
project management
sage
Sage 300
Sage 300 ERP
Sage Accpac ERP
Sage CRM
Smart Rule
social media
software testing
SQL
SQL Query
SQL Server
staff augmentation
sub-ledger
success
success story
TFS
Trouble shooting
UI design
Visual Studio
WCF
Web API
web application
web design
web development
Webinar
website
Windows
Windows Azure
XML
Email this article from Codepartners.com
Separate multiple addresses with commas(,)
To:
*
Copy me
Subject:
From:
*
Message:
ABOUT US
/
CONTACT US
/
NEWS & EVENTS
CodePartners / 16200 Addison Rd. STE 270 / Addison, Texas 75001 / Phone:
214-647-2611
/ Toll Free:
866-647-2611
/ Fax:
214-647-2612
/
info@codepartners.com
© 2006 - 2015 codepartners.com All Rights Reserved.