Thursday 27 October 2016

Week 12 - Online Website Builders

Where does one start!! There are many, many players in the FREE online website building category. Most of them have similar functionality and allow you to create websites for free using drag and drop technology. No need to code and if you need more than what is provided for free, many of these have upgrade packages available at an extra cost.

Under a free account, the free tools will give you a set amount of space and access and allow you to host your website with them under a subdomain. Many of them also allow you to also link your website with a domain name and will offer a variety of hosting options.

Domain Vs Subdomain

You can create and resister your own domain name - lots of different packages available and cost can be as little as a few dollars.

The following links will give you information about domain names and how to register

https://www.business.gov.au/info/run/advertising-and-online/register-a-website-name
https://www.auda.org.au/


http://www.domainregistration.com.au/
https://www.crazydomains.com.au/
https://au.godaddy.com/

A domain name could be:
www.michelehardy.com.au

The same website as a subdomain might be:
www.michelehardy.wix.com
www.michelehardy.blogspot.com.au

Free online website builders

Here is my list!
  • Wix
  • WebsiteBuilder
  • IMCreator
  • Sitebuilder
  • Sitey
  • Weebly
  • Jimdo
  • Site123
  • Webs
  • Webnode
  • Yola

Wix

http://www.wix.com/









Website Builder

https://www.websitebuilder.com/



IM Creator

http://www.imcreator.com/





SiteBuilder

https://www.sitebuilder.com/



Sitey

https://www.sitey.com/



Weebly

https://www.weebly.com/au




Jimdo

http://www.jimdo.com



Site 123

https://www.site123.com/




Webs

http://www.webs.com/




Webnode

https://us.webnode.com/



Yola

https://www.yola.com/




Here are a couple in Action!

Wix




Webs





IMCreator



Activity 1


Select 2 of the above tools (or any other that you use or know of) and create a sample webpage.
Share your thoughts on the tools with your classmates.






Week 12 - Closing out report

Closing out the project

The main task at this stage is the handover of the deliverable, as scoped, to the client. At this stage you tick off the items and ensure that everything within the project has been finalised. The key areas of this stage are:

  •     Client acceptance
  •     Lessons learned
  •     Celebrating success
  •     Stakeholder debrief and evaluation
  •     Closing out the project
  •     Contract close-out

The ultimate aim of project management is to bring the project to a successful and complete conclusion. Hopefully, if you have done your job properly, this would have been closely monitored and evaluated against the predetermined criteria with little room left for ambiguity or missed expectations.

As well as delivering the project to your client, the project manager and team members should use this time to look back over the project for mistakes made and the lessons learned as a result. The final stage should involve:

  •     Delivering the project’s objective, output or final result
  •     Finalising all the administrative issues
  •     Evaluating the project and the process

Do all project finish successfully? NO!!! Some projects

  •     Fail to finish at all
  •     Drift off in a non-scheduled (and non controlled) direction
  •     Are superseded with newer ideas and supporters.

Class Activity

Can you think of an example of a project that has failed to finish? Which of the above reasons do you think apply to why the project failed to finish?


If a project is not going to be completed successfully, when do you terminate the project or decide that the project should not continue?

You can start by asking the following questions throughout the project:

  •     Is the project still consistent with the organisational goals?
  •     Is management enthusiastic about continuing the project?
  •     Does the project enjoy cross-functional support?
  •     Is there still a return on investment?
  •     Are there better alternatives for the funds, time and personnel devoted to the project?
  •     Is the project team still innovative?
  •     Has the project lost any key personnel?
  •     Can the deliverable be more efficiently purchased or subcontracted rather than being developed in-house?
  •     Have any changes in the marketplace warranted the project’s outcome and/or termination?
  •     Is the client satisfied? (Has client acceptance been obtained?)
  •     Is the current project team properly qualified to complete the project?
  •     Do other projects warrant higher priority?
  •     Is the probability low that the outcome will be realised?
  •     Are all the tasks finished?
  •     Is the testing finished?
  •     Are the training programs prepared and/or finished?
  •     Is the supporting equipment installed and operating?
  •     Are the documentation manuals finished?

Client Acceptance

The only stakeholder who can ultimately know whether the project is finished or not is the client. The process of acceptance should always be completed as formally as possible so that there is a comprehensive sign off on each and every aspect of the deliverable. This should include the following:

  •     A written acceptance procedure;
  •     A completion checklist;
  •     Specification conformance;
  •     Acceptance or performance testing; and
  •     Final payment

