© 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal...

22
© 2010 IBM Corporation © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred Collins – Executive Architect [email protected]

Transcript of © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal...

Page 1: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation© 2010 IBM Corporation

Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing

Dr. Fred Collins – Executive [email protected]

Page 2: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Title: Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing

Audience: USGS

Abstract: The author will briefly introduce and define crowdsourcing, describe its value proposition, and discuss aspects of crowdsourcing applicable to geospatial applications / development. The author will discuss lessons learned and best practices.

About the Author: Dr. Fred Collins is an Executive Enterprise Architect supporting IBM’s Public Sector Consulting Practice. His main areas of expertise are SOA, Enterprise Architecture, Architecture Methods, Web 2.0, Geospatial Applications / Architectures, and Architecture Modeling / Repositories.

2

Page 3: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

DEFINITIONSBrief Introduction to Crowdsourcing

3

Page 4: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Crowdsourcing is a distributed problem-solving and production model. In the classic use of the term, problems are broadcast to an unknown group of solvers in the form of an open call for solutions. Users—also known as the crowd—typically form into online communities, and the crowd submits solutions.

Perceived benefits of crowdsourcing include the following:

– Problems can be explored at comparatively little cost, and often very quickly.– Payment is by results or even omitted– The organization can (theoretically) tap a wider range of talent than might be present in

its own organization– Organizations gain first-hand insight on their customers' desires.– Brand-building and sense of ownership through contribution and collaboration.

4

What is crowdsourcing?

Page 5: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Crowdsourced Work – From Micro Tasks to Complex Projects

5

Work submitted through crowdsourcing tools falls into four categories, from very high volume Micro Tasks to one-time Complex Projects.

Page 6: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Geospatial Crowdsourcing Examples

Amazon Mechanical Turk was used in the search for aviator Steve Fossett, whose plane went missing in Nevada in 2007. Up to 50,000 people examined high-resolution satellite imagery from DigitalGlobe that was made available via Amazon Mechanical Turk. The search was ultimately unsuccessful.

Galaxy Zoo is a citizen science project that lets members of the public classify a million galaxies from the Sloan Digital Sky Survey.

OpenStreetMap uses crowdsourcing for creation and maintenance of geospatial data. Google and TomTom are also leveraging this business model

6

Page 7: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Quake-Catcher Network - developing the world's largest, low-cost strong-motion seismic network by utilizing sensors in and attached to internet-connected computers.

Many laptops currently have Sudden Motion Sensors or Active Protection Systems inside them. While these sensors were originally designed to help protect the computer's hard disk in case they are dropped or shaken, seismologists can use them to detect earthquakes.

The Quake-Catcher Network (QCN) links participating laptops into a single coordinated network that can detect and analyze earthquakes faster and better than ever before. The laptop network is the least expensive seismic network in the world. Because volunteers (individuals like you) donate idle CPU time on laptops with these sensors already built in, each additional sensor doesn’t cost a thing!

7

Passive Crowdsourcing

Page 8: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

The blurring of crowdsourced work and on-line collaborative gaming (e.g. World of Warcraft)

8

Cerberus is an automated processing engine that translates any type of photographic satellite data into usable GIS data by harnessing the power of the crowd. Cerberus is an interactive computer game where players process photographs by marking interesting features like river deltas on Mars, the evolution of glaciers on Earth and so on.

In this example the player categorizes sand dunes on Mars to gain points and move to the next level

Page 9: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

In the fall of 2008, DC hosted Apps for Democracy to make its data catalog more useful for the citizens, visitors, businesses and government agencies of Washington, DC. The Data Catalog contains all manner of open public data featuring real-time crime feeds, school test scores, and poverty indicators, and is the most comprehensive of its kind in the world.

Apps for Democracy was essentially a crowdsourced approach to application development featuring $50,000 worth of incentives which returned 47 iPhone, Facebook and web applications with an estimated value in excess of $2,600,000 to the city.

Apps for Democracy took the crowdsourcing model, added financial incentives, and applied it to the public sector (Government of Washington DC)

http://www.appsfordemocracy.org/application-directory/

Page 10: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Shortcomings of the crowdsourcing model

Quality of resources (no past performance, resumes, credentials, etc.)

No written contracts, non-disclosure agreements, or employee agreements with crowdsourced employees.

Difficulties maintaining a working relationship with crowdsourced workers throughout the duration of a project.

Susceptibility to faulty results caused by targeted, malicious work efforts.

Reusability and scalability of crowdsourced applications

Issues with ownership and intellectual property rights

IBM weighed the benefits and shortcomings of the crowdsourcing model and launched an initiative called Generation Ocean (GenO) to tap into its crowd of global talent. The goal was to address the shortcomings while still reaping the benefits of crowdsoucing.

10

Page 11: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

LIQUID

GenO Liquid allows IBM to satisfy unmet demand for software solutions and defining work so any practitioner with the right skills at the right time can complete it

11

Page 12: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Liquid is a crowdsourcing model designed to allow short cycle work to be accomplished through competitions within various crowds

12

Page 13: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

IBM’s GenO (Generation Ocean) initiative recognizes and leverages the talent of the ‘Gaming Generation’.

13

Page 14: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Most Common Types of Competitions

14

Page 15: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

GenO Liquid Portal supports training, registration, event launches, event monitoring and billing – synchronized with the TopCoder platform

15

Page 16: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Key Success Factor – Digital Reputations (Blue Cards)

16

Digital reputations of whole Communities and Professionals

fuel action.

Focus and Insight

The strategy of building a digital reputation resonates with our professionals and Communities worldwide.

Our people look for opportunities to differentiate their performance based on value rendered

Talent management programs need to incorporate appropriate recognition. Research shows that the ‘new

millennial generation’ wants frequent feedback on performance

IBM’s transformation incorporates a variety of recognition programs – at the Community, Country and Global level. Peer recognition within Community is one

example.

Page 17: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Blue Cards permit professionals to catalogue their results throughout the year

17

Achievement By Role

Deliverables Summary

Blue Card Calculator

Tag Cloud and Community Network

Page 18: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Crowsourcing flow diagram

18

Distributed problem-solving and production model

Problems are broadcast to an unknown group of competitors in the form of an open call for solutions

Outcomes based approach to obtain the best solution

Page 19: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Clouds are an enabling technology for running Liquid competitions.

19

Each competitor accesses a virtual machine (VM) inside the cloud to perform their work

Project teams can provision and de-provision the VMs required for each competition

Custom VM templates can be created for an application’s needs

Benefits:

1. Provides competitors with tools and environments they would not otherwise have

2. Reduces need for project teams to provide installation / setup instructions for each competition

3. Reduces time required by competitors to setup their environment

Page 20: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Liquid features a community network and governance structure to improve fluidity and productivity

20

Page 21: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Best Practices / Lessons Learned

Crowd sourcing for application development / testing is not for everyone – For IBM it is just one aspect of our GenO program

It needs structure – Portal, Virtualized Development Environment, Workflow, Collaboration Tools

Tasks need to be well defined – Good instructions, access to on-line resources (wiki, blogs, chat rooms etc,), structured contests, good communication

Need metrics to measure progress – Freecycles, Component Reuse, Assets Posted, etc.

Need credentials to gauge quality of resources - (e.g. Blue Card)

Need incentives (recognition) to foster its use – Blue Card metrics tied to performance-based pay and bonuses; managers performance metrics tied to use of crowd sourced resources

21

Page 22: © 2010 IBM Corporation Effective Community Collaboration: - lessons learned from IBM’s internal crowd-sourced application development and testing Dr. Fred.

© 2010 IBM Corporation

Dr. Fred Collins Ph.D.

Chief Architect - IBM Federal Lands

[email protected]

303-324-8790

Contact Information