A webinar given jointly by MarkLogic, Aberdeen Group (research), and empolis summarized where the industry stands on the move toward offering users dynamic technical content -- dynamic in the sense of filtered for their needs and assembled into useful printables. The dimensions for filtering are the usual suspects: user skill/type, context (such as a specific product), and task type (setup vs. operation vs. troubleshooting). Aberdeen's research on current industry practices (albeit focused on the needs of manufacturers) showed they are being driven by these factors (most to least): speed to market, market segmentation, customizability, precision (need to cut irrelevant doc), and globalization (localization needs). Those organizations found to be "best in class" are pursuing these types of initiatives:

the customer is using i15, eCM and .net template with web components. they would like to use e-community as well. has anyone installed e-community in this environment yet?

Here’s an interesting project to keep an eye on – a collection of case studies of "how nonprofits and social change makers are using social networks to get the word out and inspire action."

socialmedia4change.pbwiki.com

It's a wiki, so anyone can contribute their examples to the pages. The Frozen Pea Fund is there, as well as a Second Life scavenger hunt for the Multiple Sclerosis Society.

I’ve added a page to IC for recording details of release schedules for software used by iMIS – for example the next versions of Microsoft SQL Server or Microsoft Office.

http://www.imiscommunity.com/microsoft_and_other_vendor_software_release...

If you come across any information on release schedules for products that we use or integrate with can you update it here.

customer would like to change the sort order of the display when doing a product search. we are using i15.0.3 and eCM. the current sequence looks random.

i would like to change the left nav bar for the system setup tab on the desktop. i can't find the html file which has it. does anyone know where it might be or is it hidden so it can't be changed.

This STC 2008 session shared the processes and tips used by NetIQ writers, who straddle multiple sprints and products.

Terms:

• Scrum = agile development approach that emphasizes close communication through daily stand-up meetings.
• Scrum master = team member who facilitates scrum meetings, communicates outside the team, and works to solve blocks.
• Iteration = 1-4 week stretch during which a full software development cycle occurs; begins with planning and ends with a demo.
• Backlog = repository for all requirements and wish list items. (tool to manage tasks = Xplanner)
• Capacity = maximum amount of hours a team member can work during one iteration.

No more specs:

This STC 2008 session by Daniel Wroblewski of SAP Israel introduced writers to API documentation, and he offered this minimalist approach to structuring it:

• Introduction (1 page)
• Who needs this
• What can I do with this API (main use cases)
• How guide is organized
• Quick Tutorial (1-2 pages)
• “I want to see it working”
• How to install or reference
• Concepts (2-3 pages, more if needed)
• Reference
• List of all APIs (e.g., Document! X, Javadocs)
• Other lists (syntax, types of windows, packages …)

Common goals of API users:

This STC 2008 session by Jane Bozarth offered alternatives to the methods taught in academic settings and techniques for persuading stakeholders to reconsider their demands and assumptions. Here are my key take-aways:

• Needs analysis on a napkin: assign performance problems to four quadrants, axis "wants to" versus axis "knows how to", low and high:
• doesn't want to + doesn't know how to = change job position or fire
• doesn't want to + knows how to = motivation issue
• wants to + knows how to = remove obstacles (bad process, bad management, etc.)
• wants to + doesn't know how to = TRAINING will help here, and nowhere else!
• Task analysis on a napkin: to find the critical 20%, draw a set of 4 concentric rings:
• Outer ring: call it "Everything about the domain"
• Next ring: call it "What we have time to teach"
• Next ring: call it "What learners will be able to recall"
• Inner ring: call it "What learners will be able to use"
• Mark the inner ring as 20% of all possible content, and ask the SME what few things should go in that inner ring.
  

This STC 2008 session reported findings of an STC-funded study of distance education and a case study for producing online courses from nothing (no materials or experience). The first study (by Rensselaer Polytechnic and New York Life) offered concrete tips for improving distance learning:

• Tag team: Use a course host/MC for every class, to set up, manage chat channels, direct group exercises, and record/archive, offloading the instructor.
• Plan for pain: Expect a third of the problems to be technical (media technology) and another third to be poor use of interactive channels.
• Control eyeballs: Best results come from 100% participation, by preventing/discouraging multi-tasking.
• Be fair: Use round-robin technique to ensure onsite and remote participants are equally involved (fear also heightens attention).
• Use the best: Use media in this order of effectiveness (ease and reliability): conference call (best), video conference, chat, whiteboard.
• Avoid all-in-1: Tools that bundle teleconferencing with video and more prove unreliable; move voice to Skype or similar, and push video to YouTube or similar services.
• Peer power: Seek technology that makes it easy for learners to help each other and interact -- it's effective and they want it.

The case study shows how Credence System jumped into remote learning, to meet customer demands for training when and where they need it. They tackled it with risk-management in the driver's seat: