<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Pro services opportunity: Envisioning Phase for SBP views...</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=1062706" />
  <subtitle>Pro services opportunity: Envisioning Phase for SBP views...</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&amp;threadId=1062706</id>
  <updated>2013-05-18T06:45:01Z</updated>
  <dc:date>2013-05-18T06:45:01Z</dc:date>
  <entry>
    <title>Pro services opportunity: Envisioning Phase for SBP views...</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=1062705" />
    <author>
      <name>Andrew Cadwell</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=1062705</id>
    <updated>2008-09-17T10:37:58Z</updated>
    <published>2008-09-17T10:37:58Z</published>
    <summary type="html">To create a successful mashup that integrates communications to optomize business process, its important to formalize the envisioning process. For client side value applications and "layer 8" integrations, its important to conside the User Experience or UX as a key driver for the solution. This envisioning can then drive the final solution. The fomalized process looks like this and is a billable pro-services opportunity...

1. Vertical Requirements/User Roles
2. Evaluate User Environments
a. Desktop
b. Applications
c. WWW relevance
d. Business Processes
e. Communications Processes
f. Thought Processes
3. Discover technical requirements
a. Web based
b. API integrations
c. Database integrations
d. Webparts
e. etc
4. State Impact
a. Strategic(business)
b. Tactical(user)
5. Solution Overview
6. User Experience(UX)
a. Defines Views
b. Thought-flow
c. Communications
7. Technical feasibility
a. CTI/Telephony integration
b. Defines application connectors
c. Webparts functionality
8. Document
a. Solution Overview DOCS
i. Impact
ii. Solution Overview
iii. (UX) Diagram
iv. Technical Diagram
b. Preliminary SOW 
c. Planning SOW

Good Selling...</summary>
    <dc:creator>Andrew Cadwell</dc:creator>
    <dc:date>2008-09-17T10:37:58Z</dc:date>
  </entry>
</feed>

