6. Developer@ j3C
Sprint review
Sprint 1 Review
• Ensured all have most recent version of project in NetBeans via GitHub, MVC communicating with the database, running ok in browser
• Demonstrated database structure
• Demonstrated view all and view single blog post pages pulling from database
• Demonstrated and reviewed wireframes and current HTML/CSS content
• Reviewed Scrum board and User Stories to ensure we are working on ‘must have’ content
• Divided User Stories and other tasks between team members, with some pair programming included
Sprint 1 Retrospective
What didn’t go well (STOP):
• Scale it back a bit: some areas moved very quickly and became confusing
What went well (CONTINUE):
• Planning
• Lots done
• Efficient
• Good team communication & Daily Standups
How we can improve for Sprint 2 (START):
• Focus on main functionality for User Stories
• Create a separate channel in Slack to share links or images so they aren’t lost in main team discussion
• More pair programming
Plan for Sprint 2:
• Create a flow diagram as a visual representation of our code, using debug and breakpoints
• Work on current User Stories: sign up, log in, log out, upload blog post with text and image, edit blog post, view recent posts
• Create our own user accounts using the sign up page
• Create a blog post each
9. No
Yes
Yes
Error found?
Error Page
error page
passed to
routes to be
rendered with
layout.php
view page
passed to
routes
to be rendered
with layout.php
No
Error found
Controller
requires
relevant view
Database
data returned
to controller
model action
(function)
executed
Controller
calls action
(model)
new instance
of controller
created
requires
relevant
controller
controller
action
validated
requires
Footer
requires
‘routes’
requires
layout.php
defaults
to “home
and pages”
No
Action &
Controller
set?
ConnectionSuccessful
Require
connection
(connect to DB)
index.php
Yes
requires
Header after
login.php
Developer@ j3C
MVC structure
