Goals for FY2002

Abstract Goals (as set at performace review)

Academic Computing:

DSpace:



Specific work deliverables:

I plan to divide my time between the 5 areas below working on the tasks associated with them. The tasks are listed in order of roughly decreasing priority.

DSpace:

  1. Act as liaison if there are problems with IS infrastructure. (This role shrinks over time as snags become fewer.)
  2. Attend at technical meetings (Weekly DSpace meeting, and various design reviews held through the year.) -- DONE
  3. For the following areas, review issues, requirements, designs, and implementations. Write critiques. Propose appropriate changes.

Academic Computing:

  1. Lead Athena UNIX Platform Team -- DONE
  2. Participate in strategy setting and architecting of the evolving 1 to 1 computing model. -- PROGRESS
  3. Visit computing facilities of sister schools and produce critiques that describe similarities and differences in customer base, services, and infrastructure. Identify areas where we can learn. Suggest where we have something to offer. -- DELAYED
  4. Keep informed of the ongoing status of the HP infrastructure project. Look for synergies with our expertise, and needs. Identify possible areas of conflict with an eye to preventing or resolving them. Produce critiques. -- PROGRESS

Champion Athena Unix:

  1. Produce web page that presents the Athena vendor and infrastructure requirements. -- PROGRESS
  2. Produce web page that states CNboot status and issues. Work at Sun liaison to resolve the issues. -- DONE
  3. Review costs and benefits of Athena way. Produce white paper. -- PROGRESS
  4. Respond to Sun overtures to create Commercialized Athena through Sun. See that appropriate discussions with appropriate people take place to determine if this is a project we should pursue. -- DELAYED
  5. Respond to queries about Athena Model -- PROGRESS

Lead Athena UNIX Platform Team:

  1. Perform ongoing planning, resource analysis, and resource allocation in cooperation with Delivery Council. -- DONE
  2. Produce monthly status reports. -- DONE
  3. Produce web pages, memos, meetings, and perform other outreach to make the work/workings of the team visible/transparent. -- DONE
  4. Mentor team members personal and professional growth. -- PROGRESS
    1. to be happier and more effective.
    2. to align with MIT
    3. to be more entrepreneurial.
  5. Maintain the Athena UNIX Platform Team projects page. -- DONE
  6. Take certain specific roles for certain specific projects (in order of decreasing priority):
    1. Hardware Diversity: Mentor amb's leadership, and choice of tasks. -- DONE
    2. Open AFS: keep abrest of the situation and keep stakeholders up to date on status. -- DONE
    3. Star Office: contribute a couple hours a month to performing project tasks.
      • make APSE discovery status explicit -- DONE
      • revise APSE project pages -- PROGRESS
      • Periodic check in on Sun Star Office product status. -- DONE
      • Periodic check-in on OpenOffice.org status. -- DONE
      • Occasional outreach to Sun and OpenOffice.org. -- DONE
    4. Win32 on Linux: Take this to Discovery council, and find out if it is to become a real project. If so, help get it started with a bona fide sponsor, leader and resources. -- PROGRESS
    5. Disconnected Operation: Take the role of champion of this effort. Evolve it into an appropriate role for the Athena UNIX platform team for 1 to 1 computing. -- PROGRESS
    6. AUI follow-ons: See that appropriate sub-projects are identified, taken to Delivery Council, and acted upon as Delivery Council dictates: as tasks performed by release team. by creation of a project team to do the work, or decision NOT to do anything. -- DONE
    7. Netscape 6: keep informed of Todd Belton's ongoing status in doing this work. -- DONE
    8. Kerberos Package: keep informed of Miki's ongoing status with regards to this work. -- DONE
    9. AFS Package: keep informed of the status of this work. Possibly find someone to do it. -- PROGRESS
  7. Make sure team complies with Jim's Enhancing Customer Communication Competencies (EC3) directive. -- DONE

Other:

  1. Personal Change work: -- SIGNIFICANT PROGRESS
    (Goals: less anger, more calm, more satisfaction, fewer dead ends.)
    1. Practice accurate and affirmative description -- DONE
    2. Practice objectifying hot buttons -- PROGRESS
    3. Practice exploring new opportunities. -- PROGRESS
  2. Eliminate Mixed messages
    1. review teamhtml/service.html -- DONE
    2. revise cnboot.html to be more pleasant -- DONE
    3. organize Vendor html files -- DONE
    4. add links to Tests dir -- DELAYED

Goals Archive


Last updated: $Date: 2002/03/06 00:22:30 $ by $Author: wdc $.
Bill Cattey <wdc@mit.edu>