Showing posts with label agile. Show all posts
Showing posts with label agile. Show all posts

Monday, 29 September 2014

BarCampLondon X

So that was a pretty busy weekend! Thank you to all the organisers and the sponsors for yet another amazing BarCamp London.

If you don’t know what a BarCamp is, go read about how it works, and then come back to read my notes on some of the sessions I attended.

Here’s a picture of all the sessions that the attendees ran over the weekend (that’s a lot!) and it doesn’t list all the random conversations, games and general meeting people that happened outside of the posted schedule.

devoxx4kids

Dan Hardiker @dhardiker

http://www.devoxx4kids.org/

  • one day workshop
  • aimed at age 8-16
    • 8-9 year olds treated a bit differently — they need a bit more guidance
  • with specific goals
    • make a robot
    • iOS game development
  • want to say “I made that”
  • one child been building iOS apps since age 6:
  • worldwide
  • dominican republic had > 1000 kids over 2 days
  • > 30% people who come are girls/women
  • generally 5 or 6 tracks selected from:
    • minecraft modding
    • scratch
    • python
    • lego mindstorms
    • raspberry pi
    • arduino
    • greenfoot
    • alice
    • kojo
    • iOS
    • mathbreakers
    • NAO robot
  • 4 sessions in a day
  • also go to big conferences and run devoxx4kids for the adults
  • first London event in June
    • got 95% attendance from people who signed up!!
    • 4 x 1hr sessions
    • 40 volunteers
    • had an 11 year-old fly over on his own (met his dad at airport) to run a group of 20 x 11-15 year-olds how to do minecraft modding
    • he also did a closing keynote
  • had the creator of greenfoot teaching how to build a minesweeper game
  • have a load of volunteers available to help children build stuff
  • have a show and tell at the end of the day
  • mindstorms:
    • build the main wheelbase
    • children add grab arms to grab a ball
    • get children to control by hand first
    • program the same steps (5 steps forward etc)
    • add touch & distance sensors
    • program to grab without hard-wiring distance

how to start a hackerspace

Matt Copperwaite @mattcopp

  • start a company - level of protection
    • limited company - need 3 people, can then state not for profit
    • community interest - lots of paperwork
  • business bank account
    • barclays have APIs, £50 cashback at the time…
  • insurance: paid £300/year
    • recommendation from London Hackspace
    • BIS will issue advice on this shortly
  • keep trustees involved
    • raise issues that split them: colour of the logo…!
  • system designed so you can cancel the membership at any point
  • get people signed up with open days
  • people really like laser cutters!

See current UK Hackspaces at:

kinect v2

Mike Taulty @mtaulty

  • v2 is £159 (cheaper than v1 at £199!)
  • HD video
  • infrared
  • depth sensor
  • can track up to 6 bodies (25 skeletal joints)
  • tracks depth from 0.5m to about 8m
  • infrared & depth is much lower res: 512 x 424 pixels
  • body index separates pixels of different bodies
    • lets you do green screen really easily
  • MS’s SDK is Windows only (doesn’t work with Windows VMs since it needs USB 3 & DirectX 11)
  • but libfreenect2 is an alternative open source driver for Mac/Linux

mobile network in a field

Sam Machin @sammachin and Kevin Prince @kevinprince

https://fieldphone.org at EMF Camp 2014

  • EMF Camp was c.1200 people
  • runs every two years
  • “a very british burning man” or “glastonbury for nerds”
  • aiming for phone calls but not data
    • mainly because of there was already fast wifi
  • just three base stations, so could simply architecture a fair bit…
  • using OpenBTS, Asterisk + Twilio & Heroku
  • Asterisk server sat in the on-site hosting centre
    • a refrigerated shipping container with servers on pallets
  • recreated phone supply chain by using Amazon & a tent
    • bought some Amazon burner phones on 30 day return…
  • SIMs were the hardest things to sort
    • wanted to play nicely with other networks
    • didn’t want people on real networks to connect to camp network
    • SIMs are pretty expensive: 50p to £1 each
    • hard to order in low quantities
  • bought OpenBTS boxes from RangeNetworks
    • startup in SF
    • mostly selling to small Pacific islands
    • massively cheaper than normal kit (c.$5K)
    • also put one in a search & rescue helicopter in Iceland
    • connects to someone’s phone as it flies over
    • locates to area of a football field
    • allows helicopter to call phone!
  • need spectrum to run in the UK…
    • O2 had some they had forgotten about ;-)
    • concurrent spectrum license: shared by 15 companies
    • better in other countries:
      • Netherlands: just need landowner permission
      • Germany: just need 30 days notice
      • Burning Man: use DARPA military spectrum not in use in the middle of the Nevada desert
  • antennas make a big difference
    • need a proper site survey
  • EMF Camp provide about 40 routers around the site
    • set up in locked portaloos! Datenklos (term from CCC)
  • created everybody’s accounts ahead of time
    • needed to map phone numbers to IMSIs
    • got people to type in last 4 digits of SIM
  • set up voicemail using twilio to record and forward via email
  • SMSs are harder if you need to store & forward
  • dealt with inbound calls by having a single central public number
    • call it and then dial 5 digit account number
  • added outgoing calls as well (via Twilio)
    • limited to c.3 minutes
    • but even so fairly cheap
  • also set up a few group rooms to see if people used them
  • stats:
    • ~200 SIMs handed out
    • ~100 attached users at any time
    • close to 100% coverage
    • about 1800 minutes of twilio
  • ideas for next time:
    • phone boxes
    • POTS to tent: turn up and plug in a BT phone!

managing CSS

Ben Scott @BPScott

http://reload.me.uk/talk-structuring-css

  • people keep on writing new CSS
  • not obvious how and where things are used
  • no confidence in what you can change and if it will break anything
  • build smaller isolated things
    • single responsibilities

structure

  • components
    • domain-specific objects
    • text next to image in a particular way
  • macro layout
    • grid system
    • layout of components within a page
  • theming
    • colouring of components

resulting composition

  • this thing, here on the page, in this colour
  • mobile first & extend from core functionality
    • much easier to reason about adding in CSS
    • harder to take things out
  • use additional classes to toggle additional behaviour
  • Brad Frost: atomic design
    • pages are accidents — what happens when you put components in a particular order
  • create a styleguide page
    • component, layout variations
    • automatically generated from HTML partials in application
    • HTML partials are essentially custom tags

tips

  • avoid using IDs in CSS selectors
  • try to keep selectors to max 3 levels
  • naming convention: BEM
    • double underscore = within
    • double hyphen = modifier

problems & breaking up

  • mobile first, but oldIE needs to be desktop first as it doesn’t understand media queries
  • could use respond.js but takes a lot longer to load
  • created Breakup
    • SASS/Compass plugin
    • generates different CSS files from the same SASS input
    • according to directives in top-level
    • lets you avoid wrapping specific elements in media queries

real life brain training

SenseLabs http://getversus.com

  • split activity into different frequency bands = EEG
  • delta < 4 KHz
    • babies have this all the time
  • theta 4 - 7 KHz
  • alpha 7 - 14 KHz
  • beta 15 - 30 KHz
    • focused
  • gamma 30 - 100 KHz
    • complex active stuff
  • other stuff:
    • Mu (8 - 12 KHz)
    • SMR (13 - 15 KHz)
  • neurofeedback
    • constant feedback, close to realtime (~200ms)
    • useful to use more than one sense to enable different people to relate to it better
  • current system has five measurement points
  • Chief Science Office is Leslie Sherlin

training

  • focus:
    • augment low beta
    • inhibit theta & alpha
  • can train stress response too
  • sports consistency
  • exam preparation

problems

  • QA engineer was overusing focus training
  • had problems sleeping…

uses (not scientifically proven)

  • worked with Felix Baumgartner
  • tennis players
  • reported to alleviate long term ADHD…
  • improved sleep patterns amongst developers…

