Home Building Issues - Sydney Experience

Set of posts about defects and dispute resolution in regards to new strata property in Sydney, NSW.

Part 1 - Description of the situation and outline of 11 months of initial process to try and rectify major defects
Part 2 - Research in regards to Strata rules and findings that there is a lot of dodgy activity happening
Part 3 - Fair Trading application lodged and inspection set with the builder again
Part 4 - The builder rejected some defects and didn't fix any - Fair Trading inspector was called in
Part 5 - Fair Trading inspector came and ordered to rectify defects - 1 year and 6 months into process and no results yet!
Part 6 - Two months after Fair Trading inspection - the issues still not fixed
Part 7 - Some defects still not rectified - non-compliance report by Fair Trading
Part 8 - Two years into the process - started conversation again with the vendor and builder
Part 9 - Taking builder to the tribunal
Part 10 - Some positive result - one major issue fixed
Part 11 - Next milestone - Fair Trading inspection No 2. 2 years and 7 months in the process.
Part 12 - Despite Fair Trading rectification and tribunal orders the builder doesn't rush to fix the problems
Part 13 - Getting hot without a shower and the builders still not willing to finish the work up to standards
Part 14 - Final fight to get the shower/bathroom finished. More defects to go.
Part 15 - Another Tribunal hearing and details.
Part 16 - How strata owners corporation "solves" problems.
Part 17 - Final fixes and owners corporation costs. 5 years into the process!

No finished yet - stay tuned!

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