Not Signed-In
Which clippings match 'Organisational Process' keyword pg.1 of 1
12 SEPTEMBER 2014

Automatic Art: human and machine processes that make art

Exhibition: 3 July–10 September 2014, GV Art gallery, London, 49 Chiltern Street, Marylebone, London W1U 6LY.

"This exhibition presents 50 years of British art that is generated from strict procedures. The artists make their work by following rules or by writing computer programs. They range from system–based paintings and drawings to evolving computer generated images."

1
2

3

4

TAGS

2014algorithmic art • Anthony Hill • Automatic Art (exhibition) • boredomresearch • British artchance artcomputer artcomputer art practicecomputer generated artcomputerised artdesign formalismdigital art exhibitiondigital artworkdigital materialism • Dominic Boreham • Ernest Edmonds • exhibitiongenerative artgenerative designgouache • GV Art Gallery • Harold Cohen • Jeffrey Steele • John Carter • Julie Freeman • Kenneth Martin • latticemachine-made • Malcolm Hughes • Michael Kidner • Nathan Cohen • orderly patternsorganisational processPaul Brown • Paul Smith (boredomresearch) • Peter Lowe • procedural artprocess artrule-based work • Sean Clark • simple rulesStephen BellStephen Scrivener • Steve Sproates • Susan Tebby • system-based drawing • system-based painting • systems art • Terry Pope • Trevor Clarke • Vicky Isley (boredomresearch) • visual abstractionvisual art • William Latham

CONTRIBUTOR

Simon Perkins
26 JANUARY 2014

MoSCoW Analysis: a project requirements prioritisation technique

"MoSCoW analysis divides requirements into four categories: Must, Should, Could, and Won't. It is most applicable for software development or timeboxed delivery efforts, as it focuses on determining which requirements can be implemented given specified time or resource constraints. Category descriptions are as follows:

Must: Describes a requirement that must be satisfied in the final solution for the solution to be considered a success.

Should: Represents a high–priority item that should be included in the solution if it is possible. This is often a critical requirement but one which can be satisfied in other ways if strictly necessary.

Could: Describes a requirement which is considered desirable but not necessary. This will be included if time and resources permit.

Won't: Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future."

(Kevin Brennan, 2009, p.165)

Kevin Brennan (2009). "A Guide to the Business Analysis Body of Knowledge". International Institute of Business Analysis. ISBN 978–0–9811292–1–1.

TAGS

building in measuresbusiness analysis • business requirements • clear project objectives • could • design requirements • importance • International Institute of Business Analysis • management methodmanagement methodologymanagement technique • MoSCoW analysis • MoSCoW method • MoSCoW prioritisation • must • organisational process • organisational technique • prioritisationprioritisation analysisprioritisation techniqueproject definitionproject deliverables • project delivery • project goalsproject managementproject management methodproject objectivesproject requirementsquantifiable definitionsrequirements gatheringrequirements prioritisation • should • software development methodtime management • wont

CONTRIBUTOR

Simon Perkins
16 APRIL 2013

Moniker: agency behind Light Light's crowd-sourced music video Kilo

"Moniker is an Amsterdam based design studio founded in 2012 by Luna Maurer, Jonathan Puckey and Roel Wouters. ... The studio works across various media for a diverse range of clients ranging from those in the cultural field to commercial companies. ... we explore the social effects of technology – how we use technology and how it influences our daily lives. Often, we ask the public to take part in the development of our projects. The resulting projects expand and grow like plants, displaying their inner organisational process."

[The studio is responsible for the interactive music video "Kilo" performed by Dutch quartet Light Light (http://www.lightlight.nl/) aka Björn Ottenheim & Daan Schinkel of zZz and Alexandra Duvekot & Thijs Havens of Sælors.]

1

TAGS

2012 • Alexandra Duvekot • Amsterdamautonomous • Bjorn Ottenheim • commissioned work • computer cursor • continuous series • crowd-sourced music video • crowdsourcing • Daan Schinkel • design studioDutchever-changing • expand and grow • experimental workflocking algorithmfollow other usersgenerative design • how we use technology • interactive design • interactive music video • Jonathan Puckey • Kilo (song) • Light Light (band) • ludic intervention • Luna Maurer • Moniker (studio)music videonetwork societyorganisational processparticipative mediaparticipatory Internet media • point and click • pointer • quartet • Roel Wouters • Saelors (duo) • shared experiencesocial effects of technology • take part • Thijs Havens • video work • zZz (duo)

CONTRIBUTOR

Simon Perkins
Sign-In

Sign-In to Folksonomy

Can't access your account?

New to Folksonomy?

Sign-Up or learn more.