projectmanagement
pdf
keyboard_arrow_up
School
The University of Sydney *
*We aren’t endorsed by this school
Course
1998
Subject
Information Systems
Date
Nov 24, 2024
Type
Pages
9
Uploaded by JudgeFlowerMongoose5
Project Management Summary
1
Project Management Summary
Created
Class
ipt
Type
Summary
Reviewed
Term
Term 3 2023
Communication Skills
Active listening
Eye contact
Repeating
Rephrasing, paraphrasing
Asking questions
Negotiation skills
Compromise
Interview techniques
Record it
Set of questions
Set up expectations
How long
What are we doing
Conflict resolution
Get to a point where we negotiate
Not everyone will get everything
Misunderstandings
Being unreasonable
@July 24, 2023 2:07 PM
Project Management Summary
2
If you don’t
Employment loss
Financial losses
Missed opportunities
Project Management Tools
Gantt chart
Scheduling of tasks
Who does what at what time
Journals and diaries
write down what they have done
Go back and look at accomplishments
If there was an error → check notes
Funding management plan
How much money do we spend on what
Budget
Communication management plan
How do we communicate with each other
Communicate within teams
Use email
Who do I contact for what
What time do we have a meeting
What do we discuss
What do we do for people that need to connect in remotely
Project manager
Head person
Runs project
Project Management Summary
3
Uses these tools to make sure it runs on time
Advantages
Increased productivity
Documentation throughout
Development of quality system
Social ethical
Open, honest good communication
Have documentation to show when decisions were made
Fair and balanced
Understanding the Problem
Either need a system or need to change the existing system
Are there any problems?
Identify problems with existing system
Interview/survey users of existing system
Someone who interacts with the system, but do not interact with the
processes
Interview/survey participants
IT support, interact with the processes
Programmers
Project manager
Business analyst
Analyse existing system
How does it work
Where we write up requirements report
What would we like to have in this system
What would the users like, what would the participants like
What’s in it?
Purpose of the system
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Project Management Summary
4
Analysis of existing system
Definition of additional requirements
Requirements prototype
Model
Gives users an idea of what it is going to look like
Get feedback from participants
Made to understand requirements
Screenshots, something visual
Help further system development - some things will be used later in
development
Screen generators - layout of the screen
Report generator - when a report comes out what does it look like
Output from a database
Like a data dictionary
data flow diagram
Is it do-able?
May need to make requirements
Planning
Feasibility
Is it possible
Economic
Do we have enough money
If not - probably can’t do a lot
Technical
Is it actually technically possible
Do we have the technology
Operational
Does this work in this company
Project Management Summary
5
Training
Scheduling
Time frame
Might not be possible or might need more people
Development approaches
General, safest one for a big project
Traditional
Waterfall method
One after the other
Once you pass a part, do not go back
Mistake - stuck with it
Outsourcing
Getting another person to do it
Let another company do it
Get an expert to do it
Prototyping
We create a model, keep modifying the model
Websites
Start off with a prototype and keep modifying the prototype
Better for user interface
Agile
Websites
Continuously goes through
Hack the way to a solution
Quick
Keep going back and forth
Customisation
Like outsourcing
Project Management Summary
6
Buy a package from another company, and make changes
Participant development
No money, DIY
Do it yourself
Not the most efficient way
Hack something together
Traditional
Waterfall
Iterative
Back and forth
Agile
Go around again and again
Requirements report
Time frame
Details subprojects
Designing
Making the solution
Picked a method out
Design system for ease of maintenance
What does it look like in the computer system
Refine existing prototypes
Participant development
People within system develop the solution
Tools for participant development
Design tools
Decision tree
Decision tables
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Project Management Summary
7
data dictionaries
Field name
Field ID
Data type
description
Field size
Storyboards
Main elements
Implementing
Chaotic
Pick time
Company has to be open to it
Sometimes need to do it in the downtime
Implementation plan
Participant training
Videos
Make people feel comfortable using this system
Assess age group
Conversion method
Parallel conversion
Run at the same time
Disadvantage
Waste money
Data redundancy
Advantage
Can go back to the old system
Direct conversion
Project Management Summary
8
Chuck one out and put in the new one
Disadvantage
Most risky
When something goes wrong, nothing to go back to
Advantage
Cheapest
Know where the new systems data is
Phased conversion
Do portions
Convert certain modules
Slowly change from old to new
Bits of old and bits of new
In the middle of parallel and direct
Pilot conversion
Small group of people try it out
Small group of people testing
Opal+
Select a few people and test it
Advantage
Easy to reverse
Disadvantage
People might be upset with being stuck with the old system
How it will be tested
Operation manual
Documentation which says whats involved in the new system
Details procedures the participants follow when using the new system
Testing, Evaluating and Maintaining
Project Management Summary
9
Test data
Volume data
Amazon on black Friday
If we have millions of customers try to log on, will the system handle
it?
Simulate lots of people going onto the system at once
Will this system ever undergo lots of people going on it
Simulated data
Fake details
Don’t have real people in the system
Make up people, but realistic to simulate it
Don’t want to release real people’s information or change real
people’s information
Data resembles real data but doesn’t give rise to privacy issues
Live data
Real details
Testing in a system that has the real data
Very dangerous
Will have to test in this environment and make a backup to rollback
That is someone’s real account balance
Security and privacy problems
Make a copy of it, run the tests and then delete extra data
Make sure the system works
Check to see if requirements have been achieved
Trial and use operation manual
Modify parts of system where problems have been identified
Do another survey to compare new and old system
Update system documentation
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help