New month new round of tidbits.
IASA Israel chapter 2nd meeting
This Thursday (July 8th) at 17:00 Israel time, IASA Israeli chapter is holding its 2nd meeting. I am going to be there moderating the discussion on Architecture and Lean/Agile projects if you are around Raanana feel free to join
SEI webinar on software architecture
Another software architecture related event going on on July 8th is a SEI webinar on What’s software architecture by Rob Wojcik the webinar will take place on July 8 from 1:00 to 2:00 EDT. Looks like it is going to be an interesting listening if you are new to Software architecture.
Business Analysis Agile survay
Since my blog is also published in DDJ I get a lot of PR requests from all sorts of places, most of them end in my Junk email (if the SPAM filters doesn’t catch them first). From time to time something a little more interesting crops up. This time it was this survey ran by requirements.net , the International Institute of Business Analysis (IIBA) and capgemini.
What’s interesting about this survey is that 52% of the respondents were in business analysts (or BA management) roles and that 62% of the companies they work with had 1000+ employees. So we get some views of non-devs from large companies.
What I see in these results that Agile (with a capital A) is very much in vogue so everybody wants to say they are practicing agile even if they just moved to an iterative cycle within the same old waterfall process or as the survey word it:
“Comments from participants demonstrate that many in IT Management desire to maintain current processes and organization structure, while delivering iterative development cycles. Of course, this often results in a hybrid Agile-Waterfall methodology which is commonly referred to as “Scrummerfall” [ARGO: I guess that’s pronounced Scrum-fail” :) ] or “Wagile.””
Also it seems a lot of people don’t really understand agile by thinking that SCRUM is a synonym for agile; thinking that product owner and scrum master are a logical fit to be the same person (46%) rather that dev and QA (only 11%); leaving the business analysts as “requirements authors” (42%) rather than having them as part of the “client team” (as Subject matter experts (21%)) or product owners (16%) etc.
I guess the direction is what’s important :)
Illustration by esc.ape(d)