Week 9: Iterate and Collaborate.

A project will always proceed though many versions and iterations.

Last week was a very powerful week with a lot of very impressive experiments being installed and some great ideas being discussed.

For week nine we will continue with this process of experimentation and collaborative discussion.

Those who installed work in week 8 understand the value they received from throwing something – anything – up. For those that shied away from doing so we expect that you’ll step up and grab some of this potential value – get something installed no matter how small or drafty.

This week Jo and Mat will be moving through each of the projects to discuss your progress and ideas and we will draw in a number of your peers rather than the whole class. We hope this will provide a more agile way of feeding back and having meaningful discussions about your project.

Remember the strategy of deliberate thinking that we employed last week. As your moving through and discussing the works try and use the 6 modes of thinking in order to contribute as much as possible to each project.

How does it make you feel? How do you feel about particular aspects of the work? What do you like/dislike?
What is working?
What possible paths could it develop along?
What needs work/clarifying/or discarding?
What needs to be done and how can we get it done.?

Professional Profiles : General Feedback.

We will be discussing and feeding back on your professional profile today. We’ve provided some general feedback to your Professional Profile Assignment, not so much in terms of your marks, but importantly, how you can improve on this resource for professional use.

  • Check functionality, particularly usability and navigation.
  • Start with you – who you are, what you do, what do you aspire towards, then support this narrative with your works.
  • Layout: do not use centre-align for text blocks.
  • Always run a spell-check.
  • Always (get someone else to) proof-read
  • Records in a CV should be listed in reverse-chronological order with the most recent listed first.
  • Audit and Simplify your use of language. What does a sentence actually say? If I take this sentence out does it make a difference? Look for empty adjectives and discard them. Use simple (rather than compound) sentences wherever possible – Can a sentence be broken down into two simpler sentences. Try and use a theme>rheme structure to clarify your writing (http://www.uefap.com/writing/parag/par_flow.htm)
  • Keep paragraphs short. ( 5 sentences or less)
  • Always Embed content – do not ‘link out’ and expect me to click.
  • Generally lead with an image of you or your work. (But an image of you is stronger). Perhaps and image of you with your work is the best of both worlds.
  • Move ‘Blog’ links low in your navigation schema. About > Content > Contact > Blog.
  • Always provide a form of contact.

Project Management approach

Goals, Milestones, Obstacles & Mitigations, Tasks.

  • A well defined goal is Specific, Measurable, Achievable, Realistic and Timely (SMART -urgh).
  • Milestones break down your goals according to steps with dates. We work backward from our goal to set Milestones and ensure we understand and apportion time appropriately.
  • Tasks are the direct steps needed to achieve milestones. Break you milestones sdone into small achievable task.
  • Obstacles:  reflect on your tasks (and milestones) individually – what obstacles might stop you from achieving them. Turn them into tasks in order to account for these obstacles.

Remember the rules of agile/lean management (otherwise known as iterative development) apply this ongoing process to ensure your tasks are being met on a day by day, week by week basis. Make sure your Tasks are structured using this mode of development.

There are increasing numbers of versions of this methodology – the software version is to deploy early and often, this development into a management paradigm that looks something like: (discover/design (what), design/deploy (how), measure/test/analyse), but really I think it is what artists/craftspeople and creative types always did: Act – Observe – Act (differently). Regardless of how you deploy it make sure that each task involves an action and returns an observation that will inform the project moving forward.

Versions of Agile and Lean approaches to project development:

Leave a Reply

Your email address will not be published. Required fields are marked *