06/12/2009 (status)
From Square Root
n attendance: Abin, Loomi, Michael, Marco, Sneader, John and Dave
Location: Room 263
Planned Time (hrs):60 Minutes
Actual Time(hrs):
Time Agenda Sent: 15 hours before
Type of Meeting: Status
Contents |
Meeting Goal
Discuss weekly status results and topic of the week.
Agenda
Status Update 20 minutes
- Review agenda -- Marco 1 minute
- Review action items from last meeting -- Michael 1 minutes
- Planning and Charts comments --- Marco 10 minutes
- Mentor minutes -- Mentors 5 minutes
- Review action items from current meeting --Michael 1 minute
- Meeting survey -- 2 minutes
Topic of the week 15 minutes
- Architecture static perspective - (Abin)
Team Status 15 minutes
- Team status report -- All 15 minutes (Same as stand up)
Meeting Officers
- Moderator: Marco
- Time Keeper: Abin
- Scribe: Michael
Meeting Notes
Burn down chart
- We're in the danger zone
- Stop taking stuff from the backlog, finish what you've got
- Two things came together that caused a spike, some tasks took longer than we thought, a design task came up that needed to be repaired before adding new functionality
Earned Value
- We're behind
- It looks like we're on pace to catch up
- It also looks like our plan is behind the needed pace to finish on time
- The actual value is less than earned, don't know yet if it's within our set tolerances (8-12 hours)
Upcoming Iteration
- Monday is the start of the overhead days
- Wrap up overhead tasks by this weekend
- It looks like the Security Risks feature will slip. We'll need to talk to Nancy about this and possibly adjust our planning.
- We're going to hold on to our current plan for one more iteration so we can get a good feel for how to change our plan.
Mentor Thoughts
- The trajectory of the plan is not as we want it to be (in terms of earned value). What does the team think of this?
- We're still trying to figure out how much technical debt to take on as a team
- How much refactoring is too much? Ken Schwaber doesn't have the answer. How will you know?
- Pairing seems to be a good way to handle this.
- Are you collecting defects, do you have data on this?
- Trying to figure out how effective pair programming is
- Collecting bugs from testing but we haven't done any analysis on this yet. We have opportunities to do analysis on these things to see what we're doing.
Topic of the Week
- LOLz time for architecture
- Modifiabiltiy by looking from top to bottom
- "Buildability" by building horizontally across layers
- Continue to think of the three key quality attributes. Your changes could break this stuff, so think of the "horizontal" and "vertical" dependencies
- Looks like there are some perspective issues in the diagrams shown today, make sure you're taking into account the other views
Status
- Loomi - acceptance tests for choose elicitation techniques use case finished, Write the front end for select elicitation techniques, fixed some bugs, going to do some bug analysis.
- Sneader - asset and goal association is done, need some help finishing up tasks, think I can finish the feature by the end of today with help. I want another data access function for getting small pieces of data rather than big pieces of data.
- Michael - Keep an eye out for duplicated functionality (one specific case where marco and abin created duplicated code), meeting with Eduardo about statistical methods and tracking, Looking to finish teach step over the weekend.
- Abin - topic of the week, worked with sneader on his feature, fixed a couple bugs, looking at merging authorization objects
- Marco - Prep for client meeting, work on select security elicitation techniques will continue that hope to finish and have tested by the end of the day, will assign milestone tasking today.
Action Items
- Dave - send out the paper on XP vs. Earned Value
- Marco - send out milestone assignments
- Marco - make decision about what to tell Nancy about whether we'll be able to finish the risk assessment step.
Last week Action Items:
- Marco - Fix the timeline (done)
- Marco - consider revising the agenda estimates (done)