available systems

  • medical
    • existing $10K for bare minimum
    • require expensive software, only run on Windows XP
  • kickstarter systems
    • cool, but not much neuroscientist input
    • not so accurate or useful
  • versus
    • looks like headphones
    • rebaseline every time you put it on
    • connects over bluetooth to iPad
    • uses dry spikes sensors that contact scalp
    • first consumer product $750, aiming for $500

toys & gadgets

  • thalmic myo
    • bluetooth armband picking up arm and hand actions
  • oculus rift
  • NFC ring
    • lower range than usual
    • internal and external tags (private & public?)
  • Google Glass
  • estimote beacons
    • use at least three to get indoor location fixes
    • google have set up mountain view…
  • chromecast
    • don’t bother with a digital picture frame — just get a cheap TV and one of these
    • great for broadcasting any media around the house
  • almond+ touchscreen router & home security
  • 3D printer
    • check out 3d printer subreddit
    • solidoodle
    • arduino will be launching one v. soon
  • MIOPS camera trigger
    • plugs in to flash hotshoe
    • light sensor
    • laser sensor

scaling agile

Matt Walton, Head of Product @ FutureLearn @matt_walton

spotify

  • have documented a lot of their processes
  • think it, build it, ship it, tweak it
  • now about 2000 people
  • squads consist of engineers, designers & agile coaches
  • autonomous teams with long running missions
  • spotify engineering culture
  • “agile at scale requires trust at scale”

GDS

  • lots of information radiators
  • product roadmap split into team “swimlanes”
  • have a scrum of scrums

songkick

  • similar teams
  • each team needs:
    • product management
    • design lead
    • tech lead
  • how to organise a roadmap
    • KIPs broken into themes
    • time box themes
    • agree measurements
    • form autonomous team
  • lean analytics (book)
    • ratio or rate, not a total number
  • business focussed aims:
    • if … then … because
    • based on lean analytics experiments
  • two backlogs: separate “hygiene”
    • then add 70% valid features, 30% bugs, tech support to each iteration

futurelearn

  • product strategy themed by vision areas
  • each sprint split by % of work for BAU, products, etc
  • standups and retrospectives still whole team to encourage community
  • though work done in smaller project teams

conclusion

  • share vision, mission & values
  • give autonomy and create community
  • rhythm & reflection

Sunday, 28 October 2012

Droidcon London 2012, Day Two

The second day of Droidcon London — and they kept us going from 9am until 7pm with a full programme! As with the previous day, the keynotes were focussed on how Android is being used in non-phone devices — extending the rule of configurable software over fixed hardware.

I’d really like to add the slides to these notes — the Flurry presentation especially has loads of useful information that I didn’t catch. If any of the authors read this — please get in touch via twitter or leave a comment and I’ll add a link!

Future of Android - Vendscreen

Paresh Patel

http://www.vendscreen.com/

  • touchscreen device that fits as an extension on any vending machine
  • accepts credit cards via swipe + tap to pay
    • chip & pin coming later
  • network connected — makes the machine smarter
  • can cluster machines
    • e.g. lots of machines in a hotel
    • customers can get inventory from their phone
    • energy management — can turn off some
  • example: sold small artwork pieces in a vending machine
    • people weren’t surprised
    • prices didn’t have to be low
    • people paid up to $99 by swiping their card
  • right now running Android 2.3.4
  • minor modifications:
    • got rid of desktop
    • added a recovery screen

Future of Android - Parrot Asteroid

Frederic Albinet

http://www.parrot.com/uk/products/hands-free-car-kits/parrot-asteroid

  • parrot asteroid Android car radio
  • classic & mini using Android 1.5(!!?!)
  • tablet and smart devices using Android 2.3 (still old…)
  • does voice recognition search for contacts and music
    • music searches across connected device and also the internet radio stations and other sources
  • parrot app market
    • will be live from november
    • can browse from PC or from device
  • looking to extend to dynamic network between vehicles
    • though this would depend on other cars having devices with the same protocol…

ADzero phone launch

http://www.justadzero.com/

  • world’s first bamboo smartphone
  • quad core device
  • full HD screen
  • bamboo feels really good to hold
  • flash innovation: circle around the camera — works much better for macro

building songkick

Akshay Dashrath and Jamie McDonald, Novoda

  • took 2 devs 3 months to build initial version
  • agile process, two week iterations
  • tools used:
    • pivotal tracker
    • github
    • maven
  • third party libs:
    • ActionBarSherlock
    • ViewPagerIndicator
    • Novoda ImageLoader & Novocation
    • NovodaTime — dealing with Joda Time problems

user experience design

  • spent a lot of time finding pain points in initial install process using paper prototypes
  • found out that putting buttons in the action bar were not found by users
    • mocked up on an actual device to see how it felt
  • can set a custom notification light colour (works well with branding!)
  • styled login web view to look like rest of app
  • first launch experience:
    • had a scan screen with an OpenGL animation to keep the user entertained while the initial artist information is found
  • used external apps that expose content providers
    • google music — got artist names using a projection and flexjson to push it to songkick server
    • last.fm

caching & location

  • used novoda’s novocation location library
  • used Jackson mixture of streaming & tree model to avoid memory issues
  • data from web calls loaded into database, then database loaded into views with cursor loaders
  • detachable result receiver — google IO 2011 app
    • lets you deal with rotating views and re-attaching the new activity to the old cursor loader
  • all visited content cached using Reto Meier’s Big Cookie approach (see Making Good Apps Great)
    • “Just Added” concerts sync in the background
  • if offline, then shows a transparent banner at the bottom of the page
    • send out a sticky broadcast if an online query fails
    • broadcast cleared if the app gets a good response
  • Big Cookie caching can build up too much data
    • data removed on a daily basis by removing old data — e.g. past concerts, etc

testing

  • manual QA for most stuff
  • automated tests were more for stress testing
  • also did observational user testing (one-way mirror room)
  • put UI options in a debug menu so could easily do A/B testing
  • build machine runs instrumentation tests on however many devices are plugged into it
  • used Eclipse Memory Analysis Tool to check memory allocation
    • used to fix large back stack activity
    • enabled StrictMode to deal with issues with Google Analytics & Joda Time
    • Joda Time used the UI thread for DST settings (can be fixed — see Stack Overflow)
  • got featured in Play
    • installs went 400 / day -> 20,000 / day!

soundcloud audio in Android

Jan Berkel and Jon Schmidt, SoundCloud

playback

  • Java MediaPlayer talks to C layer MediaPlayerService
    • check out the C source code to see what’s going on
  • underneath this uses PacketVideo OpenCore up to 2.2, then Google Stagefright
    • shouldn’t have to care about underlying implementation but if you’re doing something complicated you do…
    • OpenCore
      • mature, stable but limited
      • seekTo doesn’t work in streams
    • Stagefright (default from 2.2 and beyond)
      • fixes seeking
      • but not available in all devices…
  • when launched shortly after 2.3 released decided to support 2.1+ so that could cover 75-80% of devices
  • to find out which mediaplayer, tried to read /system/build.prop
  • however, some phones had both frameworks!
    • one for streaming and one for encoding…
    • playing locally would behave differently than streaming from a server
  • so to actually find out, connect the MediaPlayer to a local socket and read the user agent on the other end…
  • built a StreamProxy local server
    • could cache and fetch chunks from CDN
    • MediaPlayer then talks to proxy
    • inspired by NPR android app
    • but still no control over buffering (may want to alter it depending on network conditions)
    • different versions of Android behave differently
      • ICS has a huge buffer so takes ages before it starts playing…
  • bundled Android HttpClient is broken (it’s an old snapshot, not a proper release)
    • have to catch NPE from execute!
    • recommended to use standard Java URLConnection
    • bundled HttpClient has now been deprecated

