The purpose of these IT procedures is to allow a Systems Analyst to quickly pick up the steps required to carry out key project tasks which are typically conducted within an IT Software Development project.
Project Selection and Feasability
a) Economic
b) Technical
Develop workplan
a) Task identification and estimation
b) Work Breakdown Structure
c) Gantt chart
d) Scope management
Control & Monitor Project
a) Project Standards
b) Documentation organisation and sharing
c) Timeboxing
d) Risk Management
Determine Business/User Requirements- Why & What?
a) Online interview
People often don't know what they need until they see it - they probably understand that they have a problem or issue but don't know what the solution is.
People don't have a good understanding of their problem - amateur psychologist
look for peoples motivations
Understand people communication styles
Most req gathering is done by one-on-one interviews
Develop your own process.
Prepare for interview
Decide who to interview
Decide at high level what to get out of meeting
Outline of specific points to cover.
Mention goals for interview in invite - helps keep focus during interview.
Learn about stakeholder before meeting - name, title, responsibilities, general sense of person, how do they feel about the project.
Start with intro - recap goal for purpose of meeting
Ask questions
start at high level and ask them what the project is about in own words.
Try to understand how they think and what they want
If you don't understand, ask them to explain - let me see do I have this straight
End of interview - go on until time is up or I have enough info.
Thank them as they are helping me do my work.
Ask them who else will I speak with
Type up notes and email to Interviewee