Three questions:

  • What went well this sprint?
  • What did not go well this sprint?
  • What do you want to see changed/improved in the next sprint?

No debating items during each person's feedback, we will talk about issues after everyone has given their feedback


Frank

  • No feedback


Joel

  • Went well - got a decent amount of output with help from other developers in the group
    • Started using PHP, then switched to Javascript after security concerns were raised
    • Shared code through GIT
    • Using Jira to track status and testing had some learning pains but overall went well
  • Not well - went overtime with meetings
    • Some issues with testing
    • Some delays in getting work accomplished, took longer than expected


Jim

  • Was out for 2 weeks of the sprint, so was a remote observer for most of it
  • Most of the problems the team hit were things we need to tighten up so we have a better process in place
  • Went well - a lot of independent thinking and figuring out of things, lot of collaboration
  • Not well - spent more time than we wish we would to nail down the processes we wanted to use
  • Some personal issues on the approach to use
  • No suggested changes to our processes, keep a small number of stories for the sprint


Ken H

  • Well - got done all of our goal for the site to work right on a mobile device, fixed the issues we had coming into the sprint
    • Wish we had gotten more done this sprint
    • Better use of GIT this sprint, can still improve there
  • Not well - spent a lot of time thrashing around with Confluence and Jira and what was not working there
    • Audio conferencing can be difficult with people talking over each other and get points across.   This was an issue with our last sprint as well
  • Improved - do more development in this project.  May want to do an experimental side project for things that don't fit in with this sprint.  Learn new things without taking time from the project itself


Lora

  • Well - more hands involved in the project.  More people involved and talking with each other
  • Not well - logistics of the scheduling.
    • Went too far outside the scope of this project (good for developer but not end user)
    • We debated things that were not reliant to this project while it is hosted on Lora's server
  • Improved - next month, we look at the hard cut of the time to ensure we end when we are supposed to.   Do every 15 minute heads-up on time left during last hour.  Plan for rest of week during final 15 minutes of the meeting. 
    • The submeetings during the week are VERY valuable


Mary - absent from meeting


Paul - did not participate in the sprint so no feedback


Tom - no feedback


Tyler

  • Generally went well
  • Had a short training on X-Ray, but did not cover enough for creating test cases and test executions
  • Test executions were not showing up in the common board, should they appear there?
  • At some point, needs to present Google Analytics to team.  Need to decide when this will be done.
  • Working on getting the plug-ins into Edge so he can test more devices (broader coverage)
  • Rather than making the sprint longer, could put less stories into the sprint to keep them shorter


Wayne

  • Well - We accomplished our goals for this sprint!
    • LOTS of collaboration
  • Not well-
    • We went one week over our time box, but we expected that to happen and should plan for more time in Sprint 3 to avoid going over again
    • We want to do Agile but do not want to follow Agile practices
    • Story status, not person status - did it work better?
  • Improve:  The entire team needs training on how to properly use the X-Ray plug-in in Jira to create test cases, test executions, report defects, and test fixes to defects


Discussion:

  • Team needs to decide more time OR less stories in the sprint
  • Need to have a Ready To Test to the Jira workflow for Sprint 3
  • If people come in late, do a "this is what we are doing" when we move to next person rather than stop and catch that person up
  • Before Sprint 3 begins, need X-Ray training
  • What did we have in Rally for workflow?   What did we do there when something had to move from Test back to Development?
  • Need to decide what to do for bugs found in one sprint but fixed in a later sprint?
  • Team needs an agreed Definition of Done for our stories!!
  • Informal hand-offs from development to test so testing can be done in parallel
    • Make the functionality incremental so testing can be done on pieces while development is still in progress on stories
  • For the experimental development suggestion: do we want it part of actual sprint, do a spike, something completely separate from the sprint??
    • Do not want to go back to an always on-going project, better to have phases with specific goals so we can see things progress and get released
  • Where are we documenting up-coming projects?  Are we (web team) moving from the old Trac wiki to Confluence?  What about the rest of TSSG?
    • Bring up in Wednesday meeting: are we still using old Secure Source hosting?  It is still the SVN repository, but is anyone using the Trac wiki there?
    • This may require us to change our new member documentation if we are moving away from using the Trac wiki
  • Where will the web team document our future projects?  What information do we want there now?
    • Do discussions in Confluence, not via email
  • Most of the time is being spent on project management and very little time on actual development.  This is a problem that needs to be fixed!!
    • Different databases, different languages, different frameworks – these should be the focus of the web team meetings


  • No labels