#process (59 links)
- GOV.UK’s firebreak: why and how we spent a month working differently – Inside GOV.UK insidegovuk.blog.gov.uk
- Drones and Cowboys emeaentrepreneurs.com
Everything that gets done is either done by a system or by a person. Systems are operated by drones. Cowboys get shit done in spite of systems.
Missed this first time around. The demo technique is uncannily similar to how we've ended up working. This is a wonderful articulation.
- “The Design System Isn't Working for Me!” bigmedium.com
How to manage bugs, missing features, intentional design deviations, new patterns, and more.
- Companies Using RFCs or Design Docs and Examples of These blog.pragmaticengineer.com
- Ethical Maturity in User Research nngroup.com
- Design Principles - Adactio principles.adactio.com
A collection of design principles from elsewhere, gathered into one place.
- AI Type Design Workshop – FVS flexiblevisualsystems.info
In other words, if we outsource the creative process, we also outsource thinking. Making is deeply connected with thinking. If you want to learn or develop something new, you have to go through a painful process if you want it to be worth something.
A snappy, but not a particularly representative quote. This is arguing for doing the thing to learn properly, later augmenting with AI.
- Loomio: decide together loomio.com
Bring people together, have discussions, make proposals and achieve clear outcomes
- What is the Red Bead Experiment? maaw.info
The red bead experiment is deceptively simple because it provides a powerful message that is difficult for many to grasp. In summary, the misconception that workers can be meaningfully ranked is based on two faulty assumptions. The first assumption is that each worker can control his or her performance. Deming (1986, 315) estimated that 94 percent of the variation in any system is attributable to the system, not to the people working in the system. The second assumption is that any system variation will be equally distributed across workers. Deming (1986, 353) taught that there is no basis for this assumption in real life experiences.
- The origin of complexity itnext.io
The problem with coordination is that it adds complexity to our systems which make them harder to change and work with.
- Dark Scrum ronjeffries.com
- Simplicity bastianallgeier.com
<blockquote>The longer I look at boilerplates, build tools, frameworks and ways to make my life as a developer easier, the more I long for the basics.</blockquote>
Half agree. Choose wisely.
- Responsive News — How the BBC should practice Responsive Web Design responsivenews.co.uk
- Agile Is Dead (Long Live Agility) - PragDave pragdave.me
What to do:
Find out where you are Take a small step towards your goal Adjust your understanding based on what you learned Repeat How to do it:
When faced with two of more alternatives that deliver roughly the same value, take the path that makes future change easier.
- Scrum: Agile madness | www.jillesvangurp.com jillesvangurp.com
<blockquote>"You can’t substitute experience with process and that is exactly what agile followers end up doing. Take away the experienced people and you have a lot of people executing the rituals of scrum, kanban, or whatever without really understanding what they are doing. The assumption that that will work at all is naive at best and actually rather delusional."</blockquote>
- Full stack web development act2.me
<blockquote>So, this is where we are today – and my reference architecture is mongodb for the database server, node/express as the web/application server, AngularJS on the client side (along with Bootstrap for styling). I find that this architecture allows me to build web services really quickly that can have a client interface build fast using AngularJS, and then one can start development of mobile apps against the service using PhoneGap or native mobile development tools.</blockquote>
- Agile Software Is A Cop-Out; Here’s What’s Next | Forrester Blogs blogs.forrester.com
Yes.
- How to really make something slideshare.net
"...that people actually want". Rapid app/product development ideas from MBM.
To check in you need three conditions met: You need someone to review it and say it looks good. You need to be certified in the language – basically, you’ve proven you know the style of this language – called “readability.” And then you also need the approval from somebody in the owner’s file in that directory.
The way we do this is by having a 1-hour meeting every Tuesday morning where my manager presents a PDF report that outlines these figures and colours the report either Red (we're in trouble and we better do something about it), Yellow (We're in danger, but it's fixable) or Green (we're on track to achieve our goals).
- Walls Come Tumbling Down presentation slides and transcript | For A Beautiful Web forabeautifulweb.com
Excellent overview of agile (small-a) process from Malarkey
- ongoing · Test-Driven Heresy tbray.org
Here’s my thesis: As a profession, we do a lot more software maintenance than we do greenfield development. And it’s at the maintenance end where TDD really pays off. I’m starting to see lapses from the TDD credo as more and more forgivable the closer you are to the beginning of a project. And conversely, entirely abhorrent while in maintenance mode.
- Dear Dustin Curtis | Dustin Curtis dustincurtis.com
If the UX architect at AA.com is actually pretty good, then why does the site suck so much?
- Continuous deployment in 5 easy steps - O'Reilly Radar radar.oreilly.com
More on continuous deployment.
Hurrah, 24 ways is back.
- Wait till I come! » Blog Archive » In praise of mistakes wait-till-i.com
Instead of celebrating the successes, we should be celebrating issues that have been brought to our attention. A bug is a chance to analyze what lead to it to fix it.
- Apple's design process - BusinessWeek businessweek.com
Interesting presentation at SXSW from Michael Lopp, senior engineering manager at Apple, who tried to assess how Apple can ‘get’ design when so many other companies try and fail.
- ReviewBasics -- Home reviewbasics.com
Comment, annotate, and markup images, documents, and videos.
- Slashdot | Best Practices For Process Documentation? ask.slashdot.org
I know that this is all a waste of time if there's no follow-through from management. But assuming that the required support is there, how do you guys do process documentation?
- adaptive path » blog » Dan Saffer » UXweek2007: Leisa Reichelt on Waterfall Bad, Washing Machine Good adaptivepath.com
Notes from Leisa Richelt presentation.
- James Shore: Successful Software jamesshore.com
You can Change Your Organization or Change Your Organization.