Get feedback in class today
Get Company C to do metric - 3 people
Correct Grammar issues
Match the handbook requirements
Put in Ravi, Kris and Ruselle comments
metric results
Read Ravi paper - give him comments
provide a better introduction/abstract and look to remove the repetition of the same thing
abstract
introduction
overall flow
conclusion future work
limitation
MERGE references and appendix
so like explicity state ur weights
why agile is rated at 30%
why is that the same as change management
There is also a demo done for users every two weeks, so they can see the progress of the project as it builds up as well as requirements can be collected along the way as well as bugs detected early.
could read as
A demonstration, is done every two weeks, so users can evaluate the progress of the project. By doing this demonstation of the product at this point, new and changing requirements can be gathered, and issues with the software can be detected early.
link recommendations with metric very closely show how they work in tandam
and explain ur metric
but i think u should tie it in to ur metric section
then tie that into recommendations
have a paper on like User Acceptance of Agile IS
so can u expland ur future work
to include how better integrates
User Acceptance and the methodology
u making the assumption that the reader knows what a print is, what a standup is
what a sprint review is
u cant get the real story by simply sitting in on a meeting
u have to do like u had said speand a few whole days there
and be a snoop
to ge the full story
Meeting with supervisor:
expand explanation on UA metric
how it can be expanded/augmented?
in what cases it can be used for?
what does it need it to work...
how it can be modified to work differently?
so it is not just a generic solution
limitations of the metric
dissect it
limitation
scores 9 people - use a larger cross section of people ssample next time
i can use an agile diagram from a web site. jus reference it
