West side

Spent two days last week in Gothenburg with all the nice colleagues at our main office.

A lot of business development discussions involving our Vinnova projects, product management and software/system architecture for agile or lean organizations.

As usual it was great fun and a learning experience. Thanks all.

Tomas Sandén discussing model-based systems engineering

Product Development

Sometimes product development succeed, sometimes the customer is forgotten somewhere in the process.

Mag+ from Bonnier (thanks for the tip Tomas) is one example which even makes a skeptic - me - like the idea of a reading plate.

MS Surface at least makes for an awesome parody video.

Enjoy.

Mag+

Mag+ from Bonnier on Vimeo.

Surface

An interesting quote

I don't know how I ended up there yesterday, on some random guy's Twitter page... so I can't provide a link to it...

But anyhow he, the random guy, wrote this:

"SCRUM brings coordination of action, which is critical. Software architecture brings coordination of intent and insights."

Maybe not the most shocking or difficult line to come up with but hey he wrote it and I didn't... I kind of wished I did though 'cause I like it.

So if you look at it from that perspective how do you coordinate intent and insight? Maybe we should embrace that there is more to it than producing documents, excel sheets and UML-models? That there is a lot more to "architecture" than the technical aspects that we somehow like to indulge a little bit too much in?

The first thing I would start with I would steal/borrow/use from Scrum and the agile "world" where one common theme is the importance of Product Management. Step one for "Architecture" would be to reconnect (or strenghten the relationship) with Product Management in order to increase the insight in both ends.

Step 1 from a bigger perspective would probably be to look at Product Management directly so that "architecture" (and everything else) has something functional to reconnect to...