ingvald
An internally focused exploration of an idea is different from an externally focused one. In my experience, noticeable differences have been related to market, revenue, customer etc. F.ex, relatively small potential improvements in work within main value streams could clearly dwarf size of investments, or have been considered already.
Anyway, here’s a kind of intranpreneur canvas that’s been useful for me a few times lately when thinking about building new software.
This week I spoke at a couple of conferences.
In case you’d like to take a look at the (info)slides, a pdf is available, or you can take a look in a viewer below.
“What should I work on next?”
Yuval Yeret quotes David Anderson:
See also Al Shalloway on Lean thinking about waste in software development – it’s not about optimizing and reducing the use of “resources” (to quote a tweet by @drunkcod).
So I don’t have much time for hobby projects… And when I do have time, it is from various computers, with various setup.
That’s why I’m testing the following combination of online services, and so far it looks promising for my needs…
Being busy all the time is bad for you, your team, and your organization. It is far better to allow for slack, which is not a bad thing, but creates opportunities for improvement without needing to schedule them.
“Recipe” for what to work on next, incorporating slack:
A bit more reading related to slack.
Denne artikkelen ble først lagt ut på blogg.bouvet.no.
Det finnes mange ulike beskrivelser av Kanban. Er du interessert i å vite litt mer om hva det egentlig er?
At LKNA13 in Chicago this year I listened to @JoshuaKerievsky talk about #techsafety.
He made me think about quite a few aspects of safety and injuries for a programmer. Here’s a few quotes and elements:
What’s interesting is his claim that having #techsafety as a primary value would be profitable and produce outstanding results. I think I buy into that, even if he hasn’t had time to prove it yet with his own company, @IndustrialLogic.
A few twitter notes from the session.
Edit: Joshua have written on #techsafety himself:
Yesterday I attended TDC.
It was fun to see so many from the software development community in Trondheim turn out all at once.
I also had a short talk about better ways to work, focusing on delays and feedback – especially how it’s more central to knowledge work than we think.
Here’s the slides if you’re curious (PDF):
201210 TDC Better ways to work
Update: I added a few slides for a talk at the office – see extended version (pdf) if you like, containing a few more links/ reading tips.
What is an operations review (ops review)?
To do an ops review is to take a look at your team or organization:
Why should you do ops reviews?
I just got involved with a mobile project, and let my inner devop out for a moment… So, here’s how I got Jenkins to build, sign, and deploy an Android app for testing.
Our setup:
The gist of the Jenkins job is:
/opt/android-sdk/tools/android create project -n [name of resulting app file] -t [Android target] -p [name of temporary directory where project is copied and ant files generated] -k [package] -a [default app class]
sdk.dir=/opt/android-sdk target=[Android target]key.store=path-to-keystore key.alias=[alias] key.store.password=[pw] key.alias.password=[pw2]
And on my phone:I got useful info from an article on jenkins-ci.org: Getting started: Building Android apps with Hudson. My needs were a bit simpler, so you’ll see a bit more details there than here.
A few problems I had:
This project is a side project with low activity compared to a day job, so right now this job is a one-click deploy job (one click plus downloading and installing on the phone…) However, I think we’ll set up nightly polling, so there’s an updated app available every morning for testers, and they can see by the timestamp if there were any updates the previous day.