Lessons Learned

Every project, whether successful or not, will generate a ‘lessons learned’. A lessons learned is just that – some practical wisdom that has been observed and hopefully acquired while working on the project.

Lessons learned can be both positive and negative from both mistakes and successes during the project.

Lessons learned must be documented and shared with the other stakeholders, perhaps in a project review document or final project report. The information can then be used when planning and managing future projects.


Celebrating Success

Every project has some success and success should be rewarded. Some of the ways that you can reward your project team are:

  •     Introducing the team members to the client
  •     Taking the team members out for a meal or coffee
  •     Printing up some certificates
  •     Formally appraising and recording the team members’ positive performance
  •     Passing positive feedback on the team on to their line and/or functional managers
  •     Getting all team members to give each other positive feedback on the tasks they performed
  •     Giving the team members challenging duties and/or more complex project work
  •     Channelling your personal feedback to the team members up the chain of command so a higher authority can be seem to be recognising their contribution
  •     Recommending the team members for promotion as a result of their project achievement
  •     Holding a PARTY for the team

Stakeholder debrief and evaluation


At the end of a project you need to bring the stakeholders together for a final debrief and evaluation of their contributions, feelings and outcomes.

The Client
You need to get feedback from the client:

  •     Was the project delivered as specified?
  •     Was the reporting documentation accurate?
  •     Was the project delivered on time?
  •     Were the communication channels kept open at all times?
  •     Was the project delivered on budget?
  •     Were all variations and scope changes addressed competently?
  •     Was the project managed professionally?
  •     Were the issues resolved in a win-win solution for all?
  •     What improvements can you suggest with regard to how future projects are set up and managed?

The Stakeholders
Stakeholders are anyone with a vested interest in the project’s outcome. Each stakeholder should be questioned so that you gain an understanding of the project from their perspective:

  •     Were you satisfied with your level of involvement in the project?
  •     Were you always kept informed of the project’s achievements and failures?
  •     What part did you play in the decision making processes
  •     Could the consultation processes be improved?
  •     What improvements can you suggest with regard to how future projects are set up and managed?

The Project Manager
The project manager has had a lot riding on their back throughout the project so you should take the opportunity to review their performance also.

  •     Were you satisfied with you access to, and support from, the relevant stakeholders?
  •     Do you believe you had sufficient time, budget and resources to complete the project?
  •     Did you have the appropriate level of authority, power and responsibility?
  •     Was the project team appropriately skilled?
  •     Do you require any additional training?
  •     How effective were your leadership skills?
  •     How effective were you at motivating and rewarding the team?
  •     What improvements can you suggest with regard to how future projects are set up and managed?

The Project Team
You should meet with the project team one last time and get feedback as they were the ones doing the main work.

  •     Was your workload appropriate?
  •     Were all the disputes resolved amicably?
  •     Were all decisions reached through consensus?
  •     Did your level of skills reflect the nature of the tasks you worked on?
  •     How would you describe the project environment in which you worked?
  •     How would you describe the project manager you worked for?
  •     Did you always have sufficient information, time, resources and money to make the decisions you were required to make?
  •     What improvements can you suggest with regard to how future projects are set up and managed?

The Close-out Report
The close-out report should be a summary of the highs and lows, success and failures, of the project through the concept , outline, progress and outcome stages. It should address the project performance, administrative performance, organisational structure, project teams, and project management techniques.

Contract Close-out
If you have entered into any formal contracts during the project development, such as maintenance contracts, client contracts, warranties etc., you will need to make sure that these are closed off and/or signed off.

Thursday 20 October 2016

Week 11 - Using Bloggr to create a website

Blogger

Today we would look at our first web page creation tool because it is one that most of you are already familiar with - Blogger!!  If it is not one that you have used, you are still familiar with it because it is one that I use.

https://www.blogger.com/

Once you have logged in etc., you can start by creating a new Blog




 
At this stage, it really doesn’t matter which theme you choose as you can change and customise it at any time.








Once you have selected your theme, you can customise the colours, background images, fonts and page layout. Once you are happy, save and return to Blogger.



Click on Layout.



In Layout mode, you can add, remove or edit any of the “gadgets” that are on your page. This allows you to customise your “web page”.

If you want to include additional pages, select Pages from the left navigation pane.