recording

  • live encoding options on earlier Android versions — just AMR AB
    • only good for voice
    • narrow range, low quality — sounds like a phone call
  • instead recorded in PCM and used 3rd party lib to encode it before uploading
  • chose ogg vorbis
    • good for licenses
    • java port is slow (and incomplete)
    • would take 4x length of audio to encode!!
  • from 2.3.3 Android introduced AAC encoding
  • new requirements involved getting at the actual audio data — simple editing, resuming record
  • had to write own native layer for codecs and audio processing (Java too slow)
    • used C-based Vorbis Encoder & Decoder with a thin wrapper
    • also added a native amplitude analyzer
  • tried to avoid sending data back and forth too often
  • but… now had to deal with CPU flavours
    • armv5 on older devices has no floating point support
    • have to build native pieces for various architectures (armv7, mips, x86)
    • older devices fall back to old-style encode later style
  • Jelly Bean has new media encoding APIs
    • will be useful in the future…
  • some sony devices have a patched media framework that behaves differently…

bug detection

  • robolectric
  • bugsense crash reports
  • get a load of devices and get people to use them

The fly-in app menu for designer and developer

Cyril Mottier @cyrilmottier

  • watch out for activity back stack
    • recommended to only use fly-in menu at root level
    • but still want the back button to exit the app without going via the fly-in menu
  • libraries (all on github)
    • android-undergarment
    • slidingmenu
    • android-menudrawer
  • don’t slide the actionbar
    • you’d need a custom actionbar…
  • or create your own: need a custom view group & view
  • see “making of prixing”
  • make the slid out activity inactive
    • click on it to make it visible again
  • may need to think about right-to-left languages having right-sliding menus

Who needs thumbs? Android Instrumentation and Reverse Engineering

David Teitelbaum http://blog.apkudo.com/

I only caught the very end of this, but it looked like it could be a really useful talk — worth chasing down the slides

Android and Arduino

Fei Manheche, Robobo

  • 3 steps:
    1. build basic circuit & test it from PC (use serial monitor via direct connection or Bluetooth)
    2. build basic arduino software to set it up to be controlled from Android
    3. build Android app to talk to Arduino
  • bluetooth modules available for £6-10
  • use amarino library to simplify bluetooth between android and arduino
    • can also use amarino app to test basic bluetooth connection
  • don’t send too much data to the arduino at once (unless you write buffering serial code on the arduino…)

Memory Analyzer: avoiding memory leaks

Felipe Ferraz, CESAR

  • each process on Android has its own Dalvik VM
  • the Zygote process is forked for each app
    • it already has common libraries mapped into it, so they’re shared as read-only between all apps
  • use adb to make a heap dump (kill -10 <pid>)
    • or use Eclipse…
  • useful to create multiple heap snapshots to tell story of memory leak
  • http://www.eclipse.org/mat/
  • make sure to null Callables inside Images

Using Ubuntu to develop cloud-connected android apps

Victor Palau, Ubuntu

  • juju: https://juju.ubuntu.com/
  • orchestrates groups of servers deployed to cloud systems
  • can deploy a local instance or to Amazon ECS (or any other OpenStack compatible service)
  • local deployment uses zookeeper to set up containers on a single machine

Mobile Analytics - taking your Android app to the next level

Simon Podd, Director of Sales, Flurry EMEA

  • according to EMF there are 2Bn “affluent adults” in the world
  • 17% of time spent in Android apps is in Europe
  • time spent in apps is increasing month by month (94mins/day in Dec 2011)
  • social networking category is growing fast (equal to games in Q1 2012)
  • Flurry tracking 220K apps across 660m devices
  • iPad makes up 88% of top 3 tablet sessions
  • of the top 20 Android devices by worldwide sessions (May 2012), the top 3 are:
    1. Galaxy SII
    2. Galaxy Ace
    3. Moto Defy
  • worldwide 2011 app revenue (iOS & Android):
    • 52% in-app purchases
    • 24% mobile advertising
    • 25% app sales
  • advertising revenue (from Flurry’s ad slots):
    • iOS $6-10 eCPM
    • Android $20-30 eCPM

gaming category stats

  • ages 13-34 spend most time in apps
    • 18-24 & 25-34 about even
    • fairly even gender split
  • more money spent by 25-34yo men (29%)
  • average transaction sizes fairly constant across ages, and higher than you might think:
    • M: $15.60
    • F: $11.90
  • customers download on average 50-85 apps during a device lifetime
  • but they only use 5-10 apps a day
  • there’s an app discovery issue on the device

flurry tracking

  • can use ranges for event parameters…

Applying lean principles to enterprise mobile development

Dave Slocombe @daveslocombe — Head of Mobile Channel, lastminute.com

  • product scorecards
    • 5 or 6 key goals for the year
    • see Marty Cagan, SVG
  • keep time to release short
    • don’t miss the opportunity to innovate
  • avoid big bang releases
  • essentials: co-location & cross-functional

generating and managing ideas

  • ideas should come from all sides of the business
  • need to have a massive bucket of ideas
  • make them visible so you can choose amongst them
    • great for managing HiPPos (highest paid persons)
    • they can see that their idea is on the board
  • doesn’t mean that you have to work on them!
  • prioritise ideas
    • use the product scorecard

selecting ideas for development

  • UX team does customer insights
    • qualitative: what problems are we solving? is there a market?
    • quantitative: talking to data analysts
    • looking for strong signals
  • product owner reviews customer insights
  • UX team create designs in iterations, increasing fidelity as they go
    • want to be able to ditch bad ideas before spending too much time on them
    • try guerilla testing: take it to someone in a coffee shop and ask them what they think
    • get marketing and devs involved as well
  • get UX ideas out without using developer time
    • use axure or similar
  • have an internal site of proposed designs
    • available to exec team
  • play back early stage designs to other teams, like finance and supply
    • surface problems and feedback early
  • if ideas are generated, they can go back onto the ideas board (don’t deal with them right now)

development processes

  • retrospectives
    • done every two weeks
    • if you leave it longer, the issues get bigger and harder to solve
    • more frequent = smaller, easier to fix issues
    • e.g. found that they needed a “design issues” wall
      • edge cases found missing by the designer, not captured
      • introduced “creative coding” — designer + developer pairing, making a first pass of the UI
      • brings designers into what’s possible on mobile
      • helps devs understand value of brand & aims of user experience
  • Dave was originally a skeptic of pairing, but converted:
    • sharing knowledge
    • repeatability, consistency
    • drives out “hero developer” mentality

testing & releasing

  • “release process is the metronome that drives progress”
  • continuous deployment
    • every check-in should be deployable
    • repeatable consistent environments
    • currently 12mins to deploy to production
  • devices are tiered for testing:
    1. automated tests, max experience, manual test
    2. automated tests, optimum, limited manual
    3. observe trending, monthly testing, graceful fallback
  • just pushed iOS 3 down a level
  • looking at webdriver to generate PDFs for visual check

tying it together

  • showcase every two weeks
    • include other departments
    • no roadmap items, just value added in the last two weeks
  • focus on what your customers say, not what the industry says is cool
    • apps vs web — choose from your own analytics
    • e.g. for travel, 3x more likely to book on web
  • stats:
    • seen 10% month on month growth in Android, compared to iOS
  • ensure product always gives tech team 20% tech debt time

Replacing the Android emulator

Daniel Fages, Genymobile

http://androvm.org/

  • built on top of android-x86
  • has an emulated WiredSSID wi-fi connection
  • can use OpenGL 2.0 using hardware
    • works really well - can emulate Angry Birds
  • just added injecting sensors from attached Android device (accelerometer, etc)
  • currently working on management tool and other features
  • looking for feedback on next features
    • network
  • also can install VM on other people’s machines without having to worry about SDK
  • will be working to integrate with Jenkins
    • could be great for creating a snapshot when something goes wrong
  • not working:
    • multitouch
    • NFC, Bluetooth
    • GSM pieces: SMS & voice

Developing accessible apps for Android

Gary Readfern-Grey, RNIB

  • many people are relying on apps as the only way to do crucial things in life
  • talkback comes with Jelly Bean
  • problem:
    • icon-based buttons don’t have proper audio labels (“icon 39”, “icon 19”) so can’t find what is on the screen
    • watch out for “jump back button button”
  • accessibility came in on Donut 1.6
    • relied on physical keyboard and trackball
    • touching the screen behaved as normal and gave no feedback
  • Talkback and Eyes-free-keyboard added more recently
    • eyes-free added in Gingerbread
  • ICS brought in explore-by-touch
  • Jelly Bean brings in gestures:
    • moving focus
    • back, home, recent apps
    • notification shade
  • WebView is harder
    • Jelly Bean & ICS have an additional “allow web accessibility” checkbox

