background preloader


Facebook Twitter

Stack Overflow Developer Survey 2016 Results. Freelance / Contractor Other (Please Specify) Prefer not to Disclose 49,577 total respondents The vast majority of developers have jobs. 91% of developers in the workforce are “gainfully employed” (employed full-time, self-employed, or freelance).

Stack Overflow Developer Survey 2016 Results

I am actively looking for a new job I am not interested in new job opportunities.


Shortlisting Services. User Needs Examples. Roles. Workshop: Estimation Techniques. This week I ran an estimation techniques workshop to help my teams understand different ways of estimating.

Workshop: Estimation Techniques

I’ve run it once before at my previous company and people found it useful. This time Sam and I prepared together, and she ran the same workshop with her teams. We agreed to blog about the results to see how it compared. Goal So why run the workshop? Sometimes they get very caught up in the actual number. I like to remind people that what we care about is getting a shared understanding and consensus, not necessarily worrying too much about the actual number. So what I wanted the teams to see is that you can get estimates about 80% right with 20% of the effort, and it’s not worth the other 80% of the time. The workshop The format of the workshop was 4 exercises, each time boxed to 10 minutes.

Absolute Estimates For exercise 1 we did absolute estimating, and the items to estimate were dogs. Here are the results: Planning Poker Estimates Affinity Estimation Relative Estimation. Agile and government services: an introduction - Digital Service Manual. You must use the agile approach to project management to build and run government digital services.

Agile and government services: an introduction - Digital Service Manual

Agile methods encourage teams to build quickly, test what they’ve built and iterate their work based on regular feedback. Meeting the Digital Service Standard. GOV.UK – GDS design principles. What each role does in a service team - Digital Service Manual. Browse guides by topic — Government Service Design Manual. Government Service Design Manual. Learn about the different phases of service design and get guidance for the phase you're in now.

Government Service Design Manual

Discovery A short phase, in which you start researching the needs of your service’s users, find out what you should be measuring, and explore technological or policy-related constraints. Learn about the discovery phase Alpha A short phase in which you prototype solutions for your users needs. You’ll be testing with a small group of users or stakeholders, and getting early feedback about the design of the service. Learn about the alpha phase Beta You’re developing against the demands of a live environment, understanding how to build and scale while meeting user needs. Service design phases — Government Service Design Manual. Accessible Media Player by Nomensa The timeline slider below uses WAI ARIA.

Service design phases — Government Service Design Manual

Please use the documentation for your screen reader to find out more. Building a digital service is a complex task, with many risks. Digital Transformation — GOV.UK. Government Service Design Manual. The Digital Service Standard has changed from 26 points to a more concise 18.

Government Service Design Manual

From 1 June 2015 all transactional services will be assessed on the new 18 points. The Service Standard ensures digital teams build high quality government services. A transactional service must meet each criteria to pass the Government Digital Service assessment. If a service doesn’t pass it won’t appear on GOV.UK. Government Service Design Manual. An introduction to Wardley 'Value Chain' Mapping. This is about my journey, from a newly-minted yet confused CEO caught like a rabbit staring helpless into the oncoming headlights of change - to being voted one of the most influential people in IT within the UK.

An introduction to Wardley 'Value Chain' Mapping

It took me a decade to first develop the techniques that I'm going to describe and a further 10 years to gain confidence with them through practice. Every journey begins with a step, and in our case there were several. I'll use an example throughout, and in this first foray I'm going to map a TV company that is part of a larger media conglomerate. I'll be using an early draft, which took about two hours to develop, including the strategic play from a base understanding of nothing about the TV industry.

The reason I've selected this example is because while it explains the process of mapping, anything of commercial value has long since left it and been exploited or discarded. __ osnu cuosFe r. 1n epeedtsS__ PragDave: Agile is Dead (Long Live Agility) Thirteen years ago, I was among seventeen middle-aged white guys who gathered at Snowbird, Utah.

PragDave: Agile is Dead (Long Live Agility)

We were there because we shared common beliefs about developing software, and we wondered if there was a way to describe what we believed. It took less than a day to come up with a short list of values. We published those values, along with a list of practices, as the Manifesto for Agile Software Development:


Design Thinking + Agile. You Don’t Have To Be Extreme To Try Extreme Programming. (above) Nothing to do with Extreme Programming Extreme Programming – the name itself conjures up all sorts of images like the one above.

You Don’t Have To Be Extreme To Try Extreme Programming

It gives the impression that it’s some sort of high-octane, living-on-the-edge way to develop software. Stefan Wolpers presentations. Scrum: A Breathtakingly Brief and Agile Introduction. User Research Basics. User research focuses on understanding user behaviors, needs, and motivations through observation techniques, task analysis, and other feedback methodologies.

User Research Basics

Mike Kuniaysky further notes that it is “the process of understanding the impact of design on an audience.” The types of user research you can or should perform will depend on the type of site, system or app you are developing, your timeline, and your environment. UX Without Users Is Not UX. A Five-Step Process For Conducting User Research. Imagine that this is what you know about me: I am a college-educated male between the ages of 35 and 45. I own a MacBook Pro and an iPhone 5, on which I browse the Internet via the Google Chrome browser. I tweet and blog publicly, where you can discover that I like chocolate and corgis. I’m married.