2015Summer_ITC260

Welcome to class:

Summer2015_ITC260

Sprint Two, Task #2

Task #2: Consolidate the Controllers:

Today we re-grouped around the remaining controllers and will be consolidating them and committing them to the master. Several on the team started working on new controllers in this effort. We hope to have this done and have a report ready for Thursday, at the start of class (8/13/2015).

8/18/15 (WE DID IT!!)

Today, we’ll be talking about showcasing the work we have done so far and follow it up with a retrospective.

Today’s Tasks Mike M. - working on the welcome.php Dani & Mike - working on profile controllers, models and views Mandy - finished nav doc, working on showcase piece; Final navigation documentation has been uploaded Jenny & Anna - working on venues controller and SQL Report Max - working on contact form Nicole & Blake - deployment instance Report Shihpei - working with Mike & Dani on profile controller, models and views Kristie - Reviewing nav docs and getting a working instance

8/13/15 (Almost Done!)

Today’s Tasks Mike M - Fixing the welcome page Mandy & Nicole - working on the gig controller Report / Created Navigation Instructions (already uploaded to repo in docs folder) Dani & Mike - working on the profile controllers and models Jenny & Anna - working on startup controllers Report Code Review: Report Max - working on the contact email controller Blake - checking the link paths Report

8/11/15 (3 more classes)

Today’s tasks Max - Contact.php controller Mandy - Code review of Gig.php controller -> Code Review: Gig Controller Mike M & Nicole - Gig.php controller Dani & Mike - Profile_list.php and Profile_form.php controllers and models Anna & Jenny - Startups.php and Startup_form.php controllers and models Kristie - Nav Documentation.

Sprint Two, Task #1

Task #1 Research the controllers:

By now most of the branches have been managed, and most of the team is working on managing the controllers in a similar fashion. Tuesday we divided up the controllers, and today we’re working more deeply on them. We’re expecting a report covering each of the controllers of which we’re in charge. Here are the items to consider reporting on:

1. Controller name
2. Is the controller functional? What does it need?
3. What is the purpose of the controller?
4. Does it need to be merged with another controller? If so, which?
5. Does it have proper names throughout? (the controller should be a singular noun, like “gig” (Gig.php) methods should be for example, list,view add, delete, edit, etc.
6. Is the data merged successfully with master?
7. Is it linked yet in the main nav?

Sprint Zero

Sprint Zero:

By sprint zero we mean work done before the official work of the sprint. In our case this means work pruning the 16 or so branches left from the previous quarter and merging the code. It also means investigating and consolidating the various SQL files in the repo. Last it means to identify and prioritize (and potentially consolidate) the various controllers inside the app.