testing your app

  • download talkback from google play
    • Jelly Bean has it installed (at least on Nexus 7)
    • settings / accessibility / turn on Talkback
  • check that views are focusable and have content descriptions
  • custom views need hover events

documentation

  • Google I/O 2012 making android apps accessible on youtube
  • developer.android.com: making applications accessible
  • android 4.1 accessibility APIs

top things to do:

  • add content descriptions to your widget
    • can do in XML layout using android:contentDescription attribute
    • or use setContentDescription
    • latest linter should check for this
  • make sure you can get to all elements of the app through a keyboard
    • will also help for Google TV
  • don’t depend on colour alone…
    • e.g. “correct the field that’s coloured red”
  • test it! try out Talkback
  • RNIB Innovation can help you
    • RNIB offer paid consultancy
    • if they’re doing something that RNIB really want and aren’t in a position to pay, then they could offer free help too
    • innovation@rnib.org.uk

Tuesday, 29 September 2009

OverTheAir '09: Modelling the User Experience

Bryan Rieger — yiibu

Bryan comes from a theatre and animation background and was sorely disappointed by the tools available for designing interactive services. He and his partner Stephanie have developed a lightweight prototyping mechanism for interactive mobile services. I like the idea — especially the bit about throwing away lots of ideas in order to explore.

Tools for traditional animation

  • scripts & storyboards —> models & layouts
  • adding structure, but always changing
  • dope sheets, now known as timelines
  • pencil tests
  • animatics — complete but not finished
    • stills set to music/voice over, possibly panned and scanned

Tools for Mobile design

  • wireframes and… more wireframes
  • what are they?
    • layout, behaviour and flow all in one document
  • are we expecting too much from one document?
  • Bryan started dropping little nonsense text on the descriptions of wireframes to see if anyone was reading them — turns out nobody was!
  • documentation gets bigger and bigger but not readable
  • document management != design

Prototypes

  • where do you start and where do you stop
  • paper -> HTML -> Flash -> Python, Java, …
    • the more you get to development, the more people don’t want to tear it down
    • developers (and those who manage them) should learn the value of the spike — a throwaway prototype that you really do throw away
  • want to get something more concrete than paper but has limitations
    • really difficult to share
    • usually requires some mediation

Agile

  • iterations are good for design
  • you can explore more, develop new different ideas and throw away bad ones
  • how can I make lots of mistakes? how can I get visibility of the project as a whole?

Integrating knowledge from animation

  • applying animatics to wireframes
    • want something interactive, but still sketched
    • and the sketched part must include the flow and behaviour as well as the layout
  • disposable data models:
    • views, states and events
    • views and states are scanned in from paper prototypes
    • events switch from state to state or to different views
    • creating these is relatively easy, esp. using Fireworks as a tool
    • Fireworks allows you to create multiple states side by side, all based on a single view
  • can switch in different JPEGs really easily — iterate visual design
  • can easily alter model (flow & behaviour) by changing XML
    • at the moment, the XML is hand-built
  • player built using Mobile Processing, so runs on real devices (as JavaME midlet)
    • same player for any design — just load and go
  • models (including graphics) take about 1 day to create
    • so can create 60+ models over several weeks
  • is this system similar to Cascade Breeze, or PhoneGap?

Experience

  • created lots of documentation up front, but then started culling pages
  • shipped prototypes with the documentation
  • created 60+ models — allowed change
  • took 2 designers 9 weeks of work
  • led to clearer wireframes
    • but didn’t replace them — this is an additional tool
  • much greater user testing since lots of people could use it
  • slowly refining the tool:
    • adding gestures and touch interactivity
  • don’t model the whole app — just specific flows

Friday, 10 April 2009

BarCampLondon6: Get Google's 20% Time for Yourself

Flexible working has recently come under the spotlight — due to the change in UK law from the beginning of April, all parents with children under 17 are now able to request flexible working from their employers. Employers are only allowed to reject demands if there are “good business reasons for doing so”.

Parents often want to take time off to be with their children and to provide childcare during school holidays, but time off work is not just for looking after kids. Sometimes you might want to change the balance of your life and invest in your own ideas rather than those of a company.

This BarCampLondon session was a discussion on how you could take time for yourself, and what you would do with it once you’ve got it.

Introductions

  • Ben — a computer science student on his year out working for an ISP 2 days a week with flexible hours
  • Shadi — a “person of leisure”, problem solving for friends and family
  • Dale — working full time on flexible hours for a large IT company
    • shifted hours to be primary caregiver when first child was born, now wondering how to adjust hours to deal with second child
  • Adam — took off half a day a week when son was born; that time now used for himself since son is at school; recently thinking of moving to a full day off each week
  • Melanie — working full time but dreams of finding her own project; hasn’t found a solution yet
    • disappointed with work leaking in to personal time — e.g. people working on a Sunday to be ready for Monday morning
  • Anna — likes travelling; would like to have some work of her own she can take with her while she’s finding her feet in another country
  • Sarah — works full time but is setting up another company based in India in her spare time

Sarah’s experience

Sarah used to work for company similar to the one she has created. It was taken over a while ago, so she decided to set up something similar but better. She had a vague acquaintance who set up the contacts in India where development costs are very low (£300 per month!). At the moment she’s working on the English translation of the work done in India in her evenings, whilst working full time at her existing job during the day. This results in her working more hours than she would normally, but she has something of her own that she’s building up.

Ben’s experience

Ben is currently a student, trying to avoid going straight into full-time work. Instead, he’s working part time to his schedule. He has quit twice from his current employer as he didn’t want to work long hours. He wants to be able to work on his own projects.

Is working part-time really less hours?

Adam takes a day off every other week and gets to take that day completely for himself. However, Shadi used to work three days a week, but found that she was working until midnight to complete her tasks — her job was tech support so she had to get the customer back online. She also occasionally received calls on her days off if she was the last person to deal with a particular situation, asking her to deal with it. Since she had commitments to be in on certain days, she found she couldn’t alter her hours to compensate for working on her days off.

Ben pointed out that Carsonified have a company-wide policy to work a four day week — the whole office is closed on Fridays.

There’s also more choice than just full time or part time: some of Dale’s colleagues work compressed hours — working more hours a day, but four days a week. They still get paid full time. Others work longer hours during term time but have school holidays off so they can do childcare. See http://www.direct.gov.uk/en/Employment/Employees/WorkingHoursAndTimeOff/DG_10029491 for more information.

Sharing responsibility

As Shadi’s experience shows, you do need a job that can be put to one side — or a company environment that promotes sharing responsibility. Agile processes such as Extreme Programming make this a central part of the culture, not just to enable people going away but to encourage greater flexibility in the whole team. Hospitals also deal with sharing responsibilities regularly, with staff coming on and off shift but providing continuous cover.

Anna wondered whether the people sharing roles needed a certain level of communication skills in order to make this working style possible. Adam agreed: his company hire developers partly according to their ability to communicate in a paired programming exercise — the ability to clearly discuss what they’re working on is at least as important as being able to solve the programming exercise.

This approach clashes with a top-down, command and control culture: employees have to be able to trust their peers and communicate without going up and down the hierarchy. You can’t share a job with someone who you fear might take on your role and replace you when you’re not around.

When you have time to yourself, what do you do with it?

Setting up a new business is risky — so it’s good to balance it with the security of an existing job. Start-ups costs for online businesses are coming down — you can rent your servers in the cloud and only pay for as much CPU and bandwidth as you use.

There are also sites such as One Click Orgs which will enable you to set up a legal entity very quickly for little cost.

Sarah’s approach shows the value of capitalising on your experience — make sure that you’ve made the contacts and make sure that you build on them.

Involving other people

