|
|
Следующий семинар ATSS состоится в ноябре 2008 года. Next Seminar of ATSS will take place in November 2008. |
| print |
bottom |
| Home | About us | Activities | Events | Specialists | Projects | Programmes | Membership | Publications | International Conferences | Business & Job Opportunities | Classified | Contact Us |
![]() |
Medea Marketing Business Analyst/Product Manager Work Breakdown
-
Sales and Pre-sales
-
a. Attend meetings with clients
- i. Education sessions, product presentations
- b. Build quotes
- c. Find/send out product documentation
-
d. Internal consulting
- i. Briefing on requirements to determine what SPS does and what would need to change/be enhanced
-
a. Attend meetings with clients
-
Business Requirements
-
e. Attend meetings with clients
- i. Education sessions
- ii. Business requirements gathering
- f. Client consulting to determine how SPS could meet their requirements/what would need to be enhanced
- g. Investigating business requirements internally
- h. Correspondence with client
-
i. Templates: For initial projects with new clients, with Template Analyst:
- i. Meetings with clients to review materials
- ii. Consulting to determine links between Templates and functionality (i.e. print ordering, ad ordering, profile)
- iii. Consulting with Development to help translate and clarify customer requirements and to ensure that what is being developed delivers on the customers’ requirements.
- j. Getting approvals (sign-offs) on requirements
-
e. Attend meetings with clients
-
Scoping
- k. Scoping and quoting customizations, maintaining scope
- l. Documenting project budgets
- m. Scoping and quoting system change requests
-
Specifications Documentation
-
n. Attend meetings with clients
- i. Education sessions
- ii. Status reviews
- iii. Business requirements and specifications gathering
- o. Internal meetings to determine what information is needed from the client
- p. Correspondence with clients to gather information
- q. Writing/documentation of specifications for development based on project business requirements
- r. Getting approvals (sign-offs) on project specifications
- s. Internal meetings to determine what info is needed for change requests
- t. Correspondence with clients to gather info for change requests
- u. Writing/documentation of change request specifications
- v. Getting approvals on change requests
-
n. Attend meetings with clients
-
Product Development
- w. Testing enhancements/changes
- x. Consulting with Development to help translate and clarify customer requirements and to ensure that what is being developed delivers on the customers’ requirements.
-
Installation
- y. Answering questions from production team and clients during testing when needed (i.e. clarification of bug reports and change requests)
-
Client Facing Project Management
- z. Communicating schedules and delivery dates with clients
- aa. Following up with clients to ensure delivery dates are met
-
Product Management
- bb. Internal meetings to review and decide on product enhancement requirements
- cc. Writing/documentation of Product enhancement requirements and specifications
- dd. Testing/analysis of product enhancements, decisions on questions of how enhancements should be implemented
-
Post Installation Support
- ee. Consulting with Medea Support staff to help with system support when required (i.e. clarification of bug reports and change requests)
-
Product Documentation
-
ff. Write product documentation including:
- i. SPS Help copy
- ii. Training manuals, guides and tip sheets
- iii. Specifications ‘skeleton’ documents (i.e. the Functional Spec doc, change request doc)
- iv. Product/Project checklists and implementation guides
- v. Template production documentation (i.e. Template design guide, content package documents, bug list,
- vi. Internal financial documents (i.e. price list)
-
ff. Write product documentation including:
| print |
top |
© Content 2000-2004, Alliance of Technology and Science Specialists Inc.
© Design, 2004, SVS Technologies & Research

