Block 4 p2 Flashcards

1
Q

What is project management

A

its a field of study that brings together techniques and tools for managing development activities - it helps organisr tasks and manage resources - so the app get completed on time , budget and fulfil requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Give me two examples of projects that started small

A

Google - Larry park and Sergey brin started coding for google in a garage , both went to stanford university
Facebook- Mark Zuckerberg started coding for facebook in a dorm room , he went to harvard

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

what does these two applications have in common

A

As they grew , they needed better organisation and planning , sorting out the tasks and who would perform it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are projects (first definition)

A

it has a finite life where a unique set of skills and techniques tools and resources are brought together to achieve a specific goal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are projects (PMI definition)

A

a temporary attempt to create a unique product, servicr, result

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are projects (other two definitions)

A

A project in business and science are defined as collaborative daring journey it involbes research and design to achieve a particupar aim

it can also be defined as temporaty social system which is constitued by a team to accomplish specific tasks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Some tools for project management

A

Gantt charts , PERT (programme evaluation and review techniqurle)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Some opportunities of Projects

A

Launching new product, building a factory… increase revenue, make profit

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Some project risks

A

it may not be completed on time, cost more than estimated, may not produce the desired result

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are some common features for grand failures

A

lack of end-user involvement : end users may find the project as additional work outside their normal tasks

Long or unrealistic timescales: business requirements may change before the project is completed

Vague or inadequate requirements

inadequate testjng through the project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

what does project management wants to find a balance between

A

between requirements , quality on one side and time, resources and risks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is the proposed solution

A

form a project plan (documentation)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

what are requirements

A

are what defines the outcome of the project with sufficient details to estimate the resources necessary to compelte on time and quality

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What does the quality define in Project management

A

defines the standards by which the project outcomes will be judged

high level - passing specific functional testd

low level - use of coding or validation standards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

what does the resources represent in project management

A

people (with appropriate skills)and equipement(available when required) essetial to deliver the project on time and budget

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

what is the time element in project management

A

both sequence of tasks needed to be done and total duration of project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

what are risks in project management

A

defining in advanc what may happen to drive project off course and what will be done to recover the situation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What is the waterfall lifecycle model

A

(check slide 11, figure 1)

its linear software dev cycle - each phase must be completed before the next phase , reduce the chance of mistakes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What are user requirements (steps of waterfall model (1))

A

define what the software do by gathering input from user, at this stage the details for project management , change control, verification and testing are prepared

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

what are software requirements (steps of waterfall model (2))

A

converts user requ to logical model and functional requirements and interfaces with specific performance targets . The model is ABSTRACT . At the end we should have software requirements document , summary of users support needs , outline plan for testing the complete system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is the third phase after user requirements (1) and software requirements (2)

A

Architectural design : converts the logical model into a physical model, Only upper level components are defined in detail at this stage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What are the next three steps

A

Detailed design and production : implement low level components, design reviewed layer by layer, define error handling mechanism and usnit tests for each component

Transfer: install software to an operational environment

Maintenance: provides operational time required to ensurethat thebsofteare satisfies the user requirements (like a waranty)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Pros of waterfall model

A

time spent in early phases reduces the chance in errors in later phase

provides clear boundaries between phases that are predictable and orderly

concentrating on the skills required for each phases

solution is well documented whoch supports maintenance and upgrades

24
Q

Cons of waterfall model

A

reliance on documentation output at each phases can lead to slow developement

long delay between the start of a project and delivery of functional software

cannot do parallel development with sequential phases

not suited to projects of less than 6 months duration

25
Q

One value of the waterfall cycle

A

offers some insight into the activities that has to be done and their sequence

exp: user requirement phase (gather user requirement - define func requirement - outline acceptance tests - plan the system requ phase - prepare the requirements document)

26
Q

What is the the idea of a waterfall model

A

decompose the project into small chunks ( package of work that can be assigned to an individual)

27
Q

what does the reference numbee indiquate in the hierarchical decomposition

A

the reference number (view slide 16) indicates the level in the hierarchy (1 -> level 1 , 1.1 -> level 2 (two digits)…. 1.1.1.1 -> level 4)

28
Q

what is the resulting diagram (of the hierarchical decomposition) knowns as and what does it represent (slide 16 figure 2)

A

WBS -> work breakdown structure
it represents a map of all work to be completed

29
Q

Difference between v model and waterfall mode

A
  • phases can overlap in a v model so a phase is not necessary done before the next can comment
  • testing activity is a separate sequence of phases
  • detailed design and production split into three phased -> design code test

-the phrases after production (check slide 17) are bent upward and upward is project integration and downward is project definition

30
Q

Difference between the lifecycle model (1) and project plan (2)

A

(1) describes the work to be undertaken and the sequence (2) define objectives of the project and the process by which the work will be managed and delivered within budget and time

31
Q

What is the purpose of the project plan

A

it starts as a proposal to undertake a project , the function id to provide sufficient info for the mnagement team to decide - theres some aspects to communicate about

32
Q

Some of these aspects

A

The project obejctives -> business cased - opportunity , need , problem

Scope -> approach to the project and how it will satisfy stakeholders requirements

Partnerships -> means by which project risks can be shared

outputs -> design documents , code for components , test results

resources -> human and non human resource requirement required to complete project (servers to host…)

team -> project manager , stakeholders and partners

33
Q

To monitor performance , project management plan uses milestones and gates define those two

A

milestone -> important event in the schedule like the delivery of an item or completion of some tests ( a way to compare the actual performance to the planned one)

gates -> point where the project stops to await for a decision

34
Q

to monitor costs and progress we use metrics what are the most common metrics used

A

time -> compare actual tike by estimated duration
cost -> same as time but for cost
deliverables -> compares estimated time and cose to creare a deliverable with the actual ones

35
Q

What is the gathering stage of a requirement (1)

A

raw ideas about what the solution should provide in terms of importamt features : interview stake holders and actual end-users

36
Q

what is the refining stage of the requirments (2)band the steps

A

converts raw ideas into something more structuees , stakehilders should review it
steps:
premilinary design presented to stake holders as online wireframe and site map
stakeholder provides feedback on wireframe
feedback incorporated as revisions
wireframe model signed off

37
Q

what does MoSCoW stand for

A

Must , should , could, won’t

38
Q

Explain the four words

A

Must -> have to be in the project (func requirement)
should -> also have tk be in the project but if time is short can be postponed
could -> can be in the project if not it does not affect anything else
Wont-> project wont project a feature

39
Q

There are two types of quality , what are they

A

functional quality ,fit for purpose , for funct requirememts
structural quality , how well the software is produced

40
Q

ISO decribes software quality by…:

A

functional suitability , performance efficiency, compatability, usability, reliability, security, maintainability, portability

41
Q

Consortium for IT software quality (CISQ) describes it by …:

A

reliability : low risk of failure and downtime

efficiency: performance of the code and resources needed to exexute

security: potential security breaches for bad coding practices

maintainability: ease of updates

size: amount of code produced , work completed and the complexity of solution

42
Q

what are the challenges of the structural quality

A

aim for the right balance because raising standards in one can impact in lowering the standards of another

43
Q

What are the steps of a quality plan : (plan to ensure quality)

A
  • identify appropriate quality standards and methods to satisfy them
    -procedures to ensure quality standards are followed
  • monitoring of project outputs
44
Q

what are the quality assurance activities

A

testing, validation,, code reviews

45
Q

what is the resource and time sections of a project plan intended to

A

sumarise the resources required to complete a project together with project duration and date

46
Q

who will have direct contact with the customer

A

people mentioned in an internal plan (like project manager)

47
Q

How does one person estimates the duration of a project (what to start with)

A

create a wbs (work breakdown structure) with enough detaild to estimate resources and duratiin and the lifecycle models provide a useful base

48
Q

Other estimation methods

A

historic data (previous projects…)
ask a friend
weighted average (like ask a friend - but adding best,worsk, most likely

(best + 4 × most likely + worst) ÷ 6

management tax : add extra time

49
Q

What is risk managememt , what is it about?

A

understanding and controlling the uncertainity of the project being completed on time and budget

it is about asking questions

50
Q

Organisational question asked and External ones

A

organisational:
does the company have enoufh resources
has the project sufficient priority within the organisation

external:
do we know the customer ?
- is the customer commited to the project?
- do we know the equipment supplier? are they reliable?

51
Q

Scope and technical questions

A

Scope (requirements)
how likely are the requirements to change once the project has started?
have requirment been priotirized?

Technical (software and hardware)
how complex is the project
are the technical requirements understood?
has the technology been used before?
does the team have necessary skills?

52
Q

Project management questions

A

are the estimates realistics
is the project manager well known
will any team member be assigned multiple projects

53
Q

Low, Medium, High likelyhood

A

low : never occurs <5% of projects
medium : occurs 1 project out of 5
20% of projects
High : occurs in every project >75%

54
Q

low,medium,high impact

A

low impact : has negligible effect on the project outcome
medium : significant effect , project outcomes not threatened
high: project outcomes threatened

55
Q

What is risk rating matrix

A

view slide 35 - it combines likelyhood and impact to measure risks

56
Q

Some risk strategies

A

Eliminate : avoid by doing in a different way
Reduce the likelyhood: monitor more closely
Reduce the impact: like use a contract staff while a member is off sick
Stop the project
share the risk with partners
accept the risk if it has low impact and likelyhood

57
Q

What is the final stage of risk management

A

combine all informatiin gathered that highlights the most significant risks , outline mitigation (action to reduce) and assign responsibility for monitoring - goal is to provide a summary , the risk managememt plan is typically a snapshot of the assessed risks at the start of the project