EPF Content
I1 - Status Assessment

1.	Summary
Iteration #	I1	
Assessment target	EPF Content	
Assessment date	May 02, 2007	
Participants	•	Per Kroll
•	Jim Ruehlin
•	Ana Pereira
•	Bjorn Gustafsson
•	Nate Oster
•	Bruce MacIsaac
•	Ricardo Balduino	
Project status overview	•	Practice Library – most practices have started weekly calls, have bugs created in Bugzilla, and contributors speeding up on work – Yellow 
•	Other content areas, e.g. Scrum didn’t have representatives in the meeting today, so status hasn’t been reported– Red 	

2.	Assessment against Objectives
Below you find assessment against objectives defined for I1 in the release 1.5 Project Plan.
•	Practice Library
•	Produce project plan
o	Done. 
•	Perform iteration planning
o	Not complete, since not all practice leads were available at the iteration planning session, and not all bugs were captured in Bugzilla at that time. 
•	Capture issues in Bugzilla for each practice
o	Not complete - Some teams added bugs to Bugzilla and started signing up for bugs, but some didn’t (Shared Vision, OpenUP general, Agile Testing)
•	Method Authoring guidelines enablement
o	Everyone reads and reviews – Not Complete. Presentation was delivered, material was made available to committers/practice leads, but no feedback was provided.
•	Each practice owner enabled on status of work in his/her practice(s)
o	propose Bugzilla items for what is missing on a practice
o	feedback from each practice owner
o	Start weekly calls per practice
o	Not complete, since 3 practice teams haven’t started work in this iteration

3.	Status Report

Management Practices
Ana reported:
•	Ricardo raised bugs based on Margaret’s reports
•	Ricardo completed 3 bugs – need to be verified and closed
•	3 bugs assigned to Ana – will start working in Elaboration
•	2 assigned to Scott Ambler – Ana to ask Scott about status
•	2 assigned to Richard Knaster
•	2 assigned to Ricardo
•	Ana reviewed old OpenUP bugs, some where moved to practices: 146476, 200845, 158473 
•	XP content – sustainable pace 171120 should be assigned to practice
•	2 more XP practices – may fit or not to current practice work: 171119, 171122 – team to decide where to put those during PM meetings
•	163872 creating examples for project plan – broad group needs to decide if examples should be OpenUP specific or generic
•	10 more bugs – Ana proposes we solve half of them in May

Agile Testing Practice
Nate reported:
•	Not much done on this iteration
•	Nate went thru architectural changes. There is a meeting with Dan Popescu on Monday 5/5.
•	Nate thinks content changes will not be greatly affected by architectural changes, because existing content was well encapsulated
•	Majority of work will be bugs like merging XP and such – which means, new things to be added
•	There are people in ATS willing to contribute to test automation – team needs to bring them on board.
•	Guideline material to be added as new bugs

EA, ED and TDD Practices
Jim reported:
•	1 bug resolved
•	missing diagrams on activities 
•	TDD, ED and EA bugs have been assigned to people
•	Some new concepts have been identified
•	no sense of how much will be accomplished in May yet
•	EA is a bit behind; there’s new person in UK joining with Mark, but Jim doesn’t know status

Shared Vision Practice and Overarching Issues
Steve didn’t join the call. On last report, Steve said he will be unable to sign up for work until some point in June. We had said that at least bugs should be captured in Bugzilla to give a chance for people to volunteer to do work. No progress made on that respect.

CI, CM and UCDD Practices
Chris Sibbald wasn’t able to attend the call, but sent a detailed description of work done and plans for next iteration, with respect to these 3 practices. Please refer to his note to epf-dev for more details here: http://dev.eclipse.org/mhonarc/lists/epf-dev/msg02731.html

4.	Work Items - Plan vs. Actual
This is current status of work items. We will provide meaningful milestone numbers for teams to assign bugs accordingly. 

Link to Bugzilla work on all practices:
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywords&short_desc=ID%3A+2LPP%3A+RVL%3A+WT%3A+CM%3A+TDD%3A+ED%3A+EA%3A+SV%3A+UCDD%3A+AT%3A+CI%3A+OpenUP%3A+%5BPracLib%5D&classification=Technology&product=EPF&component=Content&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=PM+Practices&query_based_on=PM+Practices&field0-0-0=noop&type0-0-0=noop&value0-0-0=

Teams, please also make use of proposed prefixes to describe bugs, so we can easily generate queries in Bugzilla (refer to this email for details on proposed prefixes: http://dev.eclipse.org/mhonarc/lists/epf-dev/msg02714.html

Link to old OpenUP bugs – practice leads need to clean up those bugs and assign to new effort / close as appropriate:
https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_status&y_axis_field=assigned_to&z_axis_field=target_milestone&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=EPF&component=Content&component=Content+Translation&component=Documentation&component=Website&version=0.9&version=1.0&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2! =&bugidtype=! include&bug_id=&votes=&chfieldfrom=2006-10-01&chfieldt o=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=assigned_to&type0-0-0=notequals&value0-0-0=epf.tool-inbox%40eclipse.org 

5.	Other Concerns and Deviations
•	Per to touch base with Rally about their participation in the project
•	We need to make it easier for new people to get involved and join
o	Set of practices is not fixed - if you are not co-lead, you can join anyways, or propose other practices and lead them
o	We need to host one-on-ones where new contributors can raise their voices and feel comfortable
o	Where do they get started? We need to have “new user” sessions frequently – user orientation day. Record 30 min presentations, have follow up Q&A sessions
•	what is a practice
•	how they contribute new practices or contribute to existing practices
•	explain the practices architecture, so it is easier to contribute
•	how to get bugs assigned
•	advertise where help is needed
o	Bjorn to send a list of difficulties he had, so we can address those issues
•	Nate to ping Ken about the Scrum plug-in – what’s the status
•	Release
o	What is the vision for this release?
•	Only architecture changes, or is there need new stuff to be added per practice?
o	if we have new things, capture them in Bugzilla
•	if can’t do now, keep in the backlog
o	Current vision looks like: existing backlog + architectural changes + OpenUP process + non-OpenUP process
o	Jim and Ricardo to discuss that next week and create a high level vision
•	Bruce proposed to move over to EPF 1.5 starting Monday 5/5
o	Tag the library in CVS (keep history) – Ricardo to do that
o	There is no conversion of library, but new features
o	Ricardo to send an email to epf-dev announcing we are upgrading to EPF 1.5
•	Bruce and Ricardo to sync up on what version to use
•	Per proposed to use 1.5 number for this release
o	Assign bugs to 1.5 Mx
o	It helps people to see work per iteration and sign up for work
o	Ricardo to check Bugzilla for existence of those milestones, or create new

6.	Lessons Learned
•	Not discussed in details for lack of time, but it seems from discussion above we need to make it easier for new people to join the project. Actions have been identified above.

7.	Planned for next iteration
o	The current project plan has the following goals for Elaboration iteration E1:
o	Continue assigning and addressing bugs per practice
•	Architectural changes, old OpenUP bugs, and new material
o	Make sure all practices are structured according to method authoring guidelines
o	Put out a beta and ask OpenUP users for feedback
•	Should it be done next iteration instead, when we will have a more stable and complete library?