wiki:TnV3
Last modified 3 years ago Last modified on 11/26/13 15:54:58

Table of Contents

  1. Phases
    1. IN PARALLEL
  2. Phase 1: TN v3.1: moving the base layer, launching the support section
    1. Process for Phase 1: TNv3.1
      1. JK development estimates for Phase 3.1
    2. Content for TN v3.1
  3. TN's roles may make us need to create different web presences
  4. TN v3.2
      1. JK development estimates for Phase 3.2
  5. TN v3.3
      1. JK development estimates for Phase 3.3
  6. JK development estimates total
  7. EM working including JK estimates
  8. Notes about new taxonomy for new TNv3 section

TN v 3 cost estimates working document

Purpose of this piece of work: Produce an estimated cost range to produce TN v3 site, broken down into phases for board agreement and fundraising from Winter 2013 onwards.

Phases

  1. 3.01: IIRS
  2. 3.1: build D7 platform, migrate base layer, introduce tech, support and comms foundations for enhancements
  3. 3.2: enhancements based around 'thriving' groups (support section content and stack exchange?)
  4. 3.3: enhancements based around health check (integration with TN DNA support logic)
  5. 3.4: enhancements based around relational logic (regional connections)

IN PARALLEL

  • 3.02: IIRS post beta trial, extend to other countries wanting

Phase 1: TN v3.1: moving the base layer, launching the support section

Process for Phase 1: TNv3.1