If you need to involve other people in your new venture, you have to balance their commitment with their involvement: if they’re doing you a favour for little money, they won’t necessarily work to your timescales.

Local currency systems like LETS (Local Exchange Trading Systems) can provide a community of people willing to help each other. The local currency is based on trust and disclosure, with everyone able to see everyone else’s trading history at all times. Members will hold to their commitments or risk other members never doing business with them (a bit like eBay reputations). Note that LETS are not a way of avoiding tax — if you’re operating a business that sells in LETS currency, you’re still eligible for paying tax on the income.

One of the original benefits of LETS schemes was the lack of interest on loans — you can easily have a negative balance and just agree to contribute more in the future. Given that bank interest rates are currently close to 0% anyway, this may not be such an incentive at the moment…

Anna pointed out that one of the most useful people to involve in setting up something new is a mentor — someone to get you moving and be there to provide advice on basic things like planning.

Tuesday, 22 July 2008

miniSPA 2008

miniSPA is the little brother of the BCS Software Practise Advancement conference, held over 3½ days each spring time. Instead of 2½hr sessions with breaks in the middle, we get one day of 75min condensed versions as a taster to the main event next year. And it’s free!

Each of the sessions was interactive in its own way — some depending on the attendees to provide content, other involving them in exercises and others just inviting discussion about a particular experience that was present. I went to one of each type and they were all well presented and food for thought.

Best Practices for Finding your way into new Projects - quickly…

Marina Haase

This was a workgroup session in which we were invited to brainstorm ideas and experiences that help us understand and get involved with a new project.

First of all Marina gave us a run-down of some the ideas that had been raised in the main SPA conference earlier in the year. These are covered on the SPA wiki, but the ones that caught my attention were the following three:

  1. Watch out for guru fear: the team you are joining may be apprehensive of new experts joining them — will they be told that what they are doing is wrong?
    • One way to defuse this fear might be to find areas where the existing team does things better and to mention those areas of expertise; another might be to find experts in the existing team and go to them for help
  2. Prepare questions beforehand — and make sure you take time to ask them
    • It’s all too easy to get wrapped up in the work and to hurry with your integration, but taking a step back is often very useful
  3. Write down things in your own way
    • Don’t just rely on existing documentation — take a notebook and write down descriptions in your own language. Writing things down can often be a better way of understanding them than just reading other people’s descriptions.

We then went on to brainstorm further ideas for getting into a new project quickly. The most interesting part of this bit of the session was the brainstorming techniques themselves — we were invited to try one of three methods, though all the groups in the room chose the same one: Metaphorical Brainstorming.

I’ve never come across this before, but it’s a great idea (and good fun too!) — instead of brainstorming directly on a subject, think of a loosely parallel situation and brainstorm ideas and techniques for that instead. Once you are done, spend some time figuring out how each of your ideas might apply in your original problem domain.

The brainstorms that worked best were the ones that took a slightly unusual scenario (one further away from the original problem) and then pushed it to its extremes. These generated ideas that we wouldn’t have thought of otherwise and gave the group a lot more energy in the brainstorming itself. A useful technique that I may end up using if a brainstorming team shows signs of flagging.

Sid and Nancy apply for Life Insurance: Storyboarding the Domain Model

Justin Forder

The second session I attended was a more traditional presentation, but discussion was encouraged from the start and the presentation evolved directly with the wishes of the audience, skipping some slides and focussing on others.

The topic was a new style of diagramming aiming to bring the domain model of a complex system to life. Often the domain model can get fairly big and complicated. While it is (usually) understood by the people who built it, the model can be difficult to describe to new joiners, and discussion of requirements and restrictions with the business team can be subject to misunderstandings. UML diagrams such as sequence diagrams and use case diagrams are meant to help here, but they can often be too detailed or too abstract to make sense without an existing understanding of the system.

In contrast, there are a lot of techniques used to bring the user interface to life — as this is the only way that it can be evaluated. Justin’s idea was to take one of the techniques from user interface design, storyboarding, and apply it to the back-end domain model.

A storyboard looks like a cartoon, consisting of a sequence of snapshots each showing an instant of the story and hinting at the movement within each frame. In user interface design, you would create a storyboard for a detailed, concrete scenario, with clearly defined actors trying to achieve specific goals.

Justin applied the same technique to the domain model resulting in a sequence of diagrams showing how the model is populated and how it changes as different actions occur. The final document told the story of the system in a way that lots of different people could understand; it was a powerful tool for new joiners, but also extremely useful for testers. Justin even used the same technique to help identify performance bottlenecks caused by repetitious actions.

In order to make the diagrams more complete, Justin invented some simple annotation styles which are well described in his actual presentation. This will probably make its way on the web via the SPA wiki at some point..

This storyboard is not intended to be the only documentation of the system. There are several areas, such as encapsulation and polymorphism that it does not show at all. Drawing the diagrams won’t particularly help to design the system in the first place — but it does help to exercise and illustrate an existing design.

The differences between this process and specific UML use case diagrams also raised a point about testing: it’s useful to remember the difference between use cases and scenarios when writing unit and functional tests. Scenarios have specific values and tell an end-to-end story. Use cases are more general — they often capture a lot of error cases — and are more individual.

Overall, storyboarding the model looks like a very useful tool for getting an overview of a bigger system and I will look out for opportunities to take advantage of it.

Effective Pairing

John Daniels + David Cleal

The final session I attended at miniSPA 2008 consisted of a series of exercises to evaluate the effectiveness of pairing. The exercises were intended to cover different kinds of tasks — analysis & planning, social situations, physical activities and creativity. Each activity was worked on by both pairs and individuals so that we could compare and discuss the advantages and disadvantages of each approach.

The full version of the workshop allowed everybody to try all the exercises, but the cut-down version we were getting at miniSPA, only had time for each person to try out a couple of the activities. This was a great pity, as the physical exercise involved putting together a Lego model, and only two groups (not including me!) got to have a go.

I found the exercises themselves very well designed — useful source material for helping teams to understand the benefits (and sometimes drawbacks) of pairing. The planning activity in particular worked well with a pair, surprising some people who had only thought of pairing in development. At Kizoom, we try to do all our estimating and project planning with at least two people — errors caught here save not only the planning time but also the development time.

The social situation exercise was a role play of a personnel issue, with a project hampered by a troublesome guru. The group I was in found that pairing was good for the managerial side of the role play — one had time to think and a chance to moderate their feelings while the other was talking — but could be more threatening for the interviewee. On the other hand, having a one-on-one conversation meant that the conversation was more personal rather than about the issue at hand. There were some people in the session who said their companies had a policy to always have a third party in the room for personnel issues.

I really hope that the session organisers publish their exercises and the results of the questionnaires they asked us before and after each exercise (possibly here). Personally, I didn’t find my impression of pairing changed that much due to the session, but then I really like pairing already and am fortunate to work in a company that not only accepts it but recommends it as a practice.

Friday, 4 April 2008

OverTheAir: Case Study: PrimeSky -- Bringing Web 2.0 to Mobile (Tom Hume & Bryan Rieger -- FuturePlatforms)

A webservice to let people find out what’s in the sky that night… oh, and it has to work on mobile too! How do you fit Space onto a mobile phone? And we want to open source it at the end of the project.

How do you orientate people? How do you display constellations on a small screen?

design process:

  • put stuff on paper first — it’s easy to change
  • iterate with real people
  • get it on a handset as soon as possible
    • initially simple PNG files (look like a simple web page) to check expectations on single pages
    • then some simple HTML to check out navigation, with SVG images showing constellations and context

development process:

  • went through at least 3 iterations of the database schema
    • avoid database-driven design
  • needed to present images in a house style, easy for creation and working at different scales
  • technologies: Symfony PHP, WURLF+WALL4PHP, ImageMagick all on a LAMP stack
  • subjective scaling: manipulating SVG files to keep captions and stars large but overall image small
  • rendering SVG to appropriate format for mobile using ImageMagick
    • then cache pre-created images for a while
  • added in microformats:
    • events for days — every page on the site has a little API in it
    • transformed to vCal on mobile devices — allows you to bring something direct into your phone calendar
  • also provide JSON, YAML, XML, serialized PHP feeds by just adding ?api=xxx on the end of the RESTful URLs (search API is also exposed)