Click on New Page for each page that you want to add. The title will be what will appear on your navigation. Make sure you PUBLISH them when you are happy.

Once you have pages, you can include the “Pages” gadget to create a simple navigation system.




Here is a preview of my Blogger website:

 
 

So you might ask about using your own domain name rather than something .blogspot.com. Well with Blogger, you can.

Go into Settings and change the Publishing Settings if you would like to use your own domain name. You can register a domain name at a variety of places on the Internet. Prices do vary!!


Week 11 - Tracking your Project

Once your project has been set and is underway, the role of the project manager is to keep track of all aspects of the project.


Baselines

To be able to track your project, you need to tell your project management software that the current version of the project file is the one that you want to save and use to compare with. This process is setting a baseline.

http://www.rationalplan.com/projectmanagementblog/project-management-terms-baseline/


So, for our Big Move project, we have added all of the tasks and allocated is as required and we are happy with it. We can now set this as our first Baseline.

Here is my version of the project:


I will put a copy of this on Moodle for anyone who wants to use the same file.  It doesn't really matter which file you use, but it MUST be a complete plan or at least have all the details for the items that are in the WBS.

Setting your Baseline

Project Libre allows you to have up to 11 baselines.






To save a Baseline, click on Save Baseline and select which Baseline number this particular baseline will be. I chose Baseline with no number.


Once you have set your baseline, you should see a grey shadow underneath all of your gantt bars.


Add some columns that will allow you to enter and/or view actual data.


Entering your "actual" data.

There are a number of ways of entering your actual data. The first is by entering the "Actual Start Date" for each task. You can do the same with "Actual Finish Date" as well.


 You can also go into the properties for each task and add actual data.


You can change the percent complete and/or the work hours. You can also change information that is under Resources Usage.









Thursday 13 October 2016

Week 10 - Risk Management

What is Project Risk Management?


Project risk management is the art and science of identifying, analyzing, and responding to risk throughout the life of a project and in the best interests of meeting project objectives.

The goal of project risk management is to minimise potential risks while maximising potential opportunities or payoffs.

The major processes involved in risk management include:

Risk management planning – this involves deciding how to approach and plan the risk management activities for the project by reviewing the project charter, WBS, roles and responsibilities and the stakeholders risk tolerances.

Risk identification – this involves determining which risks are likely to affect a project and documenting the characteristics of each.

Qualitative risk analysis – this involves characterising and analysing risks and prioritising their effects on project objectives.

Quantitative risk analysis – this involves measuring the probability and consequences of risks and estimating their effects on project objectives. These can then be ranked based on the probability.

Risk response planning – this involves taking steps to enhance opportunities and reduce threats to meeting project objectives.

Risk monitoring and control – this involves monitoring known risks, identifying new risks, reducing risks, and evaluating the effectiveness of risk reduction throughout the life of the project.

Risk Management Planning

A risk management plan documents the procedures for managing risk throughout the project.

A risk management plan summarises the results of the risk identification, qualitative analysis, quantitative analysis, response planning, and monitoring and control processes.

The risk management plan can include a methodology for risk management, roles and responsibilities for activities involved in risk management, budgets and schedules for the risk management activities, descriptions of scoring and interpretation methods used for the qualitative and quantitative analyses of risk, threshold criteria for risks, reporting formats for risk management activities, and a description of how the team will track and document risk activities. It can also include contingency plans, fallback plans, and contingency reserves.

Contingency plans are predefined actions that the project team will take if an identified risk event occurs.

Fallback plans are developed for risks that have a high impact on meeting project objectives, and are put into effect if attempts to reduce the risk are not effective.

Risk Identification

Identifying risks is the process of gaining an understanding of what potential unsatisfactory outcomes are associated with a particular project.

In addition to identifying risk based on the nature of the project or products produced, you can identify potential risk according to project management knowledge areas:

Integration – Inadequate planning; poor integration management; lack of post-project review; poorly defined life cycle; Inadequate methodology

Scope – Poor definition of scope, work packages or expectations; incomplete definition of quality requirements; inadequate scope control; lack of documentation; Incomplete requirements identified; Lack of scope control measures for later changes

Time – Errors in estimating start and finish time or resource availability; errors in determining the critical path; poor allocation and management of float; Tight timeframes on critical tasks.

Cost – Estimating errors, inadequate productivity, cost, change or contingency control; poor maintenance; security, or purchasing.

Quality – Poor attitude toward quality; substandard design/materials/workmanship; inadequate quality assurance program; Incomplete specification; Poorly skilled resources; Lack of reviews and monitoring.

Human Resources – Poor conflict management; poor project organisation and definition of responsibilities;  Poor management and leadership styles; Poor skills and training; Team performance issues; No ownership; Allocation and over-allocation issues

Communications – Carelessness in planning or communicating; lack of consultation with key stakeholders; little accountability; Poor reporting of progress, deviation and correction; Them and Us mentality; Inappropriate reporting procedures.

Risk – Ignoring risk; unclear analysis of risk; poor insurance management

Procurement – Unenforceable conditions or contract clauses; adversarial relations;  Solvency of supplier; Supply and logistic problems; Compliance with specification; Delivery delays.


You can also categorise risks by outside forces:

Competitor  

    Merger activity
    Market acquisitions
    Plant closures
    Price fluctuations
    Introduction of new product or service offerings
    Reduction in operating costs

Economy

    The economic cycle
    Changes in exchange rates
    Government fiscal and monetary policy
    Unemployment rates
    Interest rates

Technology

    Rapid advancement in hardware and software capability
    Production efficiencies
    Mass production
    E-commerce opportunities

Marketing

    Release of competing products or services
    Market share
    Consumer response rates to advertising
    Accuracy of market research

Finance

    Availability of funding
    Funding contingencies
    Penalties/costs associated with funding
    Unanticipated changes to scope

Organisation

    Restructuring
    A move towards outsourcing
    Fluctuating morale and motivation issues
    Availability of staff

People

    Skill deficiencies
    Training requirements
    Lack of control

Outcomes

    Deliverables that are poorly defined
    Lack of user involvement
    Outcome not accepted by client

Stakeholders

    Unknown and/or changing needs
    Lack of participation

Qualitative Risk Analysis

Qualitative risk analysis involves assessing the likelihood and impact of identified risks to determine their magnitude and priority.








A risk probability can be described as being high, moderate, or low. You can also show the probability using a numeric scale. There are a number of techniques that can be used to rank the probability of risks occurring and the effect on the project outcome. They include:


  •  Probability/Impact Matrixes
  •  Top 10 Risk Item Tracking
  •  Expert Judgement


Once you have identified the probability, you can determine what the consequences of the risk will be. Consequences can also be ranked as high, moderate or low or by using some descriptive words such as insignificant, minor, moderate, major, or catastrophic.

The best way to show the risk analysis is with a table that shows the
RISK,
PROBABILITY,
CONSEQUENCE, and
PERSON RESPONSIBLE.

You can then add a column for your action plan - See Risk Response Planning

Quantitative Risk Analysis

The main techniques for quantitative risk analysis include decision tree analysis and simulation.

A decision tree is a diagramming method used to help you select the best course of action in situations in which future outcomes are uncertain.

Simulation uses a representation or model of a system to analyse the expected behaviour or performance of the system.

Risk Response Planning

After risks are identified and quantified, an organisation must develop a response to them. Developing a response to risks involves defining steps for enhancing opportunities and developing plans for handling risks or threats to project success.

The four basic response strategies are:

Risk Avoidance – involves eliminating a specific threat or risk, usually by eliminating its causes.
Risk Acceptance – means accepting the consequences should a risk occur and monitoring both the risk and the consequences.
Risk Transference – is shifting the consequence of a risk and responsibility for its management to a third party.
Risk Mitigation – involves reducing the impact of a risk event by reducing the probability of its occurrence.
Risk Exploitation - not all risks have a negative outcome. A risk may be able to be exploited to create a positive outcome


Risk Monitoring and Control

Risk management and control involves executing the risk management processes and the risk management plan to respond to risk events. Executing the risk management processes means ensuring that risk awareness is an ongoing activity performed by the entire project team throughout the entire project.

The easiest way to get started is to create a table with the following headings:
Risk - What are the risks to the success of this project
Probability - What is the probability of the occurrence of the risk: Low, Medium, High
Consequence - If this happens, what is the consequence to the project - Low, Medium, High, Critical
Strategy - What is the response strategy category -  Avoidance, acceptance, transference, mitigation.
Person Responsible - Who is responsible for the strategy

CLASS ACTIVITY

As a class, create a Risk Management Plan for "The Big Move" scenario,