IDU3390

IDU3390 - Information Systems Project Management

Official description of the course: link

email: kumlander @ gmail . com

2010-2011

Announcements

Exam

I am depressed by the exam results and very much regred that practically nobody attended Karin lectures and tried to understand and memorise all lectures publish on the main page

Just to clarify what I would expect you to write:

  1. Scope planning:
    1. In scope planning we must ...
    2. Product scope, Project scope.
    3. Project scope includes ...
    4. Scope planning steps
    5. Vision, Goals, requirements and definition of those
    6. Requit´rements: purpose, functional/none functional requirements
    7. Risks
    8. Project scope consist of ...
    9. WBS
  2. Change management
    1. Types of change
    2. Sources of the change
    3. Change control system
    4. Scope control
    5. Change Request (!!!!)
    6. Implementing the change we should consider
    7. Agile principles in Change Management
At the same time I did a step toward you and have divided now my expectations by 4, once again considering that you are not IT people (alghough management principles are similar everywhere), and put you (marks) at least two times more than I would do in normal circumstances. I am more than sure that everyone of you can do much more as all of you are intelligent and clever people and hope that it will not affect too much quality of education you get from our university.

Now you do have the following options: a) accept results, b) properly prepare and redo it one week later (then you should inform me no later than tomorrow, so I will remove that from the today exam list) or redo it in August or later

Presentations

The presentation should be: standard: 15 minutes, minimum 10 minutes (if less then it is rejected)

2011-02-20: Current task

1. Find a project you will be building a project plan for (somekind information system)

2. Find a topic to present write an essay and present during exercise hours (15 minutes): either an article or a presentation.

Lectures



Exercises

RULES

DEADLINES

Notes

If you are connected to any project in your professional life then you can use (develop) it unless it contains any private or confidential information. The project can be either building an information system (software) or changing an existing one.

A project documentation should be created using: plan - MS project (or similar software), other documents - any word processor (for example MS Word) - here we expect first of all textual information. Pictures and drawings are welcome, but those are not obligatory except, may be, the spec for the information system.

Results

2011

Presentations

The presentation should be: standard: 15 minutes, minimum 10 minutes (if less then it is rejected)

2011-05-17: Kadri Soosalu, "Agile in Waterfall Enterprise"
2011-05-17: Al-Emran Ahmed, "The Role of Testing and QA in Agile Software Development"
2011-05-17: Gennadi Jakutin, "Project Management for Distributed Teams"
2011-05-17: Shojib Mahabub, "Product Backlog"
2011-05-17: Habibur Rahman, "Scaling Agile To Work With Distributed Teams"

2011-05-10: Kerli Tarkin, "The project management fundamentals and its main mistakes"
2011-05-10: Mirjam Padar, "Project failure reasons and main factors"
2011-05-03: Ain Ellam, "Why Agile Development sometimes fail"
2011-05-03: Annike Koorts, "Kanban and Scrum: making the most of both"