Development took about 7 weeks for one developer.

conclusions and questions

  • look for design solutions first (over and above technical solutions)
    • e.g. orientation
  • you don’t get a choice of which version you want — it’s always the one for your device
    • e.g. iPhone gets a widescreen mobile version, not a zoomable full web page
    • Tom: “the iPhone has a kind of split personality — it’s billed as full web on a phone, but the big sites all have iPhone-specific versions”

There’s also an SMS and email alerting service for interesting events.

Launch date: soon...

See the whole presentation:

Tuesday, 5 February 2008

MomoLondon: Mobile Operating Systems

The Future of Mobile Operating Systems — David Wood, Symbian

“There is long term significant value in mobile operating systems”

  • In 2005 Symbian sold 1 phone every second
  • In 2007 probably sold 3 phones every second
  • Symbian has had about 70% of market historically

Reasons for increased sales:

  1. Cost going down
  2. Reliability going up (appealing to majority rather than early adopters)
    • Largest contribution to bonus is quality (count of bugs + turnaround time for fixes)
  3. Increasing stylishness
  4. Word-of-mouth
  5. Valued services available
  6. Ecosystem

Open Source is strong and powerful, but fragmentation is easy and integration is hard:

  • Mobile Linux has been been fragmenting faster than it unifies
    • 8 major, 22 minor variants

David was trying to say that mobile software is very hard, and therefore the many eyeballs of Open Source will be worse at creating a platform. I’m not sure I agree — lots of software is hard, but has been successfully created in an open source project.

He did identify that there was a problem with fragmentation from “not made here” mentality and rushing to market in mobile manufacturers. Symbian has an eviable position in that they don’t have to answer directly to product managers wanting a device on the market right now, but yet have very close relationships with many manufacturers.

He was pushing the Agile and Lean focus of Symbian. Interesting… what do they do and for how long?

Smartphones: State of the Market — Mark Burk, m:metrics

Lots of thought-provoking graphs, as usual

  • Mobile broadcast TV viewers are a very small, male group with median age of their early 30s.
  • Slightly more people who use their browsers that who made their own ringtone (48m in Europe)
  • Growth of smartphone use slow over this last year — Italy 20% compared with UK 9.9% (Nokia very strong in Italy)
  • Smartphones mostly owned by men (60-70% across all countries)
  • In UK, Windows Mobile users are older than Nokia Symbian users
  • 67% of UK smartphone owners get their handset for free (51.5% of all phones in UK)
    • Compared to only 9 (12%) in Italy
  • Satisfaction scores:
    1. Feature phone 19.4%
    2. UIQ 17.9%
    3. Nokia Symbian 12.6% (though N95 is higher than this)
    4. Windows Mobile 6.9%
  • Smartphones have over double usage of web (x4 in UK)
  • iPhone users do more than other users
  • Apple don’t have as strong brand for MP3 players in France, Germany & Italy compared to UK & US
  • High satisfaction phones:
    • iPhone
    • LG Rumor
    • T-Mobile Wing
  • Unlimited data access makes a huge difference to accessing web, search & email
    • No surprise there…
  • In the US, many smartphone users are offered unlimited data plan at point of sale
    • We appear to be missing this trick in Europe

Web Runtimes: evolving beyond the browser — David Pollington, Group R&D Vodafone

Vodafone R&D prototyping MobileScript — an extended JavaScript engine providing access to phone specifics

Trying to talk to as many players as possible to come up with something converged rather than fragmented

More targets appearing rather than less (Android, iPhone, LiMo, etc)

http://www.vodafonebetavine.net/vodafone/web/MobileScripting
https://forge.vodafonebetavine.net/projects/mobilescript

Code Less, Create More, Deploy Everywhere — Karsten Homann, Trolltech

Mobile Linux not just phones. Comms are becoming required across lots of markets:

  • Coffee machines :-)
  • Media players
  • NASCAR personal TV to follow race at track

Qt and Qtopia are market-leading Open Source platforms

kHTML browser (as in Safari & Nokia WebKit) is integrated into Qt latest release

Nokia want to make Qt available on Series 40 as well as Series 60

Qt APIs are C++, but can develop in Java using Jambi

Touch-based interface for a VoIP product (finally!)

Panel Discussion

What is a smartphone?

  • m:metrics — multitasking
  • Symbian — we’re interested in whole phone market

Who’s to blame for the poor showing for Nokia user interface in m:metric’s reports?

  • m:metrics — user interface is not being prioritised
  • Vodafone — “Nokia do what they like” (that’s not really true, though is it…)
    • We’ve crammed in too many things
    • It’s up to Nokia to throw away all the old baggage
  • m:metrics — if manufacturers have to tick off a 3000 point list from operators before work on UI…
  • Symbian — Nokia will be catching up fast
    • Touch will make a big improvement (Nokia historically haven’t liked touch)
    • Search within phone will appear soon
    • Symbian has a new API for UIs called screenplay (not in phones yet)

What about low-end phones? Do you see Series 60 moving to them? Will the web runtime be on cheaper phones?

  • Vodafone — if we have web runtime then it will be across all devices
    • Don’t need a lot of memory, storage or power for web-centric apps
    • though in my experience, browser apps seem to have high CPU requirements on the desktop…
  • m:metrics — hardware costs have decreased significantly
    • memory costs decreasing by 60% a year
    • low-end phones aren’t where the margins are
  • Symbian — more and more Nokia phones that would have had Series40 now have Series60
    • e.g. 6110, E50
    • Fujitsu & Mitsubishi both only make phones based on Symbian OS (even lower-end phones)
    • e.g. RakuRaku phones for senior citizens
  • Trolltech — looking for Vodafone to generate a need…
    • but Apple has shown that it’s up to the software & hardware to generate the need, not the operators
  • Vodafone — key thing for web runtime is certification
    • can’t be too restrictive
    • web apps shouldn’t prompt the user about connecting to the web…

Simon Rockman: manufacturers will carry on using ARM7 with no cache, won’t run these kind of OSs

  • Phones will keep on getting cheaper and cheaper
  • 80% of all phones are low-end, not high-end
  • Symbian: don’t accept that there will always be a group that don’t need these kind of services
    • more of the lower end phones will have this kind of functionality

Tuesday, 20 November 2007

XPDay 2007: Specification by (executable) Example: Prosperity of the FITtest - Immo Huneke & Robert Brown

  • Using Excel spreadsheets to import data into FitNesse test fixtures
  • Wiki has “convert Excel table into wiki table” button on input, and conversely “output as Excel”
  • Now using Excel spreadsheets directly

Using FIT made tests visible and helped communication in project

FitNesse got too slow after 350ish tests!

XPDay 2007: The Secret Backlog: Behind Every Bug-Report is a User Story - Antony Marcano

  • Why not just capture acceptance tests directly from bug reports?
  • Take bugs and unexpected behaviours as prompts to talk to the customer.
  • Worked on a project for 9 months without a bug tracking system — just used acceptance tests.
  • Bugs focussed on ugly thing that system does; acceptance tests much more positive — aimed at user goals.
  • New features are easier to prioritise and nicer to work on than fixing bugs.
  • Quite often end up with new features in bug tracking system anyway…

XPDay 2007: Fiat Lux: Testing With The Light On - Joan McGalliard, George Joseph & Pushpa Sebastian

Testing team in growing agile project

Teams split according to system functionality rather than business needs

  • No one knew if a story was finished or not

30 devs, 10 testers, 7 BAs, integration team

Embedded testers in development team

At beginning of iteration wrote down stories for iteration

  • each story had page of details: acceptance criteria

Active documentation:

  • tests written in business English
  • runnable
  • italics for input, bold for output — when run, outputs are coloured red or green
  • also had table tests

Documentation is always right since if they fail, the build fails

