Some random “things” that I will take away from the CSM-course:
If you need a lot of system design you should still parallelize design and implementation (i.e. do it within the sprint) but it would be wise to add a Sprint Zero focusing on system design alone. This sprint will most probably be a little bit longer than normal sprints (depending on your system).
I will probably take a look at the book Software by numbers.
Ok I’ll cave; using modeling-terminology Scrum can be seen, roughly, as an instance of “Lean”. At least most of the basic principles, or values, are the same.
The Spec/Developer game that we played at the training should be played in every organization… the quick lessons learnt from that one are so easily neglected on an everyday basis.
When e.g. building cars or similar products there are a very strong focus on time, technology and cost, why is value repeatedly left out of that equation? Ok this one is not from the training itself but in Scrum the focus is on value and if anything you should, when prioritizing, look for at least MMF, Minimum Marketable Feature.
I should revisit the agile architecture work together with Peter and Peter. We are on the right track there and architecture is one of the difficult questions when talking Scrum. The answer at this course was that “architecture and infrastructure are highly prioritized non-functional requirements”.
Scrum in large organizations is difficult. Scrum in large organizations developing embedded products is even more difficult. But then again it is difficult using waterfall as well.
fredag 29 januari 2010
Tick tick
Just finalized the CSM-training by completing the online certification test and thankfully I passed... piuh. Ok, currently everyone pass since they are tuning the tests but you never know... anyhow I think my score would have been enough either or; not the most difficult of exams.
torsdag 28 januari 2010
Quote of the day... yesterday...
Here’s one of the more memorable quotes from the CSM-training yesterday (as a reply to a lot of tedious questions).
"Just because we use Scrum it doesn't mean we should stop thinking"
I'll try to summarize said notebook tomorrow and see if I have anything insightful to say after a, I must say, quite good training course.
"Just because we use Scrum it doesn't mean we should stop thinking"
I'll try to summarize said notebook tomorrow and see if I have anything insightful to say after a, I must say, quite good training course.
måndag 25 januari 2010
CSM
Two days of backlogs, sprints and burn-down charts coming up, after that I'll probably be a little bit wiser and a certificate richer. I took a Scrum-course back in 2008 and it was really good, hopefully this one will be interesting too even though I guess I won't really learn anything new. However if there’s a good mix of people the discussions around the training-subject can sometimes be way more interesting than the actual material itself.
Wednesday evening we’ll know.
Wednesday evening we’ll know.
torsdag 21 januari 2010
Early weekend
Slow week on the far side of the blog busy nevertheless. Modprod is closing in and the message in my talk is getting there…
Reviewed a presentation from a colleague earlier this week and found two topics extra interesting in his talk; the evolution of PD connected to the market-development and the “architecture” of agile.
Seen similar slides before but liked how these where packaged.
Maybe something I will get back to here after some further discussion.
Thinking/working/sweating a lot in the context of marketing during the start of this year, maybe I should just do what Jack does?
Well time to get packing for that Åre-trip, packing is best served together with Teddybears STHML.
Crank it up high cause "them drum machines ain't got no soul" (thanks for the tip Tomas).
/ Out.
Reviewed a presentation from a colleague earlier this week and found two topics extra interesting in his talk; the evolution of PD connected to the market-development and the “architecture” of agile.
Seen similar slides before but liked how these where packaged.
Maybe something I will get back to here after some further discussion.
Thinking/working/sweating a lot in the context of marketing during the start of this year, maybe I should just do what Jack does?
Well time to get packing for that Åre-trip, packing is best served together with Teddybears STHML.
Crank it up high cause "them drum machines ain't got no soul" (thanks for the tip Tomas).
/ Out.
tisdag 19 januari 2010
fredag 15 januari 2010
Analysis to design
Currently involved in a lot of more business related tasks but I get to squeeze in some technical thoughts in between as well.
One that I’m exploring a bit is how xtUML and “MDA” ideas could be used to create separation of concern between very abstract analysis (or maybe “architecture” if you like) models and design models. Of course it is not so much the separation of concern I’m after as the possibility to do model to model transformation, but “soc” feels like a necessary means to achieve just that ;)
In my head, maybe I’ve got it wrong, this is initially not so difficult to achieve but when you put it in context it suddenly become a tad more problematic. Especially since it is not the pyramid-structure of transformation I’m after (you know, the “Babushka” structure…) but something a bit more intelligent where the transformation would handle e.g. cases where you go to different levels of abstraction in your analysis (because different problems require more or less details to analyze), where you could apply different patterns to solve various problems etc etc
One question though, and slightly important too, is if there would be a business case to do it this way. Another way to do it would be to kick-start with analysis models and let them evolve into design models over time (this could be a beneficial option if you don’t connect any value to the analysis model themselves and want to be able to re-use them etc).
Anyone with thoughts/ideas?
Well back to more “management” tasks.
One that I’m exploring a bit is how xtUML and “MDA” ideas could be used to create separation of concern between very abstract analysis (or maybe “architecture” if you like) models and design models. Of course it is not so much the separation of concern I’m after as the possibility to do model to model transformation, but “soc” feels like a necessary means to achieve just that ;)
In my head, maybe I’ve got it wrong, this is initially not so difficult to achieve but when you put it in context it suddenly become a tad more problematic. Especially since it is not the pyramid-structure of transformation I’m after (you know, the “Babushka” structure…) but something a bit more intelligent where the transformation would handle e.g. cases where you go to different levels of abstraction in your analysis (because different problems require more or less details to analyze), where you could apply different patterns to solve various problems etc etc
One question though, and slightly important too, is if there would be a business case to do it this way. Another way to do it would be to kick-start with analysis models and let them evolve into design models over time (this could be a beneficial option if you don’t connect any value to the analysis model themselves and want to be able to re-use them etc).
Anyone with thoughts/ideas?
Well back to more “management” tasks.
Aeroplanes
Lot of things going on today but with the huge game coming up this weekend I have to do a "non-work" post.
Rex Ryan has a lot in common with the old Swedish soccer coach Tommy Söderberg, besides the look they both use management by “positive attitude” to build confidence for the underdog.
Hopefully it will pay off against the charging bolts on Sunday.
J E T S Jets Jets Jets
Rex Ryan has a lot in common with the old Swedish soccer coach Tommy Söderberg, besides the look they both use management by “positive attitude” to build confidence for the underdog.
Hopefully it will pay off against the charging bolts on Sunday.
J E T S Jets Jets Jets
torsdag 14 januari 2010
Kanban & architecture
Just paused for a minute with a fresh cup of coffee and wandered off towards architecture in my mind.
Can Kanban be used by an architecture team? I tend to believe so even though I haven’t had a chance to prove the theory in practice (would be interesting though to hear anyone who has). Working with architecture has a very service-oriented side to it and tends to be somewhat interrupt driven. Additionally in large organizations it is easy to swamp the architecture team with work and as the stack in the inbox gets higher the focus and completion rate decline. Additionally other tasks, part of the normal process, are chunked in so big pieces that it is very easy to lose track of the target.
With Kanban you could get a tool to prioritize between the “service jobs” and “normal tasks”. Additionally you would have to create more tangible chunks of work which give you a sense of progress.
And if you still fail and are just drenched in work the Kanban-board would be a good visualization of just how much you and your team are trying to do… or maybe you are doing things you shouldn't?
Would be interesting to try at some point.
Can Kanban be used by an architecture team? I tend to believe so even though I haven’t had a chance to prove the theory in practice (would be interesting though to hear anyone who has). Working with architecture has a very service-oriented side to it and tends to be somewhat interrupt driven. Additionally in large organizations it is easy to swamp the architecture team with work and as the stack in the inbox gets higher the focus and completion rate decline. Additionally other tasks, part of the normal process, are chunked in so big pieces that it is very easy to lose track of the target.
With Kanban you could get a tool to prioritize between the “service jobs” and “normal tasks”. Additionally you would have to create more tangible chunks of work which give you a sense of progress.
And if you still fail and are just drenched in work the Kanban-board would be a good visualization of just how much you and your team are trying to do… or maybe you are doing things you shouldn't?
Would be interesting to try at some point.
måndag 11 januari 2010
Automotive transformation
Here you can find a long but interesting article on Automotive (from the Wall Street Journal) and an industry going through a revolution.
"The most remarkable aspect of last year's bailouts and bankruptcies is how auto-industry neophytes cut through craziness that had existed for decades. GM didn't know its cash balance within half a billion dollars on any given day. "
"After careening from one disastrous decision to another between 1999 and 2006, Ford had come to grips with its fundamental need to change. The company changed CEOs and is now shedding debt, dealers and brands without federal funding. Ford isn't home free, but its progress provides proof that GM and Chrysler could have avoided bankruptcy too with better leadership, and the willingness to act decisively before it was too late. "
"The most remarkable aspect of last year's bailouts and bankruptcies is how auto-industry neophytes cut through craziness that had existed for decades. GM didn't know its cash balance within half a billion dollars on any given day. "
"After careening from one disastrous decision to another between 1999 and 2006, Ford had come to grips with its fundamental need to change. The company changed CEOs and is now shedding debt, dealers and brands without federal funding. Ford isn't home free, but its progress provides proof that GM and Chrysler could have avoided bankruptcy too with better leadership, and the willingness to act decisively before it was too late. "
No progress
So far it has been a bit frustrating today, I’ve got several important issues on my table but no real progress to report of.
Reading through the papers and the circus around SAAB Automobile continues, personally I hope that it somehow works out for the best for the Trollhättan people but honestly the business case for long term survival doesn’t really seem to be there (at least not what one can depict from reading public material). Even so I find it a bit irritating reading through some blogs from prominent persons where they give themselves credit for “predicting” difficulties for SAAB a year ago… I mean, did anyone predict anything else? If you are one small non-profitable piece of a huge non-profitable organization the math is quite simple; SAAB is not the only thing at stake here. That Spyker or Genii would able to procure SAAB through their latest bid has great odds obviously…
…but great odds doesn’t mean impossible.
Well, time to get back to some marketing material.
Reading through the papers and the circus around SAAB Automobile continues, personally I hope that it somehow works out for the best for the Trollhättan people but honestly the business case for long term survival doesn’t really seem to be there (at least not what one can depict from reading public material). Even so I find it a bit irritating reading through some blogs from prominent persons where they give themselves credit for “predicting” difficulties for SAAB a year ago… I mean, did anyone predict anything else? If you are one small non-profitable piece of a huge non-profitable organization the math is quite simple; SAAB is not the only thing at stake here. That Spyker or Genii would able to procure SAAB through their latest bid has great odds obviously…
…but great odds doesn’t mean impossible.
Well, time to get back to some marketing material.
torsdag 7 januari 2010
Possibilities
New year but still in need of new people, hope you haven’t missed that we at Know IT Technology Management are recruiting in Linköping, Stockholm & Gothenburg.
Additionally I've got a very interesting meeting scheduled for tomorrow discussing seminars during the spring. I’ve got one up my sleeve that hopefully can see the light of day.
Additionally I've got a very interesting meeting scheduled for tomorrow discussing seminars during the spring. I’ve got one up my sleeve that hopefully can see the light of day.
Life in technicolor
Been a lot of powerpoint management today... and not sure if I am to pleased with the result. What I really should do is to go back to the white board and practice the talk without any aid but a pen... whatever I scribble down on the board is what I should put in the presentation.
But then again, when the powerpoint is supposed to be left behind it needs to be able to tell a story on its own... ah well, I’ve sent the embryo on a peer-review and I think a gentle push in the right, or any, direction will be helpful.
But then again, when the powerpoint is supposed to be left behind it needs to be able to tell a story on its own... ah well, I’ve sent the embryo on a peer-review and I think a gentle push in the right, or any, direction will be helpful.
måndag 4 januari 2010
IBC Conference
Another conference confirmed. In April I will talk at the “Electronics in Automotive” conference hosted by IBC Euroforum in Gothenburg. Maybe I’ll see you there?
Prenumerera på:
Inlägg (Atom)