Changeset 7fcc82e

Timestamp:

Mar 22, 2011, 7:54:32 PM (15 years ago)

Author:

Alex Dehnert <adehnert@…>

Branches:

master, fysm-4-1, space-access, stable, stage, test-hooks

Children:

952077b

Parents:

00900a3

git-author:

Alex Dehnert <adehnert@…> (03/22/11 19:54:32)

git-committer:

Alex Dehnert <adehnert@…> (03/22/11 19:54:32)

Message:

Rewrite of letter

File:

• design/stakeholders/2011-03-followup.txt (modified) (2 diffs)

design/stakeholders/2011-03-followup.txt

@@ -1 +1 @@
 Subject: Followup on ASA database
 To: laflynn@mit.edu, kamills@mit.edu, pwalsh@mit.edu, pdc@mit.edu, aeerwin@mit.edu, campus-activities@mit.edu, schedules@mit.edu
+CC: accounts@mit.edu, finboard@mit.edu, gsc-treasurer@mit.edu
 CC: asa-db@mit.edu, asa-exec@mit.edu
 Reply-To: asa-db@mit.edu
@@ -6 +7 @@
 Attachment: /mit/asa/Scripts/django/asa-db/design/stakeholders/pre/responses.txt
 
+
 Hi again,
-   I contacted all of you back in December about what functionality you wanted in the ASA database. After getting distracted by other commitments, I'm finally resuming work on this.
 
-I've attached a list of the requests that I got from my previous email (in December), as well as the notes from when Rachel and I met slightly before that.
+A couple weeks ago, ASA, SAO, CAC, and DSL met to discuss possible plans for organizing development of the ASA Database. At the meeting it became clear that we lacked information abotu what the stakeholders needed out of a new Database development process. This is more preliminary than the specific features that each of our groups said they currently used and wanted from the Database (the topic of my December e-mail), since the sense of the meeting participants was that we needed to know more about how each stakeholder wants to interact with continued development of the ASA Database.
 
-A couple major things stick out at me:
-* Having the new database automatically email on changes would be popular
-* Reporting needs improvement --- in particular, "export as Excel" would be popular, though there were other concerns
-* Better tools for enforcing requirements like president/treasurer status and 5-50%
-* Getting rid of (or making more flexible) some of the limits like one president, six signatories, etc.
+Therefore, I'd like to know:
 
-If you have additional requests, please let me know.
+How often has your office wanted development work (new features, bug fixes, and modifications) on the ASA Database in the last several years?
 
-Last week, we had a meeting amongst representatives of the ASA, SAO, CAC, and DSL about what the right way to move forward on the database rewrite project. One thing the meeting suggested to me, at least, was that we need more information before making a decision on that.
+How much do you expect your office to want *ongoing* development work in the next several years --- specifically, features or modifications that aren't part of possible Database development work this year, but will be wanted in the future because of changing requirements?
 
-Therefore, I'd like to know to what degree your office wanted ongoing development work on the database over the past several years, and to what degree do you expect to want ongoing development in the future. (Note that this is not what you want in terms of changes *now* --- I want to know about how much you expect your requirements to change later.) I'd also like to know to what degree you expect the need for changes to be driven by ASA policy changes versus changes inside your offices versus changes pushed by a third party.
+As far as changing requirements on your end and desires for future development work, to what degree do you anticipate these to be caused by 1) ASA policy/workflow changes, 2) policy/workflow changes from your office, and 3) changes driven by some third party, comparatively?
 
-If you can provide responses by the end of the week, I'd appreciate it.
-
-Once I have responses, I'll assemble them and try to schedule another meeting. Please let me know if you'd like to be involved in that meeting --- absent other responses, I'll most likely contact the same people who were present at the last one. My hope is to bring a draft proposal to that meeting for us to discuss and possibly finalize.
+If you can provide responses by the end of next week, I'd appreciate it. Once we have this information, I'll schedule another meeting. Please let me know if you'd like to be involved in that meeting --- absent other responses, I'll most likely contact the same people who were present at the last one. At this meeting I hope to propose a draft plan for proceeding with Database development work, based on replies to this e-mail and my December one.
 
 Thanks,