British Expats - Australian software processes

Page 2 of 2

Show 40 post(s) from this thread on one page

British Expats (https://britishexpats.com/forum/)

- Australia (https://britishexpats.com/forum/australia-54/)

- - Australian software processes (https://britishexpats.com/forum/australia-54/australian-software-processes-690146/)

mpgrewal

Oct 21st 2010 3:21 pm

Re: Australian software processes

Quote:

Originally Posted by DunRoaminTheUK (Post 8932649)

StyleCop is really more like StyleNazi...

It is certainly a pain to follow CAxxxx standards for the first time. But once you read CAxxxx definition that why that design standard is prescribed, you appreciate it and obey it. :thumbup:

I remember getting around two thousand stylecop errors when i used it for the first time and took 2 days to manually address each of them :(

hoofie2002

Oct 21st 2010 3:40 pm

Re: Australian software processes

Quote:

Originally Posted by mpgrewal (Post 8931940)

Becomes a compulsion if you are developing a commercial product. I was referring more to consulting projects which tend to overlook these processes due to squeezed budgets.

Hmm.. will surf further:)

There is no reason you cannot use Agile, Scrum, XP etc on consulting projects. In the end, if the customer gives you X money but wants Y value, they will still only get X's worth delivered and no amount of pissing about, gantt charts etc. will change that.

The best analogy is a washing machine. It will take a set amount of time to wash the clothes. You can't look at it shouting "spin faster you bastard !" - it will still take the same amount of time.

hoofie2002

Oct 21st 2010 3:44 pm

Re: Australian software processes

Quote:

Originally Posted by itxrd (Post 8933081)

I agree with what you've seen so far. As with any of the models its one thing in theory and another in practice. Agile if followed correctly is good but most of the time its not. Not by a long shot as its very easy not to follow it correctly. Turns into lets just bumble along, get it all in as quickly as possible and there you go. No proper planning, static testing done beforehand

You are spot on. Agile is hard to implement and to stick to, although it gets easier as time passes since it becomes second nature. Many people claim to be 'Agile' but when you look at it they really aren't bothering. Self-managing teams seems to cause may problems - in many corporate environments the managers can't get their heads round the idea that the 'team' will drive the timeline.

mpgrewal

Oct 21st 2010 5:53 pm

Re: Australian software processes

Quote:

Originally Posted by hoofie2002 (Post 8934915)

the 'team' will drive the timeline.

And these autocratic managers won't accept it:thumbdown:

DunRoaminTheUK

Oct 21st 2010 6:03 pm

Re: Australian software processes

Quote:

Originally Posted by mpgrewal (Post 8935052)

And these autocratic managers won't accept it:thumbdown:

Sounds like what where I does work...

BadgeIsBack

Oct 21st 2010 10:12 pm

Re: Australian software processes

Quote:

Originally Posted by hoofie2002 (Post 8934915)

I've done most of the OP's listed points in many roles here. I've used UML a fair bit and wish people would use it more.

Most shops have CI, unit testing and code review. Some have agile. I believe you just have to pick and choose.

Sometimes agile is just a case of 2 week sprints and a daily standup. Fine by me - I like it that different companies do things differently.

All times are GMT -12. The time now is 12:13 am.

Page 2 of 2

Show 40 post(s) from this thread on one page