IT Management




Supervision of the IT Department

Priorities

Supervision generally focuses on the following key priorities:

Tasks

IT Supervision includes, but is not limited to the following tasks:
see:CategoryManagement for additional Management training

IT Project Management Guidance

Project Management Guide
Time and Task Management Guide
Template Phases of Web Projects


2014 IT Operations Audit with comments

Known Issues


General Recurring Issues


Inadequate Staffing (historically)
The rate at which our programs and processes have changed, expanded and improved over the years has not kept up with IT staffing. We have been operating at a staffing deficit in IT for years, and a backlog has accumulated. Due to the large learning curve in IT, staff turnover impacts them greatly, and IT interns are often a performance negative to the department.

Cross-Departmental Challenges
Other departments are largely dependent on IT. Without established communication channels, IT would be constantly interrupted and their time to actually resolve these problems would be minimal. Even with the channels set up, this can still be an issue, which tends to increase with the amount of people we have in the office. Reporters of issues tend to overestimate the priority level of the issue they want to be resolved. Some IT staff can be overly accommodating with staff on low-priority issues, which ultimately leads to burnout or sacrificing higher-priority tasks. Because of the volume of inputs that IT inevitably deals with (between mantis tickets, automated notifications, emails, etc.) it is easy for high-urgency items to be missed if they are only submitted as an email or mantis ticket. Thus, high-urgency items should be communicated through multiple channels (gchat, verbally, etc.).

Expectations and Results
Oftentimes election-cycle projects are not initiated until late in the cycle, causing an unexpected crunch time which then competes with other priorities. Also, we have had difficulty defining measurable goals for IT, expressing or demonstrating progress in IT to non-technical audiences, and marketing IT progress in nice packages for fundraising purposes.


Timelines
Past projects we’ve undertaken have suffered from inaccurate timeframe estimates and missed deadlines. Part of this is the inherent difficulty in determining how long IT projects will take, because unexpected challenges while arise with any new project. “Scope creep” (the scope of the project changing and increasing after original estimates for the project is given) is another common issue and is related to inadequate initial requirements. Drifting requirements and the fact that we generally get feedback from higher-ups only at later stages can also produce a hiccup near the end of the project.

Project Management
Many problems with previous projects may have been prevented or resolved better had there been a clearly-established, proactive project manager. Working with external consultants has been particularly challenging, because it requires lots of communication, greater-than-expected needs from internal staff, and managing a lack of understanding that external providers have. These external providers tend to give unrealistic deadlines which they then miss by a long shot, but we have little control over helping get it back on track by the time we figure that out.

In practice, the National Director has historically provided some project management functions, but this it is not sustainable to expect the National Director to perform day-to-day project management functions in light of other responsibilities. It is often not practical for IT staff to perform day-to-day project management functions in light of other responsibilities, and is often not the best match or best use of IT staff skillsets. Vote Smart is not currently equipped to provide training that in itself will prepare staff for Project Management responsibilities.

General Recurring Issues


Hiring and Retention

Staff Development

Cross-Department

Expectations and Results


Timelines

Requirements

Project Management

Upcoming Issues

Institutional Knowledge

Staff Resource Levels


Critical Operations

3 Staff members is the bare minimum the IT Department must have to sustain some critical operations: a Director, a Sys Admin/Dev Ops, and a Full Stack Developer.

Priorities

Impacts
By focusing only on high priority tasks, we will add to the backlog of low and medium priority tasks, and have limited time to devote to other projects. The pace of work on external projects will seem excessively slow; perhaps three times slower than expected, due to high-urgency interruptions. We would also rely on workarounds and short-term solutions rather than long term solutions which would be a net benefit.

Risks

Well-Functioning

A well-functioning IT Department requires approximately 4-5 total staff members covering general operations, plus additional staff may be needed for special projects.

Additional roles to those listed above include a Database Specialist.

Growth-Oriented

Any staffing above and beyond our “well-functioning” staffing needs would permit us to test and implement new ideas and focus more on long-term investments in our infrastructure.



CategoryITInfo
There are no comments on this page.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki