Construction issues resolution in Sydney

Construction issues resolution in Sydney - Part 3

Major building defects are still not resolved and the owners of most of the units didn't even bother to follow up. However some units are eager to finalise the process and fix the defects.

One member of executive committee has built an online application on the Internet to get the response from the interested units what defects have been fixed and what are outstanding. With the results of that report owners corporation lodged a complaint with Fair Trading against the builder on the outstanding defects.

The complaint was lodged on 16/01/2013.
A week later, on 23/01/2013 Fair Trading called the owners corporation to confirm the details of the complaint.
Same day they called the builder.

Builder contacted owners corporation on 29/01/2013 to advise that they are coming to inspect the defects again! They explained it as they want to confirm what defects they are responsible for and that they are going to contact Fair Trading after the inspection.
The builder advised they are coming for inspection on Friday 01/02/2013.

From the Fair Trading perspective the owners need to give builder a chance to rectify the defects which is by first inspecting the property.

Thursday 31/01/2013 the builder called and said they can't make it on Friday 01/02/2013 and asked to reschedule for Tuesday 05/02/2013. All the owners were notified already and expected the builder to come on Friday. Some of them took time off work already.

The response to the builder was to come on Saturday 09/02/2013.

To be continued.

Other posts from this story.

Comments

Wine - 2011 Brown Brothers Crouchen Riesling

Very nice wine with fruity taste - peach and pear: Consumed with Hungarian salami. Tasting notes .

Scrum - Team Culture and Wall Manifesto

In the Scrum framework one of the key components is the wall and daily stand-up. In some organisations I worked with the whole concept of the wall is not accepted by many developers, because of the stand-up necessity and "time waste". Very often all that methodology is used for the sake of methodology and not to achieve what we actually do - adding or creating value to our customer (usually called "The Business"). I can understand frustration that is caused by the wall and stand-up process. From the software developer perspective it is really a waste of time for the following reasons: 1. In 95% of cases developers are head down working like hell delivering valuable outcomes that they are accountable for. Extra effort to go to the wall, staying there for 15-30 minutes and listening or not listening to what others were doing yesterday and will be doing tomorrow is annoying for them; 2. The mere fact of having to do something mandatory to do that looks like

Mastering The Multitasking

There is usually two distinct perspectives on multi-tasking: 1. Multitasking is counterproductive. We get distracted by multiple tasks that all get our way and fight for our scarce attention, time and resources. This leads to a common fallacy that if you do multiple activities “at a time” you are not doing good work in any of those. 2. Multitasking is a way of getting many things done in a short period of time or in a long run. Indeed it can be either a disaster or a great helper depending on how it is used and practiced. Most recent research shows that we don’t do multiple tasks purely in parallel or simultaneously. That means we don’t purely multi-task, but switch between tasks and execute them one at a time, but by spending very small timeframes on each task. A good example from the history is a story about Julius Caesar capabilities in that area. Plutarch writes, “Caesar disciplined himself so far as to be able to dictate letters from on horseback, and to give directi

Travels etc.

Search This Blog