(TRP) Turban, Efraim, R. Kelly Rainer, and Richard E. Potter. 2003 Introduction to Information Technology. 2^nd edition, New York: John Wiley & Sons, Inc.

(BG) Barrett, Katherine and Richard Greene. 2000. Powering Up: How Public Managers Can Take Control of Information Technology. CQ Press ISBN:1-56802-575-0

Heeks, Richard. ed Public MIS papers (1-9) www.man.ac.uk/idpm/educisps.htm

Additional resources:

For sample technology plan http://www.artswire.org/spiderschool/workshops/kit_buffalo_01/elements/index.html

Technology Plan Template http://www.rmcdenver.com/eetnet/tem.htm

TechSoup – The Technology Place for Nonprofits http://www.techsoup.org/index.cfm

Web use and site evaluation: http://www.helping.org/nonprofit/evaluating.adp , www.cyprg.arizona.edu

Site for nonprofit IT architecture:

NIST’s Security Self-Assessment Guide for Information Technology Systems (look through http://csrc.nist.gov/publications/nistpubs/index.html )

A project of the New York Foundation for the Arts site offers online workshops for nonprofits. http://www.artswire.org/spiderschool/workshops/agendaplanning.html

Verizon gateway site for nonprofit tech info: http://foundation.verizon.com/08006.shtml

Small Business Association’s NonProfit site, http://www.sba.gov/nonprofit/

Sites for public organizations:

Center for Technology in Government (mainly US) , www.ctg.albany.edu/

Federal Computer Weekly and Civic.com magazines plus Government CIO summit covering IT in government (mainly US) , www.fcw.com/

Government Technology magazine covering IT in government plus other resources (mainly US) , www.govtech.net/

International Council for IT in Government Administration , www.ica.ogit.gov.au/

IT case studies in US local and state government , www.excelgov.org/techcon/sldoc/index.htm

National Partnership for Reinventing Government (US) , www.npr.gov/

Note: if necessary, in course corrections to syllabus will be posted online at www.u.arizona.edu/~demchak/pa502.htm

Course Description:

This course is designed to integrate public and nonprofit organizational issues with the demands and opportunities of information systems. In this course we will emphasize hands-on MIS in a nonprofit or public setting. The course will have three intertwined components: an intensive overview of general MIS terms and tools in private and public agencies, analytical exercise in constructively (both in print and in presentation) critiquing a public or nonprofit organization using available information systems and a knowledge of organizational structures and processes, and finally discussion of existing and emerging wider public policy issues that will influence the future conduct of public and nonprofit MIS.

Major Course Requirements:

In this course, you must prepare a task force report constructing a nonprofit organization (NP) effectively using IT, contribute to an online computer conference as directed, participate in class, and perform adequately in reinforcing quizzes at the outset of the course. These requirements are outlined in detail below.

A. In a task force, you will jointly produce a written report constructively critiquing the design of several new or existing public or nonprofit organizations, looking specifically at their information technology (IT) architectures and speculating possible application choices. Each report will have one appendix per person and each appendix will discuss a particular case study organization. The joint section will look over all the case studies for lessons to be applied to other public or nonprofit organizations. The focus in the appendices will be on the background and possible IT difficulties and opportunities found each organization. In the appendix process, you will discuss the actual organization in terms of its mission scope, organizational chart, and IT or effectiveness history. At the end of the appendix, each author will make some recommendations about using MIS applications. The focus in the joint section will be on possible solutions for these organizations and across the board lessons learned. This requirement is worth 40% of the grade with separate grades allocated for each appendix and the joint section. Details about the final requirement are found at the end of the syllabus.

B. Display command of the required material by participating on the course computer conference on CAUCUS (PA502s03PNPMIS) once a week. This requirement is worth in total 30 percent of the grade.

1. By the beginning of the first FULL week of classes, each student will join Caucus for this course, the GovPub listserve (GOVPUB@LISTSERV.NODAK.EDU), and the free email sections of Wired News (www.wired.com/news). Also, noted above are several websites with information on public and nonprofit experiences with IT. Government Technology is highly recommended. For your information, there are also many online business reference services that can also provide complementary IT information.

2. Each week of the course, we will cover several chapters in the text and 1-2 online papers or case studies. Each week in a single consolidated entry to Caucus, each students will do as directed in the syllabus: Each student will also comment on a previous student's submission whether or not it is noted in the syllabus.

3. I will not participate directly in the conference but I will read each week’s conference. Only at the end of the semester will I download and evaluate all the submissions from each student for both frequency and quality. I will not be able to tell you how many times you have contributed until the cumulative rollup at the end of the semester.

C. Display command of the required material by participating as required in class and by using applicable library time as intended. This requirement is worth 10 percent of the grade.

1. In general, roll will be taken in scheduled lecture days. If the course registration is small enough, I will do this in my own notes without calling on anyone.

2. Whenever students are required to meet in task forces, they are not required to meet in the classroom other than the first few meetings. However, task force members MUST meet with each other during class hours. Each task force must appoint a point of contact who will send by the following Monday a message to the teaching assistant with a brief discussion of what occurred during the previous week's task force library research period and who was present on those days. Failure to attend meetings or misrepresentation of attendance will count against the final class participation grade.

3. Bring the books to all class meetings. You are responsible for both knowing the readings for the week and being familiar with the articles uploaded by your colleagues.

To achieve a passing grade, you must fully participate in class discussion, task force activities, and have adequately participated in the computer conference in at least 60 percent of conference sessions.

D. Successfully complete in-class quizzes. The quizzes are NOT intended to be discriminators but rather reinforcing tools. The questions will be multiple choice and will consist of questions directly taken from the text with few exceptions. The questions will emphasize commonly used definitions and relationships, not minute details. Each quiz will cover material studied since the previous quiz. This requirement is worth 20% of the final grade; each quiz result will be weighted proportionally. Quizzes will be weekly for as long as we are reading the Turban book.

At the end of the syllabus is the grading scheme used for all evaluations of written work and participation.

Reading Assignments:

(all Caucus assignments must be in by 2200 Monday AND bring course book to all class meetings.

16 JAN Intro Class

Introduction to Public and NonProfit Management and MIS

Thursday: Introduction to Pedagogic goals, Syllabus, Computer Caucus, Task Forces, Conduct of class, Web research, Admin

Reading: none

*** Admin: SUBSCRIBE TO CAUCUS conference BY NO LATER THAN next Sunday and submit the first week's response no later that 10pm Monday 20 January. You must have a UA CCIT account to get access to this site. Use a browser to go to the CAUCUS home site http://caucus.arizona.edu/ and “join” our conference (PA502s03PNPMIS). Note that each week has a topic. You will respond to the question listed in the syllabus under that week. You will submit material required by 2200 every Monday before the assigned class. See the in-depth instructions in Requirements above. Note that each week has a topic. Put the week number in the subject heading of all your caucus entries. Late entries are accepted only on a case by case basis. I will not participate in the conference but I will read each week’s conference. At the end of the semester, I will download and evaluate all the submissions of each student for both frequency and quality. After 28 January, our conference will NOT be on the list of conferences to click (it will be unlisted).

NOTE: Do NOT submit CAUCUS submissions as attachments! Always write them offline and paste them into the Caucus site.

21 JAN Week 1

Organizations, Political Environments and Information Technology

Tuesday: Class discussion

Thursday: Class discussion

Reading:

TRP, chaps 1-2.

BG, chaps 1-2

ISPSM 9: Why Health Care Information Systems Succeed or Fail, Richard Heeks, David Mundy & Angel Salazar (http://www.man.ac.uk/idpm/isps_wp9.htm)

Computer Conference (Caucus) –Comment on what surprised you in these readings and what you feel was useful to jot down for future consideration.

28 JAN Week 2

Software, Hardware and IT Infrastructure

Tuesday: Class discussion

Thursday: Class discussion (We will formally assign task force members on Thursday.)

Reading:

TRP, chap. 3-4

BG, chaps 3-4

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

04 FEB Week 3

Managing Organizational Data and Legacy Systems

Tuesday: Class discussion

Thursday: Class discussion

Reading:

TRP, chap(s). 5.

BG, chap 6

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

11 FEB Week 4

Telecommunications and Networks

Tuesday: Class discussion

Thursday: Class discussion

Reading:

TRP, chap(s).6

BG, chap 5

ISPSM 8: Information Management, IT and Government Transformation: Innovative Approaches in the New South Africa , Michael Kahn & Russell Swanborough, (http://www.man.ac.uk/idpm/isps_wp8.htm )

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

18 FEB Week 5

Internets, Intranets and Extranets

Tuesday: Class discussion

Thursday: Class discussion

Reading:

TRP, chap(s).7

BG, chap 12

ISPSM 2: Planning and Creating a Government Web Site: Learning from the Experience of US States, Linda DeConti (http://www.man.ac.uk/idpm/isps_wp2.htm )

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

25 FEB Week 6

Task Force Research

Tuesday: Task Forces meet in course classroom

Thursday: Task Forces meeting

Reading: none

Computer Conference (Caucus) -

ADMIN: during this week, task force members will meet during class hours in the classroom to discuss their case study organizations.. Be sure to have each person send an email to the TA noting when you met and what was accomplished. You will individually send this email each week during this task force period. No excuses for absences will be accepted without medical or emergency certification.

No office hours this week.

04 MAR Week 7

Enterprise-Wide and Interorganizational Systems

Tuesday: class discussion

Thursday: class discussion

Reading:

TRP, chap(s).8

BG, chaps 7, 13

ISPSM 7: Centralized vs. Decentralized Management of Public Information Systems: A Core-Periphery Solution , Richard Heeks (http://www.man.ac.uk/idpm/isps_wp7.htm )

ISPSM 5:Public Sector Mgt Information Systems, R. Heeks (http://www.man.ac.uk/idpm/ispswpf5.htm)

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

11 MAR Week 8

Supply Chains, Ecommerce, and Process Integration

Tuesday: class discussion

Thursday: class discussion

Reading:

TRP, chap(s).9-10

BG, chaps 8, 9

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

25 MAR Week 9

Data, Knowledge, Decision Support and Intelligent Systems

Tuesday: class discussion

Thursday: class discussion

Reading:

TRP, chap(s).11- 12

ISPSM 3: Decision Support Systems and Strategic Public Sector Decision Making in Egypt, Sherif Kamel (http://www.man.ac.uk/idpm/isps_wp3.htm)

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

01 APR Week 10

Strategic Information Systems and Reorganization

Tuesday: class discussion

Thursday: class discussion

Reading:

TRP, chap(s).13

BG, chaps 10-11

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

08 APR Week 11

IS Development, Ethics, Effects and Security

Tuesday: class discussion

Thursday: class discussion

Reading:

TRP, chap(s).14-15

BG, chaps 14-15

ISPSM 1: Information Systems and Public Sector Accountability. Richard Heeks (http://www.man.ac.uk/idpm/isps_wp1.htm)

ISPSM 4: IT and Public Sector Corruption, R. Heeks, (http://www.man.ac.uk/idpm/isps_wp4.htm )

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

15 APR Week 12

Task Force Research

Tuesday: Task Forces meet in course classroom

Thursday: Task Forces meeting

Reading: none

Computer Conference (Caucus)

ADMIN: during this week, task force members will meet during class hours in the classroom to discuss their case study organizations..Be sure to have each person send an email to the TA noting when you met and what was accomplished. You will individually send this email each week during this task force period.

22 APR Week 13

Presenting Options in Integrated Org-IT Designs for NonProfit Organizations

Tuesday: Class discussion

Thursday: Class discussion

Reading:

BG, chaps 16-17

ISPSM 6: Information Age Reform of the Public Sector: The Potential and Problems of Information Technology for India, R. Heeks (http://www.man.ac.uk/idpm/isps_wp6.htm )

Computer Conference (Caucus) - Comment on what you feel was useful to jot down for future consideration.

29 APR Week 14

Presentations of Task Force Results

Tuesday: Task Force Presentations

Thursday: Task Force Presentations

Reading: none

Computer Conference (Caucus) - none

NOTE: You must attend all presentations.

06 MAY Week 15 Course Review on Tuesday and possible participation grade return

Final Reports (paper and disk) due MONDAY 5pm McClelland 405GG (include both a paper version and a disk with the entire paper in one consolidated Word file entitled with each task force member's last name as in "lastname_lastname_….502s03".

Sign in both paper and disk.

Be sure to run a virus scanner on the diskette after copying the file.

Have no other files on the diskette. Files will be run through a plagiarization detection program. See policy on plagiarization in Grading section of syllabus.

Also, be sure to provide contact telephone numbers on the diskette in case of a problem reading it.

Every student will send the Instructor a private email evaluating the percentage of the work performed by colleagues on the team according to the following: organization of efforts, research data, write-up, and preparation of the presentation. These will be kept in strict confidentiality and will be reflected in a grade if there is a sufficient pattern by several students to merit such an adjustment. The adjustment will be taken off the taskforce joint grade.

No extensions are granted without an emergency situation.

--------------------------------------------------------------------------------------------------------------------------------------------------

TASK FORCE REPORT FORMAT REQUIREMENTS CHECKLIST:

1. The task force report must have a professional appearance with an executive summary, joint section, appendices, with the report clearly subdivided with subheadings, all charts and tables labeled and properly cited, and a bibliography. An executive summary presents the conclusions as well as a brief overview of the work itself. It should be very tightly written, as it is often the only thing an executive might have time to read. The presentation should be conducted using PowerPoint slides and, to the extent possible, broken up into segments for each task force member to present some portion of the work.

2. Cite all sources in the text using the format (Smith 1992:23) where the number 23 is the page in the citation. All key ideas, lengthy descriptions, data, and tables must be cited individually. If one source dominates a section, then cite it at the end of each paragraph. Normally one citation per paragraph is a minimum unless every idea, thought, and information is completely your own creation. Remember that just because three books have made a similar observation does not mean it is common knowledge. Those may be the only three authors in the world who know this item. A consistent failure to cite sources properly is a demonstrated failure to honor intellectual property rights and may be evidence of plagiarization. Cite all web sources in the text in the same manner; use some brief acronym in the text plus some identifying information from the bibliographic entry. Do NOT put the whole URL in the text citation.

3. Egregiously poor citations will result in a failing grade and plagiarization may result in both a failing grade and pursuit of a charge of violation of University ethics policy. Please note that copying whole paragraphs from another source and then simply noting the source without making it clear that this paragraph is a direct quote is plagiarization. There is no minimum…..one paragraph directly inserted without properly noting that it is a direct quote or a pattern of single sentences so "borrowed" are both plagiarization, as is taking an idea without duly noting its source.

4. A bibliography of ALL sources used is required. To be acceptable, it must indicate a thorough search in the literature for relevant works. ALL works in the bibliography must be cited in the body of the text. Because this paper is in lieu of a final exam, the text must integrate ideas from the course readings and, therefore, the relevant course readings must be cited in the text as well as listed in the bibliography. Cite all web sources as well using some acronym as the author, if there is no author, and any other identifying information such as any title, source noted on the web site, the URL itself [standard practice these days is to bold italicize the URL], and the date you downloaded the material.

5. Use neutral language at all times. Avoid "should" or "ought" until the recommendations section. Avoid global exaggerations like "everywhere", "all", etc. Always take the "me" and "I" out of the discussion to the extent possible. This personalization of the work makes it harder for the reader to give the work credibility.

6. Other administrative notes.

a. Length of work: this will vary with each team but an executive summary is a maximum two pages single spaced).

b. Do not right-justify any submitted work. That only works in narrow news columns.

c. Put all task force member names on the back side of the whole work and each individual appendix must have its author identified on the back side of the last page of the appendix. Do put your student ID numbers with your names. Put a contact telephone number for each task force - this person MUST be able to contact any other task force member quickly.

d. Page numbers are required in the upper right-hand corner of every page of text.

As of the end of the semester, your participation grade is the following. This assessment is based upon your contributions and submissions in class and your email submissions (both frequency and quality). Making key class meetings and regularly submitting requirements on time are required for a passing grade. excellent efforts in one area, however, may compensate for poorer performance in the other. See the end of the syllabus for an explanation of the grading criteria.

Participation Grade: _________

GRADING STANDARDS FOR ALL REQUIREMENTS

including participation

Paper standards are in italics.

MASTERY

A Dominates the material

[Good Thesis Statement, Good Argument, Structured well, Written well]

A+ Beyond the expectations of the course or specific requirement

A- Demonstrates some mastery of the material across most categories.

PROFICIENCY

B Demonstrates a good understanding

[Good Thesis Statement, Acceptable Argument (few fallacies, mostly clear),Structured well, generally written well]

B+ Excellent Performance in several categories

B- Demonstrates aptitude for the subject

PASSING

C Demonstrates passable but shallow understanding:

[Passable Thesis Statement, barely acceptable argument (fallacies, unclear), Structured generally, grammatically passable]

C+ Can build on this foundation

C- Limited and short-lived understanding

POOR

D Demonstrates extremely shallow understanding

[Attempt at a thesis statement, a story or history rather than argument, Some evident structure, grammatically poor]

F Demonstrates no effort or violates major requirements

[No thesis + Garbled story, embarrassingly poorly written, plagiarization or fraud in authorship, especially using quotes that are not labeled as direct quotes.]

NOTES:

Task Force Grades will be adjusted for contribution using peer-group and/or self-evaluations and the professor's judgment if the situation warrants.

"Domination" of the material includes displaying insight well beyond the mere accumulation of facts.

For the top grade, any assignments must be well organized, well cited, and comprehensive.

The participation grade is based on the intellectual contribution to the class and computer discussion in terms of clarification, insight, stimulation, original ideas, and attendance in the course. A passing grade of "D" requires at least 60 percent regular attendance and regular contribution to the class discussion. Attending all lessons but saying nothing merits a failing participation evaluation. Absence or failure to be prepared when your name is called for article presentation merits up to a 10 percent penalty in in-class participation evaluation.

Creativity merits reward if it demonstrates sophisticated insights and command of the material...up to one grade point per requirement.

Grade adjustments: The University of Arizona does not allow me to give plus or minus final grades although I prefer to grade with them in the course. Your final grade will be altered according to the full grade to which your calculated final grade is closest. Half point grades will be moved up; quarter point grades down. Those falling between X.30 and X.50 will be evaluated individually to see if moving up is justified on the basis of other demonstrated work.

No extensions will be permitted unless there is a demonstrable emergency and you have arranged the extension in advance.

Students who wait more than a week to inform the professor that a task force member has withdrawn are held responsible for the entire task force report with no adjustments for fewer people. No exceptions.

(TRP) Turban, Efraim, R. Kelly Rainer, and Richard E. Potter. 2003 Introduction to Information Technology. 2nd edition, New York: John Wiley & Sons, Inc.

(BG) Barrett, Katherine and Richard Greene. 2000. Powering Up: How Public Managers Can Take Control of Information Technology. CQ Press ISBN:1-56802-575-0

Heeks, Richard. ed Public MIS papers (1-9) www.man.ac.uk/idpm/educisps.htm

Reading Assignments:

(all Caucus assignments must be in by 2200 Monday AND bring course book to all class meetings.

Introduction to Public and NonProfit Management and MIS

Thursday: Introduction to Pedagogic goals, Syllabus, Computer Caucus, Task Forces, Conduct of class, Web research, Admin

Reading: none

21 JAN Week 1

Organizations, Political Environments and Information Technology

Thursday: Class discussion

TRP, chaps 1-2.

BG, chaps 1-2

ISPSM 9: Why Health Care Information Systems Succeed or Fail, Richard Heeks, David Mundy & Angel Salazar (http://www.man.ac.uk/idpm/isps_wp9.htm)

Tuesday: Class discussion

Thursday: Class discussion (We will formally assign task force members on Thursday.)

TRP, chap. 3-4

BG, chaps 3-4

Tuesday: Class discussion

Thursday: Class discussion

TRP, chap(s). 5.

BG, chap 6

Telecommunications and Networks

Thursday: Class discussion

TRP, chap(s).6

BG, chap 5

ISPSM 8: Information Management, IT and Government Transformation: Innovative Approaches in the New South Africa , Michael Kahn & Russell Swanborough, (http://www.man.ac.uk/idpm/isps_wp8.htm )

Tuesday: Class discussion

Thursday: Class discussion

TRP, chap(s).7

BG, chap 12

ISPSM 2: Planning and Creating a Government Web Site: Learning from the Experience of US States, Linda DeConti (http://www.man.ac.uk/idpm/isps_wp2.htm )

Task Force Research

Thursday: Task Forces meeting

Enterprise-Wide and Interorganizational Systems

Thursday: class discussion

Reading:

TRP, chap(s).8

ISPSM 7: Centralized vs. Decentralized Management of Public Information Systems: A Core-Periphery Solution , Richard Heeks (http://www.man.ac.uk/idpm/isps_wp7.htm )

Thursday: class discussion

Reading:

TRP, chap(s).9-10

Data, Knowledge, Decision Support and Intelligent Systems

Thursday: class discussion

Reading:

TRP, chap(s).11- 12

ISPSM 3: Decision Support Systems and Strategic Public Sector Decision Making in Egypt, Sherif Kamel (http://www.man.ac.uk/idpm/isps_wp3.htm)

01 APR Week 10

Strategic Information Systems and Reorganization

Tuesday: class discussion

Thursday: class discussion

Reading:

TRP, chap(s).13

IS Development, Ethics, Effects and Security

Tuesday: class discussion

Thursday: class discussion

Reading:

TRP, chap(s).14-15

ISPSM 1: Information Systems and Public Sector Accountability. Richard Heeks (http://www.man.ac.uk/idpm/isps_wp1.htm)

ISPSM 4: IT and Public Sector Corruption, R. Heeks, (http://www.man.ac.uk/idpm/isps_wp4.htm )

Tuesday: Task Forces meet in course classroom

Thursday: Task Forces meeting

Reading: none

Computer Conference (Caucus)

22 APR Week 13

Presenting Options in Integrated Org-IT Designs for NonProfit Organizations

Thursday: Class discussion

ISPSM 6: Information Age Reform of the Public Sector: The Potential and Problems of Information Technology for India, R. Heeks (http://www.man.ac.uk/idpm/isps_wp6.htm )

Thursday: Task Force Presentations

Reading: none

Computer Conference (Caucus) - none

NOTE: You must attend all presentations.

06 MAY Week 15 Course Review on Tuesday and possible participation grade return

Final Reports (paper and disk) due MONDAY 5pm McClelland 405GG (include both a paper version and a disk with the entire paper in one consolidated Word file entitled with each task force member's last name as in "lastname_lastname_….502s03".

Sign in both paper and disk.

Be sure to run a virus scanner on the diskette after copying the file.

Have no other files on the diskette. Files will be run through a plagiarization detection program. See policy on plagiarization in Grading section of syllabus.

Also, be sure to provide contact telephone numbers on the diskette in case of a problem reading it.

No extensions are granted without an emergency situation.

(TRP) Turban, Efraim, R. Kelly Rainer, and Richard E. Potter. 2003 Introduction to Information Technology. 2^nd edition, New York: John Wiley & Sons, Inc.