Tuesday, January 8, 2013

Ethical Code of Conduct

9th January 2013

Risk Management

8th January 2013


Risk?
Risk can be defined as the combination of the probability of an event and its consequences. (theirm, 2013)

As shown by Institute of Risk Management Risk Management Standard is the result of work by a team drawn from the major risk management organizations. (theirm, 2013)


Risk management is important because:

  • projects are, by definition, risky enterprises
  • implications of project ‘failure’
  • use of estimates/assumptions

What risks do projects face?


>strategic risks

project abandonment

massive over-run/over-spend

loss of client confidence/future business

> operational risks

constant change/replanning/inefficiency

over-run/over-spend low morale/unacceptable working conditions

Risk Management Process
Risk planning

adopt risk management approach/policy

identify  mechanisms to identify risk factors

Risk identification

identify tasks

predict effect on baseline plan

Risk analysis

assess likelihood of specific risks

assess impact of specific risks

Risk response

plan possible responses to risk occurrence

develop contingency/fallback measures

Risk action

implement risk reduction measures

monitor risk factors 

How to identify risks?

must be a precise definition

must be capable of being measured

must have measurable impact


 How to analyze risks?

  •  

Career Development(CV/ Cover Letter/ Job Interview)

1st January 2013

Curriculum Vitae & Cover Letters



What is a Curriculum Vitae?
This is a short account of one's career and qualifications prepared typically by an applicant for a position.(merriam-webster, 2013)

What is a Resume?
Formal presentation of a job applicant's education, skills, and work experience.(businessdictionary, 2013)

Curriculum Vitae

General Set up features of a CV:

  • Font: Time new Roman
  • Regular paper: White
  • Font size: 12 points
  • No underlining but can bold or use caps to stand out things
  • Single sided
  • 1" margin in all around
  • Number the pages
  • No graphics
  • Full name on every page

Sections of a CV

  1.  Contact Information
  2. Objective
  3. Education
  4. Honors & Awards
  5. Professional Experience
  6. Publications/ Presentations
  7. Extra-curricular & Volunteer Experience
  8. Interests

 

 Cover Letter

Why write a cover letter?(law.du, 2013)

The cover letter is your first and possibly, only opportunity to engage a prospective employer. It is a 
key marketing tool to convince the employer to take the time to look at your resume. .

The primary purpose of your cover letter, when combined with your resume, is to get an interview.
The second purpose is to communicate “the intangibles” not readily apparent from the factual
content of your resume. It should be written in a tone that is direct, unassuming, and conveys
enthusiasm. 

Helpful hints while writing cover letter


  • Be assertive
  • Value to employer
  • Simple and direct language
  • No grammar errors
  • Reflect your individuality
  • Spell recipient name correctly
  • Be friendly
  • Target your letter

 Sections of Cover Letter

  • Your address  and date
  • Recipient name and address
  • Salutation
  • Body of the letter
  • Complimentary close and signature
  • Title of respect
  • Return address and  zip code

Job Interviews 


What is an Interview?
It is a meeting of two people face to face to accomplish a known purpose by discussion.

2 important facts to remember in an interview:
  • Aptitude : Able to learn new technologies
  • Attitude : Able to work with others
In an interview there may be 3 types of people :
  • Technical
  • Emotional Quantum
  • Evident of the CV
 Types of questions that can be asked from you in an interview:
  • Rapport building questions - helps to put the candidate at ease
  • Open-ended questions - Depending on how the first questions were answered, this set of questions will be brought up
  • Probing questions - These are mostly technical type questions
  • Non-questions - Makes the candidate comfortable at responding by asking questions that does not end with a question

Wednesday, December 26, 2012

Personal Branding

18th December 2012

(defineyourdiva, 2012)

What is A Brand?

As mentioned on sa.sc, 2012 website, it is a trademark or a distinctive name identifying a product or manufacturer. 

What is Personal Branding?
The significance of personal branding is surrounded mainly with Confidence.
Personal Branding is about unearthing what is unique and different about you and allowing every one to know it. (SCHAWBEL, D. (2009))
Personal Branding involves the process by which a person differentiates themselves by identifying and articulating their unique value proposition. (SCHAWBEL, D. (2009))

One of the main aspects of Personal Branding is the "Visibility". This is the ability to clearly display your values to the outside world. Opportunities for advancement and success will arise through your connections and visibility that is being created through repetition and strategic placement of Brand Messaging. 

Personal Branding is all about:
  • Taking control of your image
  • Know what you have to offer to the world, to the society and to the mrket.
  • Know what makes you different from the rest of the people
  • Know what makes you stand out and be recognized and remembered.
Developing Personal Branding:
  3 easy steps -
    1. Take time to know yourself
    2. Donot be the person whom the other people want you to be
    3. If you are with attribution - you will not be successful with this alone.

My Personal Brand


 My personal brand denotes :
  • Good Memory
  • Creativity
  • Straightforwardness
  • Goes forward and never turn back
  • Living with the nature

Friday, December 14, 2012

Models and Life Cycles (Software Life Cycle Models)

17th December 2012
(docstoc, 2012)


Life cycle models describe the interrelationships between software development phases (levela, 2012).

 A software life cycle model is: "A representation of the major components of software development work and their interrelationships in a graphical framework that can be easily understood and communicated"(chambers, 2012)

The common software life cycle models are (levela, 2012):
  • spiral model
  • waterfall model
  • throwaway prototyping model
  • evolutionary prototyping model
  • incremental/iterative development
  • reusable software model
  • automated software synthesis


