Project Management (BCS Diploma) Guidance from Ms.Dilshara

Wednesday, March 14, 2018

Golden Rules for BCS Exams

Hello BCS busy heads ,

all I can say by now is

BCS is not Impossible , but you need to be patient , wise and tactful to choose the right questions and Manage Time

For your PM Module

Golden Rule #1

Time is Crucial . Never take more than 30 Mins for a Question

Golden Rule #2

Use essay format answering style unless otherwise list , identify , state verbs used in question. . even in that case , remember not to write few words for a bullet point. write a meaningful sentence per bullet point.

Golden Rule #3

Choose Questions wisely. take about 5 minutes to slowly read each question , mark with a big Circle , the asnwers you are sure about . Small Circles for unsure but manageable answers . crosses for what you dont know . then have a look at questions you can score the most . !!!! Very Important !

Golden Rule #4

Spend the exact minutes by timing each question. Leave some extra space at the end of every answer . (it may be useful in Rule #5)

Golden Rule #5

Never attempt more than 4 questions . Its a time waste to write more questions. Instead , if yo have spare time left , you better improve the answers you have already written (remember rule #4 , leave some space ).

Golden Rule #6

Start with the easiest question and gradually go to the most difficult one. Never start with the most difficult one , it demotivates you and even looses marks from easiest questions.

Golden Rule #7

If you want to do scheduling question, please keep it for the last 1/2 hour .

Golden Rule #8

Never doubt your abilities . You came all this way because you are capable ! Believe me ! Smile

Good Luck Everyone

Monday, March 12, 2018

Change Management / Configuration Management

Hello everyone ,

Seems like everyone in to studies not revision classes ? :'/

Only one kid came for this class. and seems no one knows importance of last minute classes.

Anyways we did a very important lesson , thats change management .

How a project manager should systematically address changes in to the project . Changes cannot be refused , changes can not be at all , all accepted. There is theoretically a procedure for managing change .

After studying the note below

https://www.dropbox.com/s/ohcasgjy60nsphk/Software%20Configuration%20Management%20note.docx?dl=0

now do these past paper questions

Questions on Change Management – Project Monitoring & Control

Q1 - Project Monitoring & Control Life Cycle - 2016 September – A3 – a

The framework for controlling a project to ensure it meets the project plan is the project control lifecycle. Draw and label a project control lifecycle diagram.(8 marks)

April 2013 – A1 – b – 5 marks

Your company has decided to develop a new in-house computer system and the project plan has been prepared. Explain briefly the FOUR key steps (which might then be repeated) in the project control life cycle.

Q2 - Change Control Process & Who involves in Change control Process. ?

2017 March A1 - c) - 8 marks

There are five stages in a change control system:

o submit the request for change (CR)

o investigate and review the request for change

o assess the feasibility and implications of the requested change

o consider the request, and decide whether to accept or reject

o implement the accepted change

(i) Identify the people (or groups of people) who should be involved in each of these stages.

(ii) Identify and explain in which of these stages the configuration management system should be referred to or affected.

Q3 - What is configuration Management?

2017 March A1 - a – 10 marks

a) Explain the main purpose of using a configuration management system during an IT systems development project.

List and describe the THREE main elements of a configuration management system and explain how they would be used during the project.

Q4 – Items in a Configuration Item CI -

2017 March A1 – b – 7 marks

Identify and describe at least FIVE different details held when defining a configuration item.

Q5 – Sep 2011 – B6

Explain the main purpose of using a configuration management system:

1. during an IT systems development project;

2. after the system has been installed, when further software maintenance will need to be undertaken

Q6 - Oct 2010 - Question A3 – a – 12 marks

Explain the main reasons for using:

i) Change control

ii) Configuration management when developing a new in-house computer system.

Highlight at least TWO advantages and ONE disadvantage of each.

Q7 – Sep 2011 – B6 C

Identify and explain in which of these stages the configuration management system should be referred to or affected. (8 Marks)

Sunday, March 4, 2018

2018 March 3rd Class–Communications Management and 2017 March Paper

Hello all

we discussed the elements of different reports

1. Elements of a Highlight Report

2. Elements of an Exception Report

3. Elements of a End Stage Report (Home work)

4. Elements of a Lessons learnt report ( Home Work)

And the past papers

A1 – We will do next week once we complete the chapter on Project Configuration and Change Management

A2 – Scheduling – we have already done this in class

** remember to practice AON redrawing with changes ( part b)

A3 part a

Skills of a PM

Leadership Skills
Communication skills
problem solving skills
good estimation skills
people management
negotiation skills

Attributes of a PM

patience
understanding people ( empathy )
belief in quality
customer focus
adopting to changes
motivating team
document handling
listening

A3 part B – done – refer to slide

A3 part c – PROBELM SOLIVING STRATEGIES

analyse the root causes for this situation
discuss with team members and senior management
go through reports and analyse performance parameters
discuss and generate possible solutions
choose the most effective solution
implement the solution
analyse the growth of performance and effectiveness of the solution

Process 1 – Concept formation and Analysis (outcomes : req specification )

Feasibility study and report
requirements analysis
requirements specification

Process 2 – System and Software Design (design diagrams eg : DFD , ER , ELH , Class , Sequence etc )

process design
interface design
database design

Process 3 – Development and Testing (outcomes : COde , Application program , developed databases and interfaces , finalised documentations – system and user documentations )

coding
database development
interface development
unit , integration , system and user acceptance testing

Process 4 _ Implementation and Maintenance ( outcomes : bug reports , change requests , upgraded system )

site preparation
training and development
installation
final testing
bug fixing / improvements / upgrades

B4 part 2

Verification – are we building the project and product right – are there any errors ? defects ? is the system well tested ?

Validation – are we building the right product or project ? – have we understood the requirements correct ?

B5 part a

already available in printed note

B5 part b

ISO 9001 – process oriented , customer focus , SYstem approach to management

ISO 9126 – Product Oriented , completely product focussed , products and modules no mention about people , processes

B5 part c

Review techniques are static techniques ( without executing a code )

Peer review
Desk check / dry run
walkthrough
proof reading

Agile approach

- Changes are welcome at any stage of the project

- customers are continuously involved in development

- no rigid steps

- iterative development

compare these with waterfall .

B6 part b

MOSCOW rules – refer to note

part c

XP diagram explain with sprints

How I did my BCS Exam :)

Hello Everyone ,

I know you all must be getting ready for the battle in few weeks.

Twelve years ago , in 2006 April , I too was just like you and making time tables, revision notes , past paper questions , no pay leaves (talk about it ! )

if you are able to read in sinhala, just spend a few minutes to read how I did my BCS exam in 2006 Smile