Your SlideShare is downloading. ×
0
Doing More with  Less
Doing More with  Less
Doing More with  Less
Doing More with  Less
Doing More with  Less
Doing More with  Less
Doing More with  Less
Doing More with  Less
Doing More with  Less
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Doing More with Less

706

Published on

Presentation for Maricopa's 2011 Teaching and Learning with Technology Conference, by Ben Archer, Victor Navarro, and Mark Schufletowski.

Presentation for Maricopa's 2011 Teaching and Learning with Technology Conference, by Ben Archer, Victor Navarro, and Mark Schufletowski.

Published in: Education, Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
706
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Doing More with Less<br />A case study in technology process improvement<br />
  • 2. Project Overview<br />Project Background<br />Challenges<br />Previous project (’99)<br />Key Business Processes<br />Pilot<br />
  • 3. The 4 P’s of Team Makeup<br />Including key stakeholders is essential<br />Process requestors<br />Problem customers<br />Programmers<br />People who execute the work<br />
  • 4. Process Improvement Demo<br />
  • 5. Sample Process 1: New Employee Setup<br />Business problems:<br />Too many handoffs<br />Time to completion<br />Dropping the ball<br />Communication &amp; transparency<br />Process defines the tool<br />Custom Remedy workflow<br />People problems<br />Get as close to agreed-upon process as possible<br />
  • 6. Sample Process 2: Course Software Request<br />Based on faculty liaisons for individual rooms<br />Not scalable<br />Problematic for rooms shared by divisions<br />Software not removed<br />Major pain point for semester startup<br />Based on linking courses to software needs<br />Extremely scalable<br />Automatically handles shared rooms<br />Software can be flagged for removal if not used<br />Will auto-update for new sections, class room moves, etc.<br />Old System<br />New System<br />
  • 7. Lessons Learned<br />Define business problem(s)<br />Process defines the tool<br />You can’t solve people problems with processes<br />Get as close to agreed-upon process as possible<br />
  • 8. Summary<br />Customer and stakeholder involvement<br />IT is a customer-centered service<br />ITIL<br />People/Process/Tools<br />Organizational Process Analysis Team<br />
  • 9. Get more at: techfest.weebly.comQuestions?<br />

×