The document discusses end-user development, where users create tools and applications to meet their own needs rather than relying on IT departments. It provides examples of mashups, plugins, and databases created by end users. It also outlines reasons for and against end-user development, as well as tools, techniques, and best practices for supporting this type of grassroots computing.

1. Local information management: The end-user revolution Jean Graef The Montague Institute Jean.graef at montague.com (413) 367-0245

2. Agenda What is “end-user development” Examples Why do it? How to do it Tools & techniques Implications for info pros

3. What is it? Amateur computing in a business setting Alternative, not replacement, for other strategies

4. It’s not new 1979 1985 1990 1994 2001

5. Mashups

6. Public APIs

7. Database: Three sources 1 2 3

8. Blogs

9. Plugins/Extensions

10. Who does it? University staff Field scientists Telecommuters Anyone with aptitude, desire, lack of access to IT resources

11. Why do they do it? They can More knowledgeable Instant help on the Internet Free or low cost downloadable “widgets” Tools are easier to use, more sophisticated

12. Why do they do it? Users more assertive and vocal There are more like me My time is valuable My needs are unique IT has no time for me

13. Why do they do it? Limitations of current approaches Lack of user involvement causes IT failures User requirements hard to define in advance Too much spent on “change management” % of adopters is too small

14. Why do they do it? Proprietary solutions decay over time Lost features Incompatibilities No support

15. How to do it End user development vs. “waterfall method” User-initiated vs. usability studies Prototyping vs. functional specs “Cheat sheets” vs. user manuals One-on-one training vs. formal courses Definition > Analysis > Design > Coding > Deployment > Maintenance

16. Tools & techniques Databases Plugins, extensions, macros Freeware, shareware Commercial services

17. Databases Search engine thesaurus (XML) Search engine search from thesaurus (calculation) Site contents (text processing/import)

18. Search engine thesaurus

19. <set> <show>indexes</show> <show>linguistic tools</show> </set> Thesaurus.xml Search engine thesaurus

20. http://www.montague.com:8765/query.html?col=public&qt=indexes&charset=iso-8859-1&image.x=0&image.y=0&image=+search+ Thesaurus search

21. Web site contents

22. Plugins, extensions, macros Text processing (Word) Custom metadata (Word)

23. Text processing

24. Custom metadata

25. Freeware, shareware

26. Commercial services ProQuest (import metadata) Factiva (Sharepoint Web part) Amazon (Federated search)

27. Import metadata

28. Sharepoint Web part

29. Federated search

30. Commercial application iRise Studio Application simulator Starts at $250,000 Reduce rework costs Reduce time-to-market Customers: Agilent, Wachovia, Watson-Wyatt

31. iRise Studio

32. iRise Studio

33. iRise business case

34. More savings What if Web application saves $20 per user, but only 28% use it? 100,000 x .28 = 28,000 x $20 = $560,000 savings 100,000 x .80 = 80,000 x $20 = $1,600,000 savings

35. Mentored development Montague Institute courses Project-oriented Theory + Lab Interdisciplinary teams See how your data behaves Information modeling with custom Lab Written specifications Implementation

36. On the other hand Users lack the tools Users lack training & help Code & data can’t easily be reused Lack of quality assurance & data standards

37. How to support them New business model Communities of practice Standards Interfaces

38. materials architect land financing craftsmen schedule Contractor model

39. Marketplace model

40. Marketplace model Project ideas Special interests (wood projects for gardens) Buying guide How-to guides Interactive planners “Green” & healthy tips

41. Tips Communities of practice + written reference tools Allow time for development activities Recognition & incentives Segment the “market” Professional vs. amateur “ Agile” programming http://agilemanifesto.org

42. More tips Cultivate “boundary spanners” Focus on the gaps Data normalization & transformation Application integration Inter-departmental workflows Target the business unit manager Speak business, not technology

43. “ Lite” support practices Software versions, embedded comments, non-technical “cheat sheet” Searchable support KB for each developer Data cleanup services Use cross-platform development tools Make test files and computer available

44. More info Montague Institute Review http://www.montague.com/review/review.html