Changes between Version 39 and Version 40 of TransitionMaintenance


Ignore:
Timestamp:
12/16/13 17:35:11 (3 years ago)
Author:
ed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TransitionMaintenance

    v39 v40  
    66 
    77* We have a target of 22 hours per month for ongoing site maintenance (equivalent to £770 per month) 
    8 * We have an absolute maximum of 28 hours per month (equivalent to £1,000 per month) 
    9 * We seem to be cruising at 24 hours per month (roughly £850) at 16/12) 
     8* We seem to be cruising at 24 hours per month (roughly £850) at 16/12 
     9* We have an absolute maximum of 28 hours per month (equivalent to £1,000 per month) in Q1 2013 (Jan-March) 
    1010 
    11 The assumed average hourly rate on which this is based is £35 p/h to take into account different tech's hourly rates. However, if a more expensive tech uses up more time, this can bend the money, while staying the time allowance - Beware.  
    12  
    13 Most of this work will be around website hosting and maintenance, but there will be times when developers (more expensive) do stuff too.  
    14  
    15 All work done for this needs to be on tickets categorised with the milestone maintenance; it is possible to have different categories (task, enhancement etc.) 
    16  
    17 There have been various changes over this year which you can read about in the budget confusion section at the bottom of this page, which Ed has kept for posterity and if we need to refer to it later when we are reckoning budgets at the end of March 2014. Please don't delete these.  
     11* The assumed average hourly rate on which this is based is £35 p/h to take into account different tech's hourly rates. However, if a more expensive tech uses up more time, this can bend the money, while staying the time allowance - Beware.  
     12* Most of this work will be around website hosting and maintenance, but there will be times when developers (more expensive) do stuff too; this happened a lot in Q3 2013 as we had hard and software problems 
     13* All work done for this needs to be on tickets categorised with the milestone maintenance; it is possible to have different categories (task, enhancement etc.) 
     14* There have been various changes over this year which you can read about in the budget confusion section at the bottom of this page, which Ed has kept for posterity and if we need to refer to it later when we are reckoning budgets at the end of March 2014. Please don't delete these.  
    1815 
    1916== Monthly process in detail == 
     
    7067* We should, one day, copy the macro here to generate a list on this wiki page, http://www.gossamer-threads.com/lists/trac/users/48563 
    7168 
     69 
    7270== Notes about budget confusion here for posterity == 
    7371 
    74 Ed realised his budgetary maths was askew on 3/12 and that the monthly amount approved from the board meet was £6,000 + £3,250 = £9,250 = £770 per month. Somehow he had asked them for not enough money based on his assessment of 2013 Q2, and then incorrectly divvied up the money he got, assuming he got £1,027 per month instead of £770 - when actually he needed approx £840. So there is some confusion, and lots of the monthly analysis is now irrelevant, which he has since deleted for simplicity's sake. During this panic, Sally pointed out that the web and IT budget, within which this maintenance stream lives, is doing well to date and is, as a whole, under-budget, so this stream's confusion could be absorbed as Ed has spent less in other places. THEN: Since this panic, we have uncovered some excess in the Inner Transition budget which can bring £230 per month to the maintenance budget, so we can have a ceiling of £1,000 per month. Ed is targetting 22-24 hours done per month for Sam in 2014.  
     72Ed realised his budgetary maths was askew on 3/12 and that the monthly amount approved from the board meet was £6,000 + £3,250 = £9,250 = £770 per month. Somehow he had asked them for not enough money based on his assessment of 2013 Q2 (should have been approx £840 per month), and then incorrectly divvied up the money he got, assuming he got £1,027 per month instead of £770. So there is some confusion, and lots of the monthly analysis is now irrelevant, which he has since deleted for simplicity's sake (although you can see it at bottom of this page). During this panic, Sally pointed out that the web and IT budget, within which this maintenance stream lives, is doing well to date and is, as a whole, under-budget, so this stream's confusion could be absorbed as Ed has spent less in other places. THEN: Since this panic, we have uncovered some excess in the Inner Transition budget which can bring £230 per month to the maintenance budget, so we can have a ceiling of £1,000 per month. Ed is targetting 22-24 hours done per month for Sam in 2014. Ed and Sarah discussed this on 11/12/13; in 2014/15 budget, we will have one stream for ongoing website work to cover both 'maintenance' and 'enhancements' with a model to aim for a quarterly/monthly total, and then any leftovers will be rolled up into 'site enhancements'.  
    7573 
    7674=== Changes made in July following board meeting and new budget and daily rate ===