Tests linked from stories and checked in to source control

The story process:

  1. agreeing acceptance criteria
  2. dev complete
  3. BA/show-and-tell sign off
  4. tester sign off

Can colour code iteration plan to see how far each story has got

Technology involved

Originally used FIT — introduced idea of active documentation

But inflexible, developers didn’t like fixtures

Ended up using Concordion

Tests are written using JUnit but described in an instrumented HTML page

When they fail, they give a stack trace as well as the failures on the resulting page

How to introduce

How to catch up on legacy code?

  • Forget about it — just test for current stories
  • Ended up covering criteria for previous stories too

Having tests ready in time?

  • Works best for 2 testers for every 3 developer pairs and 1 customer/BA

Takes quite a while to write the testing framework & tests

  • 50% of developer time…?

Faulty fixtures

  • Change test data and ensure test fails appropriately
  • Reuse fixtures
  • Pair testers & developers to write the tests

My thoughts: the fixtures are not visible to the customer, and the words in the active documentation do not actually have any connection to the testing code

XPDay 2007: Working With Customers towards Shared Understanding - Andy Pols & Mike Hill

This was a workshop session in which we brainstormed enablers & disablers, chose the best techniques and then talked about how we would use them and what would be the pros & cons.

Techniques that we chose:

  • user stories
  • show + tell
  • rich domain model
  • acceptance testing
  • developers using the system

XPDay 2007: Agile Alliance ATDD Tools Workshop Report - Antony Marcano

Side issue

Research in Calgary on touch-sensitive table used for agile planning (Frank Maurer)

  • enables card throwing :-)
  • create cards using tablet pc with pen-based input, then appears on shared surface to be moved around

Intro

Antony's Blog — things about testing, aggregates other blogs too

Report

Workshop in Portland: discuss cutting-edge advancements in, and envision possibilities for, automated acceptance test driven development tools

  • Tools that help communicate & share with customers to figure out what they want
  • original name was “functional test tools workshop”

Looking at design process using tests

Had a debate: what’s the difference between an example and a test?

  • some took examples and wrapped them, others thought they were different things

Levels of abstraction

  • UCD: Goals, Activities, Tasks
  • Fit tests work better at activity rather than task level
  • Kind of translates to named methods (navigateToJourneyPlanner) vs individual “fill in field with id blah”’

Vocabulary

  • Given, when, then
  • behaviour driven development — RSpec (ruby) in process of integrating given, when, then
  • taking hamcrest & literate tests and making a view that allows customers to interact with the tool
    • e.g. like a word processor
  • looked at JDave — didn’t feel as comfortable and natural as JUnit/Hamcrest
  • great for flow tests but not so good for:
    • do this and result in this data (row fixture in Fit)
    • truth tables — have some ideas but too immature right now
  • Nat Pryce refactored tests to be literate, next step to output Word docs from tests
  • Antony would like to enable customer to write tests (but still need conversation)
  • Nat saying that customers need to write tests in conversation with developers, so in code is good
  • thoughts: given, when, then: moving towards Z & specifications — anybody looked at synergy here?

Visualisation of flow

  • Brian Marick blog
    • currently implemented in Ruby, uses Omnigraffle so Mac-only :-)
    • draw a picture and annotate it
    • fear that if pics too detailed, then lots of refactoring needed
  • Ward Cunningham - Eclipse portal (not open source but tightly coupled to Eclipse project)
    • workflow involved in someone being nominated to be a committer on Eclipse
    • after the fact reporting on tests
      • can hover over steps and view form & data particular step
      • also have links to take you to that point in the application with data already set up
    • also used for help documentation — legal dept could see steps involved
    • actual tests captured in text-based format
  • CubicTest — Eclipse plugin to visually design tests with states
    • generates an interactive HTML prototype, based on the tests you have written
  • these tests were captured at task level, but reported at activity level

Model based testing

  • Ben Simo — state oriented model
  • Manually create state & transition model in Excel, and then generate tests from this model
  • agitator — exercises all the paths through the code (uses code as model)
    • more recent tool allows you to generate JUnit tests from suggestions, can then tidy up and rewrite
  • idea — generate a model from the first tests
    • can then generate new tests to explore the software against that model
    • helps find gaps in thinking (wouldn’t be used for auto-generating, more to suggest new tests)

Patterns of self testing software

  • talk of setting up a wiki to start capturing these ideas

Conclusions

  • tools will encourage appropriate level of abstraction
    • avoid refactoring overhead of writing at task level
  • will allow multiple views on tests
  • tightly integrate into documentation generated from application
  • will become more popular to make tests more transparent — available to customers
    • allows customers to provide specific examples
  • Frank Maurer has an open source project called FitClipse
  • Rick Muggridge: zibrieve.com — refactoring Fit tests
  • Green Pepper: using Confluence to write tests (also ties in with Jira)
    • one issue was tying test versions with app versions (may be sorted with Confluence subversion plugin?)

Q&A + Comments

Concordion, decorate an HTML page with tags underneath, and then JUnit runs it

  • concordion.org — open-sourced last month

Profit — supposedly allows transformation between Fit & Java for refactoring

Online discussion: aa-ftt@yahoogroups.com

Jim Shaw/Shore has idea of customer unit tests (not end to end)

  • forcing the customer to think in modular ways

Good thing for a coach to do — encourage always asking questions

  • put on the tester hat and be persistent about asking questions
  • tester is a role that is very useful in any team

Functional tests taking a long time

  • run as separate continuous integration
  • overnight tests did full thing
  • during the day, had a different config that simplified stack and took less time

XPDay 2007: Keynote: Cheek-to-Cheek: why Co-Located Collaboration Persists - Yvonne Rogers

Video conferencing vs collocated

  • can’t talk privately to others
  • what happens after the meeting is almost or more important that during

HP Labs — mututally immersive mobile videopresence…

  • Live video of the front and sides of the user’s head
  • Mounted on a mobile robotic trolley

Issues

  • Situation awareness — aware of what’s going on around you
  • Non-verbal communication v. important to control the flow
  • Research shows that it’s easier to switch between physical & digital artifacts when face to face

Research over the last few years looking to facilitate face to face communication

eSpace — interactions between (travel) agents & customers

  • customer appears to be understanding and nodding, but really isn’t getting anything
  • a lot of translation going on from information for agent and information for customer _(hey, that’s kinda what Kizoom does :-)-
  • changed the workspace to be a side-by-side interaction with three screens
    • reduced social awkwardness
    • both looked at the screen and occasionally had eye contact
    • both took part in creating the itineraries

Theoretical approaches for supporting collocated teams

Multiple entry points

  • when each person has their own paper and pen, it becomes easy for people to share
  • when there’s only one pad, people fight over the sole entry point
  • also at whiteboards — single entry point is the marker
  • used mitsubishi diamondtouch + diamondspin s/w: touch-sensitive display table to provide shared workspace with multiple entry points
    • saw lots of turn taking and “turn inviting”
    • also people who were normally shy could take part more with the physical tasks

Distributed cognition

  • traditional approaches to cognition talk about what goes on within a single person’s head
  • distributed approach takes the system at large — lots of people with input to the group and output from them
  • distrib. cog. tries to chart:
    • where the overlaps in knowledge are
    • levels of access to information
  • this is the approach used by Helen Sharp (Yvonne is now working with her at OU)
  • Yvonne shows picture of Kizoom’s bug wall and talks about how central it was to our environment
    • (in fact this was probably a breakdown since it just filled up and didn’t get addressed…)
  • large interactive surfaces:
    • OU waiting for MS Surface (due in November, but now arriving next summer)
    • reactable — physical interaction with music software

Dynamo — collocated people sharing & showing digital content

  • shared screen with multiple mice & other devices
  • can carve out sections of the screen and protect them against others
    • can then grant and revoke access to other individual users
  • can seal parcels and leave for other users
  • deployed into a 6th form classroom
    • interaction tended to be a few people using it and others watching as an audience
  • not yet deployed into a software company, but if you want it, let Yvonne know

