Progress weekly reports for Big5

BIG5, WEEK 14 (7.12.2010)

  • Coding for the application has been proceed
  • Preparation for the 1+3 campaign has been finished
  • Meeting held with tu10 students

Risks: List here the risks                       

  • Demo still not ready
  • Co-operation with tu10

Contingency plan: Actions to decrease the risk here

  •  focusing on the fan pag

Next steps:

  • Sales pitch next thursday
  • Delivering necessary documents to Run to Shop
  • Combining our and tu10 students' facebook pages

BIG5, WEEK 13 (30.11.2010)

  • Some coding has been done (by outsourcing)
  • Some preparation for the 1+3 campaign has been done
  • Fan page content has been updated
  • Instructions about the 1+3 campaign for tu10 has been delivered

Risks:  

  • Time is running
  • No programming skills
  • No time or skills to complete the coding
  • Co-operation with tu10

Contingency plan:

  • focusing on the fan page
  • let's try to keep the boundaries

Next steps:

  • 5 min sales pitch
  • continue working among the marketing side
  • continue improving the fan page
  • combine our and tu10 students' fan pages? (when the availability tool is working)

BIG5, WEEK 12 (23.11.2010)

  • Existing code and instructions about the fan page content have been delivered to Run to Shop
  • Interviews about putting infos to the waiting list has been held and responses analyzed
  • Fan page content has been updated
  • Instructions about the 1+3 campaign for tu10 has been done, waiting for the approval from 24 Online

Risks:                      

  • Time is running
  • No programming skills
  • Run to Shop has no time to do the coding
  • Co-operation with tu10

Contingency plan:

  • focusing on the fan page
  • let's try to keep the boundaries

Next steps:

  • 5 min sales pitch
  • sparring tu10 about the 1+3 campaign
  • continue improving the exterior of the fan page
  • combine our and tu10 students' fan pages? (when the availability tool is working)

BIG5, WEEK 11 (16.11.2010)

  • Facebook fan page has been programmed as far as possible with our own skills
  • Interviews about putting infos to the waiting list has been held and responses analyzed
  • Listing what is going to be in the fan page, done
  • Project plan done and introduced
  • Sales pitch was held again

Risks: 
       

  • Time is running
  • No programming skills
  • Run to Shop has no time to do the coding
  • Co-operation with tu10
                

Contingency plan: 

  • focusing on the fan page
  • let's try to keep the boundaries

Next steps:

  • 5 min sales pitch
  • sparring tu10 about the 1+3 campaign
  • continue improving the exterior of the fan page

BIG5, WEEK 10 (9.11.2010)

  • Started to create the Facebook fan page
  • Sales pitch was improved
  • Interviews about putting infos to the waiting list has been started
  •  

Risks: 

  • Time is running
  • No programming skills
  • No demo to present still
  • Co-operation with tu10
               

Contingency plan: 

  • focusing on the fan page
  • let's try to keep the boundaries

Next steps:

  • Analyze the responses from the interviews
  • Keep the Sales pitch again
  • Continue the fan pages
  • Meet tu10

BIG5, WEEK 9 (2.11.2010)

  • Focus was changed to Facebook
  • Advert draft questionnaire is done and shared
  • Questionnaire about putting infos to the waiting list has been done
  • Listing what is going to be in the fan page is started
  • One member left the group

Risks:                      

  • Time is running
  • No programming skills
  • No demo to present still
  • Co-operation with tu10

Contingency plan: 

  • let's breath* let's find a programmer
  • let's try to keep the boundaries

Next steps:

  • sales pitch again ?
  • share the questionnaire
  • start to do the fan page proto with some tool

BIG5, WEEK 6 (12.10.2010)

  • Second meeting with 24Online again
  • The three campaigns has been defined
  • Sites has been continued ( Web technologies )
  • The sales pitch has been done ( ADP )
  • Conversation about the co-operation with Uudenmaan Insinööriopiskelijat
  • Visioning the adverts are started

Risks:                      

  • No innovative ideas
  • No graphic skills
  • No programming skills
  • Motivation problems because of confusion of project task

Contingency plan: 

  • We just put all that we ever can image on the paper as a list
  • We create just the spefications and the rest is 24Online's task
  • Let's do it how we feel it

Next steps:

  •  
  •  

BIG5, WEEK 5 (5.10.2010)

  • Meeting with 24Online
  • The campaign changed
  • The questionaire has been shared by facebook
  • Routes are defined
  • Co-operation with school is started
  • Project manager was sick 30.9.-5.10.2010 and coding manager is on a vacation for ten days

Risks:                      

  • Foundings in the research
  • Scheduling
  • Abences
  • Motivation problems because of the changing the campaign

Contingency plan: 

  • Sit down and think if the campaign is the target group right.
  • Sit down together on saturday with glass of wine and think the business ideas again
  • Not so much partying, more attendance
  • Cheering !

Next steps:

  • do the sales pitch for next week
  • developing the application and internet page

Big5, week 4 (28.9.2010)

  • The questinnaire is done, waiting for sharing
  • Scheduling the meeting with 24Online
  • Business plan have been done ( Power point slides)
  • Business ideas has been listed,
  • One application proto type has been started

Risks:                      

  • Share the questinnaire doesn't go well
  • No killer business ideas
  • Scheduling
  • Motivation problems (sometimes)

Contingency plan: 

  • Ollaan tarkkoja ja innostuneita jakamaan
  • Sit down together on saturday with glass of wine and think the business ideas again
  • Do as much taks etc at school as it's possible
  • Let's put all our power on this !

Next steps:

  • Share the questinnaires
  • developing the application
  • Continue the marketing and strategy plan ( thursday, friday)

Big5, week 3 (21.9.2010)

Status:  

  • Metropolia sales and marketing plan is on the way
  • Met the 24Online CEO and agreed on lunch together this week
  • Represented Big5 on Run2Shop party
  • Lots of brainstorming being done, nothing concrete is ready

Risks:  

  • Vellu leaving soon for a vacation
  • No real ideas
  • No serious vision about the future plan

Contingency plan:

  • Afterschool-meetings
  • Waking up for the school for real
  • Vision from 24Online on Thursday
  • Big5 together!

Next steps:

  • Meet the 24Online CEO on Thursday
  • Polishing the teamwork and methods
  • Kicking each others to do give more for the project
  • CHEERING!

Big5, week 1 (9.9.2010)

Status: 

  • The roles has been assigned, team is named and SWOT-analyse is done
  • Got acquainted with the company and their situation now
  • Defined the task for run2shop: what is the customer problem, what we have to do and what is our goal,
  • Target group of customer is defined

Risks:                      

  • lack of coaching
  • no programming education
  • too much other school work now

Contingency plan: 

  • keep on touch to coaching
  • get a programmer to our group or study programming or overwrite some way
  • do tasks on lessons not at home

Next steps:

  • market research: other broadband retailers' prices and services, customer analyses
  • developing the application (slogans, marketing channels)
  • starting project plan, business plan
  • party with Run2Shop people

!DRAFT! Big5, Date !DRAFT!

Status: Describe here the current status

  • xxx
  • xxx
  • xxx
  • xxx

Risks: List here the risks                       

  • xxx
  • xxx
  • xxx
  • xxx

Contingency plan: Actions to decrease the risk here

  • xxx
  • xxx
  • xxx
  • xxx

Next steps: _List here the things you’re going to do in the next week_

  • xxx
  • xxx
  • xxx
  • xxx
  • No labels
You must log in to comment.