PurposeTo setup and develop technologycapability for the future and nearfuture Research Engine. Design Engine. Problem Resolution
Work AreasFuture Explore technology Business Strategy POC of product ideas Training of team members Scalability PerformanceNear - Future Manage complex modules Availability Design and spec-ing of current projects / Product opportunities Security Engineering & Quality certification of current projects [SPASM] Manageability
1 Product Life Cycle Present POC & Stages Anticipate Deal & Discuss InvestActivities Create a Display Capability Build POC using Sell the solution to technology get buy in for new and existing the customer. framework around project modular code a business RequirementSolutions Model framework for VOC Feature Design - QFD Marketing & a business req. Presentation Packaging Head Customer Visits Business Models Financial Structures Role Participate in Forums Contract Models University tie-ups?Solutions Develop a technology Build POC framework around the Identify & Set Team business req. Technology Role Build working models challenges Dabble in technology Explore technologies Customer Visits Participate in Forums University tie-ups?
2 Product Life Cycle Stages Deliver Maintain ProductizeActivities Build the product Build a Generalize – Iron clad it maintenance Modularize for relationship future business relationshipsSolutions Project Manage Account Management Identify Further Head Resource Management Contract models Applications Templated design Role Market Research – Sales Quality Engineering Tech - Support Feature EnhancementsSolutions Performance Engineering Platform Independence Develop certain modules Team Role
Solutions Head ++• Identify Market Opportunities – Based on technology portfolio• Customer Interactions – Project pre-sales design and understanding – VOC + customer feedback• Business strategy – For growing technology capability• Financial planning & costing• Resource management.
It is critical that..…the solutions team interacts &with & delivers along with techteam during projects… Such revenue generating activities to maintain relevance of the team and thereby motivation
A team consisting of..~ 15 members. Working on 2 modes 1. Basic technology explore new technologies explore new products - FOSS explore new frameworks [for e.g. search algorithms, dynamism, 2. Specific technology applications
Typical Team Member – Additional to be being a software programmer• Masters – Primary Research – Domain know-how• Systems understanding – Great comfort /knowledge in basic infrastructure like linux• Logic / Basics – Algorithms / logic mathematics – Statistics?• Quality – Good design & documentation know how and intent
Vishwanath Ramdas …• Process and Business Consultant• Working Areas – ITSM, Process consulting, – Product Design & development, – Business & Finance Management• Bangalore [India]• Web UID: gopu44 – http://gopu44.googlepages.com – http://www.slideshare.net/gopu44