www.teamia.com www.teamia.com

Budgets are being cut Work load is increasing Current systems are lacking

features Outdated platforms Inefficient business process

Business Problem

Increase Efficiency Effective use of

technology New technology Upgrade or modification

to existing systems Re-engineer business

processes

Solution(s)

Past

Mainframe application that lasted 20+ years Programming skills and tools were static

Present Distributed architectures, ESBs, Virtualization Internet, GPS, mobile devices/smart phones .NET, Java, Python, Erlang, Boo, DSL, Ruby Programming skills and tools change rapidly

Future - ??

Changing World

Can you do it by yourself? Should you?

Different Skills are needed to maintain a system compared to Re-engineering business processing Developing custom applications Installing, configuring and customizing COTS or

MOTS

If not then how can we reach a solution?

How?

Hire expertise through

partnership(s) that have the knowledge and experience that you need

Let that partner guide you Formulate a team consisting

of agency resources and partner resources that take ownership and shared responsibility in the outcome of the project

Partnership

“a person who shares or is associated with

another in some action or endeavor; sharer; associate”

We are in this together. Success or failure is up to us. We need to know and trust each other.

Trust is built through face-to-face communications

Known expectations/responsibilities

What is a Partner?

1. Expect analysts to speak your language. 2. Expect analysts to learn about your business and your objectives for the system. 3. Expect analysts to structure the requirements information you present into a

software requirements specification. 4. Have developers explain work products. 5. Expect developers to treat you with respect and to maintain a collaborative and

professional attitude. 6. Have analysts present ideas and alternatives both for your requirements and for

implementation. 7. Describe characteristics that will make the product easy and enjoyable to use. 8. Be presented with opportunities to adjust your requirements to permit reuse of

existing software components.9. Be given good-faith estimates of the costs, impacts, and trade-offs when you

request a change. 10. Receive a system that meets your functional and quality needs, to the extent

that those needs have been communicated to the developers and agreed upon.

Customer Bill of Rights

1. Educate analysts about your business and define jargon. 2. Spend the time to provide requirements, clarify them, and iteratively

flesh them out. 3. Be specific and precise about the system’s requirements. 4. Make timely decisions when requested to do so. 5. Respect developers’ assessments of cost and feasibility. 6. Set priorities for individual requirements, system features, or use

cases. 7. Review documents and prototypes. 8. Promptly communicate changes to the product’s requirements. 9. Follow a defined change control process. (This is often the

development partners process)10. Respect the engineering processes the partner uses.

Customer Responsibilities

Who should you chose

as a partner? Trust Expertise

Who?

Not created equal

Software development companies

Software products Software Development

Life Cycles (SDLC) Project Management

methodologies PEOPLE

Expertise

Not much different than hiring an employee

Resume – Proven track record References

Approach What do they bring with them?

Existing tools or products Experience in the specific realm of the project Knowledge of tools, frameworks or products

that help solve the problem

Assessing Company Expertise?

A single prime partner leading the project Partner should be able to provide skills for a

project from inception through post production support Project management, software architecture,

infrastructure architecture, business analysis, design, development, testing (all levels), installation and support.

Continuity is critical

Expertise - Continuity

Cost is not the most significant factor in

determining a partnership. Total Cost of Ownership (TCO) is much more

important than the initial cost: Purchased/licensing costs Initial implementation costs Ongoing maintenance and system usage costs

including agency employee costs Infrastructure (hardware, power, network)

Cost?

Do less work Work more

efficiently Pay less per unit of

work

How to Reduce Costs?

Options for reducing work

Reduce features of application based on priority and severity. Possibly a phased approach

Reduce artifacts/deliverables.

Customer can take on more responsibilities

DO IT RIGHT. The most expensive work is rework.

Do less work

Use the right person for

the job. Huge difference in efficiency between people.

Better tools Timely decisions and

feedback Resource Retention.

Turnover of key resources is very expensive.

Efficiency

Only works if comparing

apples-to-apples. ie. If rate on Person A

drops, cost will drop. But replace Person A with Person B cost might drop or rise depending upon the individuals.

Be careful not to look at rates only. You might get what you pay for.

Pay less per unit of work

Budgets are being cut Work load is increasing Current systems are

lacking features Outdated platforms Inefficient business

process

Business Problems

A Trusted partner that has the expertise,

proven experience, people and tools to guide the team through the process.

Solution

Industry leader in Document Imaging,

Document Management and business process workflows

EMC Strategic partner offering storage and virtualization solutions

Long history of delivering customer focused software solutions to business problems

Locally owned and operated

TEAM ia

TEAM ia has add

key staff to help grow in the application development domain

TEAM ia provides expertise in all areas of SDLC

TEAM ia Expertise

Besides the suite of

licensed tools owned and licensed by TEAM ia, also provide a full suite of the other “Tools of the Trade”

TEAM ia Tools

Questions or Comments?

Questions & Comments

Thank You!

www.teamia.com