Regular Attendees
- Andrew
- Bill
- Brad
- Chris
- Dan
- Jonathan
General
- Call In To: Free Conference Call HD - DuraCloud Line
Please note that we will be using the Free Conference Call HD line for this call. Information about calling into this line is available from the link above.
- - Indicates who will be taking minutes
Discussion Topics
Planning Board
Task Board
DfR Planning and Estimating - 0.1
Topic Discussion Leader Tracking and Estimating Methodology Jonathan Review of Epics and ROM Estimates (Must be complete) Dan Kick-off Initial Stories Brad and Dan More stories and nothing but stories No one gets out of this - Brad and Dan List additional resources needed (perhaps a Git repo, addl mailing lists, bamboo build) Chris Coordination with DuraCloud builds, unit tests, ITs Bill Project and Partners Jonathan
Actions from last meeting
Last Weeks Actions:
Action Item |
Assignee |
Status |
---|---|---|
Create a wiki page with story point listing for epics |
Dan |
(wiki) |
Each of us submit number of story points for each of the epics over the next week |
All |
|
Tie some of the DuraCloud jira items to DfR stories |
Bill + Andrew |
|
Related Information
DfR Software Next Steps - Jan 2012
2012-01-03 - Architecture Meeting, Temple University
Status
- Jonathan
- Continued discussions with Fluid (overhead policy) and Thorny (public statements re collaboration)
- Meeting with Sloan program officer tomorrow
- Andrew
- DuraCloud/Shib architecture updates
- Bill
- Brad
- Unicon call
- Chris
- Dan
- Discussed with Andrew the strawman approach to Jira and most of the team. (Andrew was the road)
- Added a page for top-level estimates
- Worked on adding cards (towards covering the whole project)
- Met with Jonathan and Brad on priorities
- Jonathan
Minutes
- Epic level planning and estimating
- inputs from team complete
- Methodology
- epics/stories/tasks
- estimates are done at story-level
- if a story is > 8pts, it is converted to an epic
- need to add field in jira for story-points in 'tasks'
- it will take more time (6 weeks?) to hone in on accurate velocity
- Scheduling
- not all short-term stories have yet been created
- approaches
- start working, and back-fill jira work (planning)
- do not start iteration until jira work for iteration is complete
- suggestion
- get jiras populated for work in next two weeks out
- we come to next week's meeting with stories to review
- need basic agreements: java6? scm? appserver?
- define what each team member is planning on working on in short-term
- discussed jira DFR-63 as an example
-
- story-points 2?
- Bill 3pts
- Chris 2pts
-
- Brad and I to put story points against security tasks
- Dan and Chris to look at Object Creation Service
- Box account
- monthly ?$
- yearly $400
- will create an account as soon as we are ready to use it
Actions
TBD