Submission for Week 2

[martha-kumi]

Status Report

Achievements

1. Interviewed client and other stakeholders and gave feedback on their responses.

2. Acquired FOCUS schema from Daniel Botchway.

3. Built some part of the student perspective of our project.

What we could not do

1. We could not continue using C# due to inadequate knowledge and preparation for the MVC framework.

Insights

FOCUS schema is in PostgreSQL not MYSQL.

We might have to create our own small version of FOCUS since we are not sure if we will get access to FOCUS itself on time.

We as a team might need to go back to our clients to understand the big picture of the Advising system.

[rachelwarren]

Client Project Week 2 Grade

Team: Advising System Score: 87.3/90

Grader: Rachel Warren

Overall

Breakdown

Score	Possible	Description	Comments
8.3	10	Presentation on Tuesday	Todd: Love your description of the problem; very vivid. Like the student insights; need to spend a little more time with faculty who do advising. I liked your affinity; but the flows were not as enlightening as some others.
10	10	Factoid spreadsheet with 10 total interviews (Thursday)	I couldn't find this. I assume you have done it, can you send it to me and I will revise the grade.
14	15		Main CD Models consolidated from interviews: Cultural/Context model (3), Flow (4), Sequence(4), Physical(2), and Artifact(2). Flow and sequence should have at a minimum 3 constituencies. 3-4 sequences related to your scenario should be identified. Models can be done on paper and turned in via a high-resolution picture OR be built online using a drawing tool. Physical and Artifact are lower priorities and worth a smaller number of points. (Thursday)
8	10	Affinity Diagram from factoid spreadsheet. On paper or in sticky sorter (Thursday) 30 or more facts grouped appropriately	Not sure that you have 30 of them in there, but looks good nonetheless
5	5	Email report (cc’ing faculty team member) to client about who you have interviewed, and what you’ve learned. Attach your Tuesday presentation and cc your faculty member (Thursday)
5	5	Any Revisions to the architectural diagram in the wiki. (Thursday)	looks good
10	10	Define and implement a technical spike in your target tool set (Thursday)
10	10	Initial Story Backlog in Github (Thursday)	Good
5	5	Pull Request with status report (may not have much code yet, Thursday)	Good

[rachelwarren]

Client Project Week 3 Grade

Team: Advising System Score: 62/75

Grader:

Overall

Breakdown

Score	Possible	Description	Comments
18	25	Presentation and Demo of Progress	Fausi: No feedback from paper prototype. Also, demo did not show a slice through functionality. It would have been nice to have something from the adviser side. Todd: Excellent personas with good goals and attributes. Some of the stories are a little big---the reports may have some sub stories as part of the progress. Slice is ok; a little small.
20	25	Client Ready Project Vision and Scope of Work	The what we are not doing and the issues and risks section can and should be expanded. I'm not sure what they are, but off the top of my head I can make some guesses. For example, you are not replacing focus, you aren't replacing email. You risk creating a third system on top of focus and courseware which is hard to use, which might, I dunno confuse freshman more? Its important to think about these things.
15	15	Backlog in GitHub, implementation of your system	Looks good
5	10	Pull Request and Source code Management	Source code control looks really good, but no pull request....

[rachelwarren]

Now you should be able to create another one for week five, I will give you back the five points for weeks three and four now that I know why there was no pull request

[martha-kumi]

Thank you very much Rachel.