Conclusion & Q&A

Collocated teams will always work better than distributed teams

  • but no quantifiable effects here

What’s the value of these technologies over index cards?

  • Helen’s research shows that cards have great value that won’t go away
  • if developing a product that requires you to interact with digital content, then this tech gives an advantage
    • especially if making connections
  • people overlook emails and other digital content — posting it on a public space makes people take notice (honeypot effect — they all gather round)

What happens with larger groups?

  • Yvonne’s research is mostly with groups of 2-3
  • When groups get to 6-7 then group segments and division of labour sets in
    • “I’m working on this bit and you can work on that”

Monday, 19 November 2007

XPDay 2007: Mr Agile Goes to Washington: The Impact of Politics on Agile Projects - Panel Discussion

Panel

Sallyann Freudenberg — internal agile coach (permanently employed)

  • previously did PhD in collaborative software development
  • approach: gently let things bubble up and then deal with them

James Davison — head of PM at Razorfish (previously at ThoughtWorks)

  • has come across a lot of politics
  • don’t think you can stay out of it — perception is very important
  • try get everyone into the same space by socialising

Stuart Blair — investment bank

Mike Feathers — object mentor in US

  • travelling coach

Rachel Davies — independent coach

  • often working with several companies at one time
  • facilitating retrospectives: ensure voices are heard in a neutral way before jumping to solutions

Discussion

The focus of the group seemed to be of within large corporations rather than smaller companies working with other companies.

Politics:

  • covert action to get what you want from scarce resources
  • decision making process not clear — individual roles not well defined

Good politics:

  • Aligning projects with high-ups objectives
  • Finding right person to present the case on your behalf
    • Externally, this would be called sales; but internally called politics…
  • Try reframing their goals in a more positive way
    • At least lets you work with them
    • When you catch yourself saying bad things about another, it’s time to stop and step back
  • Having a strong manager who can recognise political games and call people on it
  • We often assume intentions
  • Selling the success of the project within the organisation
    • We find it hard to celebrate success

Bringing politics into our practices:

  • We don’t really have a lexicon for political behaviour…
    • Need a rudimentary politics for software developers
  • Getting to Yes — by Roger Fisher (from Harvard Law School)
    • also others in series (Getting Past No, etc)
  • Can we have a patterns book for politics…?
  • De-politicising a situation:
    • Listening
    • System thinking — showing how things all fit together

In any group have a tension between wanting to belong to a group and wanting to be an individual

Dealing with customers who play games?

  • Build a relationship with them
    • Delivering to 11 countries
    • Turned up in Austria — greeted on front door of building: you’re here to implement a system that means the office will be run from London; go away
    • Had to do a sales job; had to get sponsor on phone to convince him
  • Very difficult to build a relationship with someone when hiding something
  • Can bank integrity in relationship
  • Ask questions of everybody in the company
    • Find different points of view
    • Understand perspective of lots of different people

How do we get recognition within hero-based culture?

  • Always have to sell success (even if not being massively successful)
    • what we are delivering is useful, provides value, ready on time
  • some clients have culture of celebration when a project is completed
  • agile projects release often and regularly
    • need to celebrate that
    • tie in to business successes
  • hold an end of year retrospective
    • show off all that has been achieved
    • lots of issues overcome, just not by panicking
  • hero culture can cause problems — expose the problems and compare with smooth delivery
  • make time to be seen to be doing a good job — and build that in to project planning
    • regular show and tell

What to do when gantt chart and burn down chart start to disagree?

  • agile bubble in a non-agile company
  • often pressure for report comes from middle management: just query with higher management
  • use extra features and benefits of agile methods to sell
  • if the agile project is the first to report that it’s running late…?
    • be honest — hard conversation early on (risk of getting fired)
    • speak their language (e.g. use gantt chart)
    • that’s the project manager’s job
    • it’s going to be late or you can have this instead
    • saying “no” in a way that can be accepted

XPDay 2007: The Social Nature of Agile Teams - Elizabeth Whitworth

Why are agile developers so excited?

  • What aspects of agile dev are related to team cohesion?
  • What makes a team really gel on a project?

Speed & ease of interaction:

  • whole team involvement
  • trust, openness, respect
  • culture of action & change
    • immediate action that they could take in the near future
    • individuals could see themselves make a change
  • agile participants had a more collective viewpoint

Social identity theory

  • in-group out-group bias: just naming different groups biases the dynamic
  • agile culture increases the strength of the project group identity rather than dev, biz, etc

Planning

Planning game makes the conflicts more visible and allows developers to take more ownership over development process

Planning responds to team needs — tasks are neither to hard (anxiety) or too easy (boredom) — increases feeling of flow

Short term planning increased willingness to compromise — team interactions more relaxed

  • increased feelings of security & comfort

Long term planning hard to do as a team

  • gives rise to feelings of insecure, apprehension, stress
  • having to make decisions for things 6 months in advance

Regular Iterations

No definite end goal caused loss of “buzz” — group motivation & focus hard to maintain

Consistent delivery over multiple iterations gave rise to feelings of confidence & security

Whole team awareness

Constant feedback to individuals that all team members share awareness of team activity & share commitment to goals

Supported by daily group standup:

  • Forum for non-task based issues
  • Extra motivation (disapproval from team) and validation of requests
  • Recognition of what’s possible and what’s not
  • Communication is not need-based — allows other topics

Group standup supported by chunked activities

  • Something to report if small enough chunks
  • Loss of motivation if stuck on same task for whole week

Information Radiators: noticeable measures of progress

  • completed stories “give endorphin rush”
  • also supports awareness of individual contributions to team goal (others as well as self)

Performance

Increased sense of control & self-efficacy improves performance

Conclusion & Questions

http://www.ewhitworth.com/html/ma.html

Have a list of weaknesses at end of project, for example:

  • agile focussed on developers — makes them feel good, but QA & documentation felt isolated
  • high-level of interaction sometimes resulted in burn-out

Data collected from:

  • 5 participants from one company
  • 17 participants each from different companies

Agile is a method that helps people work as a team in the software development environment

Frank Maurer (Uni. Calgary): agile planner — distributed planning for agile teams

XPDay 2007: Embrace Uncertainty - Jeff Patton

I came in 10 minutes late for this keynote. Train problems…

Results of stories don’t need to completely satisfy the customer — the aim is to get value and reduce risk. Iteration retrospectives should evaluate on these two goals:

  • Did we get some value? Could we get more value? Biz should answer this.
  • Did we reduce risk?

It’s ok to do the simplest possible thing that could possibly work, rather than the simplest thing that could be released.

Three different customer prioritising strategies:

  1. Follow the money — go for a single business benefit at a time
    • cuts out whole swathes of stories and simplifies iterations
  2. Don’t choose your solution too early — look at what the user wants to accomplish and defer choices as late as possible
  3. Build up feature quality iteration by iteration — need everything but can build up quality and complexity
    • e.g. building a bus — can’t
    • e.g. leave out AJAXy stuff until later, improve performance gradually
    • if build to ideal quality in each iteration then may miss out vitally important function
    • customers say “great, it’s done, let’s move on”
      • so have a report card across the features: D to A
      • can say to customers, “you have your X but it’s D quality now. You’d really want better”

As soon as you start to be dogmatic about following the process, you’re dead!

Q&A

What’s your idea of the role of business analyst in agile?

  • in commercial software company like Yahoo, there’s no such thing — instead they have designers
  • would like to see BAs take more design responsibility for what they’re doing
  • in enterprise software houses, have business people talking to BAs, talking to developers

How do you deal with multiple business voices?

  • use user-centred design & scrum product owner
  • product owner takes responsibility for direction of product
  • understands the different factions and can answer to them why the development is going in that direction

In Yahoo, have designers but also product managers — how do they fit in and can we learn from them?

  • they choose direction of business value from choices given by designers

If stay uncertain, how much is it going to cost?

  • strategies outlined before came out of fixed price projects
  • play space is users to support, kinds of things to do, quality of resulting product, etc

See Jeff Patton's blog version for more details