I was definitely thinking graduate roles, but you have to have some training or experience to get into them usually. She doesn't like the idea of BA very much, so may keep looking on the technical side of things, what training is available.
TwoSeven: For those people who seem to think that development is an unregulated industry, I might point out that it actually isn't. There are quite a few formal industry wide certifications that take quite a bit of experience and effort to gain, from The IBA, PMI, Prince2, PSP, ISO etc.
Hogwash.
I'll admit several of my colleagues have tertiary qualifications (even I have one). Even the odd doctorate.
But, to say that unless one has a tertiary ticket it prevents them from working in the industry is unfounded. I agree there are companies that might have policies insisting on a certain level of tertiary attainment. That doesn't mean the industry is regulated.
There's nothing stopping anyone without a formal CS education from starting up the next TradeMe, Xero, Google, Facebook, etc. - unlikely as that might be.
The same cannot be said of starting a law or medical practice for example.
TwoSeven: Then there are the basic trade skills such as Application/Solution/Enterprise architecture, professional software engineering/solution development (looking at a minimum of 3 year apprentice + 5 years just to get to the intermediate), or a Software Process Engineer (upwards of 10 years relevant experience).
Sounds like a marketing/recruitment agency ad line.
TwoSeven: There is a big difference from someone that can write code in a few languages in a small team and someone who can manage a team of several hundred software engineers in an enterprise project.
One is a management role, and the other an engineering one. No, they are not the same.
TwoSeven: I'd very much doubt that someone could just become a BA without some level of domain experience. On top of that the technical skills of requirements elicitation, data analysis and project management. However, like all of the sub-professions, there are entry level positions in each role.
If you're saying to be a successful/better BA, that real-world experience is essential, then I'd agree (I think). However, I don't think you actually _need_ a ticket to be a BA do you? Even if it's a BA for some startup.
I don't think there's any requirements to be a BA. Incidentally solution architect is a fairly senior position, most people need 10-15 years experience to get into that, and enterprise architect is a step up again. I'm just going through qualifications for those, self study, given I've been doing SA work for a while now.
Then there are the basic trade skills such as Application/Solution/Enterprise architecture, professional software engineering/solution development (looking at a minimum of 3 year apprentice + 5 years just to get to the intermediate), or a Software Process Engineer (upwards of 10 years relevant experience).
If you called Enterprise Architecture a "trade" around my gaff there'd be fisticuffs.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
Trusted
ID Verified
