- Sprint demo was held on Wednesday 5/23, there was still work left to do on the MVP release
- Sprint planning for Sprint 2 has not been held yet, so we are still in Sprint 1
- Three main questions: what went well with the sprint, what went poorly with the sprint, what do you want to see changed in the next sprint?
- Joel
- Took way longer than expected, still have bugs to work out
- Disappointed with how the work went overall
- It was a good learning experience, realized that he hardly knew anything for working with Bootstrap going in
- Liked working with Ken and that we had a time period to complete the work
- Do not know what your schedule is like each week, so hard to estimate if you can get the work done in the sprint timebox
- Also a problem with estimating the amount of time that the work would actually take
- This can not be a full time effort due to also needing to job hunt (which has to take priority)
- Not sure how to correctly approach a bootstrap project
- Ken
- Challenge to find the time to get together with Joel. His role was to help Joel with his work on the project
- He gave advice on areas he had learned previously (more experience coming into this project)
- Is better at debugging, good at applying those skills
- Learned things as he helped Joel solve problems that the project ran into
- Did not like the strict agile environments and agile practices / meetings (too cumbersome)
- Need to get used to updating the Jira tickets to log progress on the work being done
- Agile is based on 40 hour work week, which does not work well for our group since we are not full time on the project
- Lora
- We do not have the right process in place regarding people/process/tools
- We spent 3 weeks just getting the tools set-up, that should have been done before the project began
- Liked the way the MVP product looked, being simple, not overly complicated
- More things to add to the website in later sprints
- Need to have a way to make the process work faster, closer to a business environment
- Tough issue to solve by us
- May need deadlines to help make sure things get done when expected
- No knowing the skill levels of the team members caused some issues
- We did complete what we intended to do for the sprint
- Suggests a process template be created for teams like ours to work smoother
- Having just a Monday meeting when doing an active project is not often enough for team to meet. Need to meet at least twice a week on a scheduled basis.
- Note: Joel and Ken still working on Nav Bar scrolling issue, so final MVP version is not yet publicly deployed
- First item on Wednesday agenda should not be Scrum, it is a general meeting for each team to update the rest of TSSG on what they were working on and interesting topics related to the group
Overview
Content Tools