1. Spiral Model -

(teced, 2012)


Is developed with the aim of reducing risks in the Software development life cycle. Spiral Model is a combination of :
  - Waterfall Model
  - Evolutionary Model
  - Incremental Model


Advantages of Spiral Model (stsc.hill, 2012)
• It provides better risk management than other models.
• Requirements are better defined.
• System is more responsive to user needs.

Disadvantages of Spiral Model (stsc.hill, 2012)
• The spiral model is more complex and harder to manage.
• This method usually increases development costs and schedule.

2. Waterfall Model (ecs.csun, 2012)

(buzzle, 2012)
 Waterfall model includes the steps: 
    •  Requirements Analysis
    • Software Design
    • Coding
    • Testing
    • Maintenance
Advantages of Waterfall Model
  1. Easy to understand
  2. Widely used in many projects
  3. Establishes milestones - when deliverables are produced and when reviews are being taken place.  
Disadvantages of Waterfall Model  
  1.  Not Realistic - may not work in real world projects.
  2. Does not reflect the iterative nature of projects.
  3. Working software may not be available for this Model
  4. Does not incorporate risk assessment

3. Evolutionary Prototyping Model (cse.unr, 2012)

(cse.unr, 2012)
 Advantages of Evolutionary Prototyping model
  1. Deals constantly with changes
  2. Provides quickly an initial version of the system
Disadvantages of Evolutionary Prototyping model
  1. Quick Fixes may be involved
  2. The system's structure can be corrupted by continuous change
 

 

Development Methodologies

11th December 2012


A Method is "a way of doing something, especially a planned or established way."(macmillandictionary, 2012). Method Includes Models, Life cycles and appropriate techniques. 

While A Methodology is " a system of methods used in a particular area of study or activity". (oxforddictionaries, 2012)

 Reasons for using a Method? 
  1. - Define what you need to do
  2. - Define the order in which you do it
  3. - Improve your productivity
  4. - To provide milestones
However, the issues faced with Methods are : 
  1. Methods are only tailored to large, complex organizations. For small projects methods may not be very useful.
  2. Methods cannot guarantee success. It depends solely on the correct application at the correct time and the correct place.  
  3. A Method may also have a too little scope.







Project Management

10th December 2012
(tenrox, 2012)


What is Project Management?

Project Management is the application of Knowledge, Skills, Tools and Techniques to project activities to meet requirements of the project. The Project Management Institute adds another important component to the above definition as " It’s a strategic competency for organizations, enabling them to tie project results to business goals — and thus, better compete in their markets".

Process Groups in Project Management [Stages in Project Management](projectinsight, 2012)

(constructionchat, 2012)

  1. Project Initiation - An idea for a project will be carefully examined here to determine whether or not it will bring benefits to the organization. During this phase, a decision making team will identify if the project can realistically be completed. 
  2. Planning - A project plan may be put in writing, outlining the work to be performed. During this phase, a team should prioritize the project, calculate a budget and schedule, and determine what resources are needed.There are 9 steps carried out in this stage. They are: 
  • Integration
  • Time Management
  • Quality Management
  • HRM Management
  • Procurement Management
  • Cost Management
  • Risk Management
  • Communication Management
  • Scope Management

   3.  Executing - Resources' tasks are distributed and teams are informed of responsibilities. This is a good  time to bring up important project related information.After this stage is completed a "Status Report" is developed.

  4. Monitoring & Controlling - Project managers will compare project status and progress to the actual plan, as resources perform the scheduled work. During this phase, project managers may need to adjust schedules or do what is necessary to keep the project on track.

  5. Closing/ Completing - After project tasks are completed and the client has approved the outcome, an evaluation is necessary to highlight project success and/or learn from project history.

Why Manage Projects?

Projects are managed to ensure the project will produce the expected results as the output. This increases the chances of success and optimization of resources while managing the stake holders expectations.
These expectations are of 2 types:
  1. Stated Expectations - Clearly explained expectations
  2. Implied Expectations - Provides an expectation that can be accessible. Costs does not incur to fulfill Implied Expectations. 
  3.  Eg: User Friendliness of the System. 

What is "Triple Constraint?

(pmhut, 2012)
The Triple Constraint Mentions that (projectsmart, 2012):
  • Projects must be delivered within cost.
  • Projects must be delivered on time.
  • Projects must meet agreed scope, no more - no less.
  • Projects must also meet customer quality requirements.

Project Scope & Feasibility

  1. Aims and Objectives of this Project - Analyzes the reason why a company requires Information Systems for its project 
  2. What will the project not do - The content of the project that will be done and the content that will not be covered within this project. 
  3. Is the project feasible in terms of: 
      • Cost - will its save the time and effort of people
      • Technicality - is the technology advanced enough to suit the project
      • Socially - Are the people ready to accept the project
      • Organizationally -  Will it be useful and fit in with the business requirements.


Skills required for Project Management

  1. Hard Skills -
      Hard skills often involves in the creation of a tangible deliverable leadership, More technical in Nature, Often incorporate the use of a tool (scheduling software; spreadsheets; presentations) or
    deliverable templates. (projectmgmt.brandeis, 2012)
  2. Soft Skills - 
     Also known as "Interpersonal Skills". This includes traits such as leadership, communication, negotiation, expectations management, influencing, problem-solving, and decision-making. Soft skills are largely intangible, not associated with a deliverable or a concrete output, and they are generally employed without the use of tools or templates. (projectmgmt.brandeis, 2012)