Today we talked about the third milestone of the WEB assignment which is the implementation plan.

Our team got the following feedback:

  • Most sites were nice, clean, attractive, good simple management
  • It was good we picked up on the green theme – It can count in some markets like councils, ministry for environment and DOC
  • He thought to take the website to the next stage we would need to write up more detailed content from what he has told us. He also thought he would write up a bullet-pointed list of information about staff and the history of the company that we can take and re-write as website content.

What we also need to do is make a video about how to:

  • Login
  • Edit one page
  • Save the content

Additionally we need to write more content about the company and staff information, as we will have to deploy the website within the next two weeks we will need to (backup db, uploading to server). Nelson Data Systems will provide the subdomain and we will upload our files to their server.

Class notes on Implementation planning and Deployment Milestone 3

This is a formal definition for how we are going to build and deploy the websites. This is basically defining the systems development life-cycle we will use.

This report will require the following:

  • How the website will be implemented in the production environment – There is a template from Princeton University on Moodle for this part of the report
  • How we are working, by defining that we are using user stories (what the user stories are) as part of the Agile SCRUM methodology

SCRUM – Agile development method

Doing SCRUM as a one person team is hard as you will need multiple roles.

It was suggested that we adopt an agile, SCRUM like approach to getting our group work done. We will need to split up the work into user stories, this comes to 16 hours a week for a team of 4 people.

What we need to do in the next week is:

  • Prototype for KissMeHardy
  • Write short content for Nelson Data Systems

To implement the SCRUM method we will need to:

  • Identify the user stories
  • Determine how long each user story will be
  • Allocate a SCRUM role to each member of our group

 

SCRUM concepts – Quickly taken from the SCRUM video we watched in class

Features are user stories – They are the end user requirements

Product owner – Set direction of product

Scrum master – Like project manager he controls the workload.

Product backlog – Collection of user stories. Specific user stories to built.

Sprint – 2 days -30 day. Shorter the release Get portion of release backlog to ship state.

Burndown chart – Sprint vs time. Communicates the sprint breakdown.

Miscellaneous class notes:

SCRUM is the common software development mantra of getting the prototype out to the customer as soon as possible. This is the agile development method.

Todd was saying that our development server is our machines, and the production environment  will be the Nelson Data Systems web server.

Production environment will hide some errors, so  when it is deployed to the production environment the errors will be thrown and will break the system, this is where DevOps comes to the rescue. As I understand it DevOps is the aligning of development and production environment.

 

 

 

 

 

 

Advertisements