Friday, May 14, 2010
Project Documentation
Charter
Business Requirements
Project Plan
First Draft Screenshots
Thursday, May 6, 2010
momma's got a brand new bag
I am now in various states of implementation in 3 projects using "KP Ideabook" - a community of interest group for the administrators of the application I support, coordinating a 6 week UAT (user acceptance testing) group of about 40 people and a six disciplines of training follow-through tool for ongoing use through out the company. The last implementation will be replacing an expensive vendor tool (fort hill results engine). I will be re-writing my charter on the six disciplines tool - as it is leader sponsored and is going through the whole charter to implementation process in the next few weeks.
Wish me luck - charter to follow shortly.
Tuesday, May 4, 2010
crazy, crazy, crazy
I am integrating the tool as a "Community of Interest" for the administrators of my system, with interior subgroups for special teams - like Report Users and User Acceptance Testers. I will use these spaces as a part of our overall deployment/communication effort. "KP Ideabook" has discussion boards, blogging, document management(including collaborative documents) and mini project plan modules. I am in a rush to get the space ready for our first push this coming Thursday, when I will demo the tool for our large user community. Our go-live date is drawing near again (Sept 1st) and it looks like this time it is for real. As one of only two people set to deploy not only a system but training on that system to 3,000 users - this will be a godsend.
As well - there is a leader sponsored project to replace a costly vendor tool with a no cost solution. Web 2.0 to the rescue. I am going to use "KP Ideabook" for this project as well - although I will set the functionality and user interface to look and behave very differently from my User Community of Interest.
This thing is going to be put in place right away - and had I not taken this class - I would have never understood the possibility of this tool. Thanks Jun!
Wednesday, April 14, 2010
I work for a really big company (made up of large sub companies~ 180k) and the app I work on has to fit a really broad range of needs and be approved by a large set of clients. In some ways, it is really interesting to work at this level - a window on the training activity of the entire enterprise. My metrics are big, my reports have loads of users and I have a slew of "super user" clients.
In some ways - because it must meet so many requirements - it waters down and dulls some of the sharpest aspects of the software. There are whole suites of tools we bought we can not use, because they would not be scalable. In our enterprise situation, processes and decisions are made all or nothing - it must suit all or can not be done.
I recently hit my ten year mark at my company. I looked over my resume and saw that the first 3 years - when I was working with a much smaller audience (6k)- I really got a lot more done than in my past 3. When I started, the department was new and processes had to be built everywhere - we were making up our structure as we went along. Now, in a more mature orginization, processes are improved, tweeked, the possiblity to implement a suite of apps like 37 signals has passed me by.
I feel envy for all of you who say your team is just getting started down this path - you have so many cool new tools to use and platforms to build that will take you to the next step. Enjoy it while you can.
Sunday, April 11, 2010
obsessed with ancestry.com
AC is a SaaS model where I pay a monthly fee to access the database records. The actual platform – the user interface and application, is secondary to the massive data that AC has digitized and made searchable. My mind boggles at the undertaking - digitizing hundreds of years of millions of records – records commonly found in county file cabinets, yellowing bits of census journals with pen and ink handscript. Optical character recognition (OCR) allows searches against images of the actual documents – I can view my grandparents signature on their marriage license.
My original goal of creating a basic family tree with the view towards getting a better idea of “where am I from” has basically been answered. (Long story short – the four corners of PA, VA, WV, OH before they were states) The more time I spend on the tree, the more engrossing the whole process becomes. I built a base of ancestors back to 1700 (as far back as I care to go). As I searched and added family data from census and other information; I came against misspellings of names, duplicate records for a single ancestor, and changing city, county names (this came into play as the commonwealths become states and the mason-dixon line created WV from VA). As anyone who has created a db from scratch will tell you – data integrity is key (no pun intended!) and an obsession of it's own. I kept an eye to what seemed the most accurate of records.
Of course, as soon as I had my data set, I wanted to play with it. I wanted to do a timeline chart, a chart by birth months, a map of residences; I wanted to see the whole tree in it's splendor. As I mentioned above, AC as an actual application is pretty light with very limited ways to view my data and no reports at all to showcase my records. I began thinking of AC as my system of record and searched for a reporting tool to feed my need for metrics. The common file type for family tree software is GEDCOM and exports as a large text file with keyed records. I couldn't easily export the file to excel or access to create a home-brewed report, so I needed to find software that would integrate and allow me to manipulate my newly-culled family data.
I have downloaded a demo of MacFamily Tree and look forward to testing out the touted reporting tools. Although I have been able to gather this hierarchical net of family data, what I am missing is the narrative – the family stories that truly populate a family tree. Luckily – it looks like I might be able to find some family stories via google books. Isn't technology grand?!
As a note to myself - future topics for posts:
CMM, PCMM, and HRO
http://en.wikipedia.org/wiki/Capability_Maturity_Model
http://en.wikipedia.org/wiki/People_Capability_Maturity_Model
http://en.wikipedia.org/wiki/High_reliability_organization
Favorite fruit/what feeds employee engagement
Audience size is everything, integration
Hosted/Internal - service and support
Thursday, April 8, 2010
Charter - attempt #1
I really struggled with this charter - I was not sure where the line was between a proposal and a solution. Here is my first attempt.
Charter - LMS Catalog Cleanup
Problem Statement
The number one complaint against the Learning Management System is the course catalog is difficult to search. If learners are unable to locate training they will either open a help desk ticket or neglect to enroll and complete training. This compliant has escalated to the highest level of leadership. This issue is a major cause of mistrust/lack of buy-in of the LMS. (where can I find stats on time lost?)
Problem Details
The learning management system is enterprise wide and administered by regional training departments. The LMS is like a library in which any author can place his/her books on the shelves. The catalog search is made against course information, so clean and correctly tagged courses are key to a successful search. Administrators wish for their courses to be found - but are not always successful in understanding how to code the information correctly.
Customers
1. Learners
2. LMS Administrators
3. LMS Support Team
4. Learning Leadership
Business Case
(system agnostic)
(is this where I propose a solution?)
Create a series of course information audits (such as category, keyword, availability, course name, course ID, abstract, sponsoring dept, duration, domain, ce's, cancellation policy)
Trend existing course information to create a controlled vocabulary for keyword and category tags. Create a living taxonomy for course information.
Archive fallow courses.
Begin using existing description field for metatagging.
In Scope
Create a new set of best practices for creating courses. Changing policies, processes, training and job aids around course creation. Creating audit process to ensure practices are followed. (Is this too close to a solution?)
Out of Scope
Addressing the search functionality of the LMS. Saba owns the search functionality of the LMS. We can only address data/record issues.
Success Metrics
Reduced help desk tickets
Improved perception of LMS
(clean course information audits?)
Deliverables
Communication Plan
Communication of new policies, job aids, training and best practices
Training Plan
Revised training for administrators and learners
Resources
Functional/Technical
Enterprise Learning Services
Sponsors
National Learning Leaders
Core Team