JK development time estimates added in italics

  1. Autumn 2013: Prune and prepare
    • Remove CMS, PSE, Sharing Engine 0.75 days
    • TN work on strategy .5 days
    • Start search for more Ttechs
      • site admin
      • programmers
      • usability focused designers
  2. Winter 2014: Assess and agree: critical TN foundation work
    • TN work on 'Transition DNA' (i.e. basic communications building blocks)
    • TN work on support framework design (i.e. section architecture)
    • TN work on value proposition (i.e. 'engagement model and motivation - esp. Official/Muller? issues)
    • TN work on migration - what to take, what to archive
    • TN work on ethics, tracking users, sharing data with other groups, using third party services
  3. Spring 2014: Plan and design, start build TN v3.1 1.75 days
    • Key TN v3 taxonomies
    • Usability and design: workflows and site 'directions'
    • Content analysis: match incumbent content and taxonomies to new requirements
    • Taxonomy analysis: match incumbent taxonomy to new requirements
  4. Summer 2014: TN v3.1 deliver -- see breakdown below
    • Build
    • Migrate
    • Populate
    • Market
    • Measure

JK development estimates for Phase 3.1

  • Parts 1-3 (prune/design/plan) = 3 days
  • Part 4 - Build - breakdown:
    • Plan content types, taxonomies, fields and implement as a set of features. 1-2 days
    • Build key views/directories, set up content type layouts (panels?) 2-3 days
    • Extend taxonomy displays, plus views and filters for maps/location 0.5-1 days
    • Build basic user relations/engagement/motivation/crm -- depends on plan, modules and degree of integration 1-2 days
    • Simple, attractive responsive Bootstrap-based theme with nice UI that aids engagement 2-5 days
    • Extend Migrate for data we want (users, profiles, Ini, Proj, News, some events, resources etc) 1-4 days
    • Web services (commenting, sharing, sync, CRM etc) client/server and social plugins/auth (TBC) 0.5-3 days
    • Tweaks, fixes, snagging, launch, other gubbins TBC 2-5 days
    • Inevitable first month of extra tweaks, support, maintenance & fixes 1-5 days
    • BUILD TOTAL: 11-30 days... Clearly a wide range due to unknowns around user engagement, quantity of migration, services/social integration and other unknowns.
  • Total Phase 3.1 = 14-33 days, likely to be below midpoint of this (23.5) as much is unknown at this point and we're going for simplicity and power first and foremost. Gut says 15-20 days.

Content for TN v3.1

  1. Editorial
    • mostly migrated content
    • massively simpler commenting (distributed?) and relations to other services (FB etc.))
      • news
      • blogs
      • stories
      • pages
  2. Support
    • new section from scratch: first two of four parts (all four hopefully using same structure, EM to confirm). New taxonomy based on group process (8-10 elements of group development)
      • 'basic'
      • essentials
      • strengthenging
      • 'developing groups'
    • migration of incumbent content and relation to new section
      • ingredients (???)
      • resources (yes and might need to adapt to new taxonomies)
      • tools (???)
      • other (???)
  3. Directories
    • base layer migration and probably extended layer (might keep extended behind the scenes)
    • massively slimmer registration and content addition process (i.e. slimline TI addition as per IRS)
      • directories People, Projects, Initiatives
      • first version of more integrated locational logic (e.g. on registration 'did you know that xxx Tis within 50 miles)
      • first version of CRM-styled updating process (e.g. quarterly update emails to P.O.C.s)
      • include new status field based on activity? Not clear what happens with official/muller but likely to be removed.

TN's roles may make us need to create different web presences

  1. Transition 'International': 'Universal' support and news
  2. Transition UK: national hub site

These will need to see the same core features but present them differently - we'll need a taxonomy of sorts to identify 'universal' materials (e.g. support materials that anyone in any country can use) and 'local' materials (e.g. UK-specific support materials). So the UK hub will be the first of the national hub sites to use the TN 'universal' stuff with its own locally relevant stuff).

TN v3.2

  1. Support: gradual release of third part of support section and introduce p2p knowledge share trial *'thriving' groups section
    • stack exchange style p2p knowledge share Q&A (good for thriving groups who are more advanced and self-directed)
  2. CRM: gradual introduction ofTN-logic-based support analysis tool 'health check'
    • integrate with TN diagnostic tool and process - Tis complete easy tool to assess

JK development estimates for Phase 3.2

  • Choose and implement advanced user engagement, commenting, voting and gamification (rewards/badges etc). 2-5 days
  • Theme and Drupal structural changes to site to get best from engagement 2-4 days
  • Addition/integration of BASIC CRM modules and/or service (approach TBC) 2-5 days
  • Extension of CRM features to add value and cover specific use-cases (TBC) 2-5 days
  • Creation/integration of TN diagnositics modules/forms/views/reports etc (TBC) 2-5 days
  • Total Phase 3.2 = 8-24 days, likely to be below midpoint of this (16 days) as much is unknown at this point. Gut says 10-15 days.

TN v3.3

  1. Support: gradual release of fourth part of support section
    • 'projects'
  2. CRM: gradual introduction of regional relational patterns
    • integrate with a CRM package

JK development estimates for Phase 3.3

  • Democratisation/internationalisation of above CRM & knowledge featureset (i.e. make available to the world where needed) 2-4 days
  • Build and enhance Projects offering. 1-2 days
  • Enhancement of features and ideas in phase 3.2 - better, more compelling/powerful 3-6 days
  • Further theme and Drupal changes to site to get best from engagement approaches 1-2 days
  • Advanced TN diagnositics modules/forms/views/reports etc (TBC) 1-3 days
  • Web services for syncing/sharing across the network 3-6 days
  • Total Phase 3.3 = 11-23 days, likely to be below midpoint of this (17) as much is unknown at this point. Gut says 12-18 days.

JK development estimates total

  • Phase 3.1 = 14-33 days, gut says 15-20 days
  • Phase 3.2 = 8-24 days, gut says 10-15 days
  • Phase 3.3 range = 11-23 days, gut says 12-18 days
  • TOTAL: range = 33-80 days; gut = 37-53 days; expected around 45 days.

EM working including JK estimates

  • Phase 3.1
    • Development estimate: 25-30 days
    • Theming: 5-10 days
    • Usability: 5 days
    • Project management, production, testing, editorial: 2 days per week (Ed so cost in core)
      • Ed total: range = 40-45 days
      • Ed financial: 40 days, 320 hours, av rate £38 p/h = £12,160 -- 45 days, 360 hours, av rate £13,680)
  • Phase 3.2
    • Development estimate: 20-25 days
    • Theming: 3-5 days
    • Usability: 3-5 days
    • Project management, production, testing, editorial: 2 days per week (Ed so cost in core)
      • Ed total: range = 26-35 days.
      • Ed financial: 26 days, 208 hours, av rate £38 p/h = £7,904 -- 35 days, 280 hours, av rate £38 p/h = £10,604)
  • Phase 3.3
    • Development estimate: 15-20 days
    • Theming: 5-10 days
    • Usability: 5-10 days
    • Project management, production, testing, editorial: 2 days per week (Ed so cost in core)
      • Ed total: range = 25-40 days.
      • Ed financial: 25 days, 200 hours, av rate £38 p/h = £7,600 -- 40 days, 320 hours, av rate £38 p/h = £12,160)
  • Project management overhead for each phase: Add this to all of them
    • Face to face meetings: at least 2 per phase, approximate cost per meet is travel + hours = £500-£1,000, estimate: £2,000 per phase
    • Weekly skypes: (1.5 hr meet x 3 techs @ £38 p/h = £171) x 10 = £1,170 per phase
    • Documentation: getting techs to write stuff up (AKA pulling teeth from chickens): (1 hr p/w for 12 weeks per tech) x 2 techs, = 12x2x38 = £912 per phase
      • Total estimated project management costs for techs: £5,00 per phase
  • Phases estimated totals combining tech and project costs (NB does not include Ed's time)
    • 3.1: Dev + project management: £17,000 - £19,000
    • 3.2: Dev + project management: £13,00 - £16,000
    • 3.3: Dev + project management: £13,00 - £17,00
      • Total range: £43,000 - £53,000

Notes about new taxonomy for new TNv3 section

Mike and Ed working on new structure for TN support section - which we'll need to use for editorial and resource content elsewhere - this is basically a group process way of looking at the world, based on the Transition Launch training. You can see more about the support section further up this page.

  1. Essential elements list is a taxonomy for 'universal' groups
    • What is Transition
    • Why do Transition
    • Group development
    • Group initiation
    • Vision
    • Partners/networks
    • Engagement with community
    • Inner Transition
    • Part of the movement
  2. The support section and taxonomy is built around a high level process with approximate 'stages'
    • Basic
      • Essentials
      • Strengthening
      • Projects
      • Thriving
  3. There are different audiences for different support content, based on TN's different roles
    • Universsal = GLOBALLY relevant content and group process
    • UK = pertinent to UK (national hub site) only

26/11: things Mike and Ed thought about

  • Possibly adding a 'finance' element which starts as basic money stuff and goes to REconomy
  • Differences in projects and thriving - and how you provide information and/or advice/connections at what stage
  • Universal idea and word AGREED totally
  • Thriving likely to be a different dynamic (socio-technical design)
  • Elements exist as a useful taxonomy in Essentials, Strengthening, Projects, and (mostly) Thriving
  • Essential elements things a group goes through, they see the value, and then use them as tools in a process for project and thriving