List view
Items for review / completion during NDC
No due date•3/3 issues closedThis is our second milestone on the path to v1.0 release in December. Issues are tagged with proritiy: P1 (highest) through P3 (lowest).
Due by November 21, 2016•32/32 issues closedThis is our first milestone on the path to v1.0 release in December. Issues are tagged with proritiy: P1 (highest) through P3 (lowest).
Due by October 22, 2016•22/22 issues closedThis is our final milestone to release v1.0 in January! Issues are tagged with proritiy: P1 (highest) through P3 (lowest). Updated for a little breathing room into February as we are awaiting issues from scenario run throughs
Due by February 13, 2017•54/54 issues closedThis milestone is a set of items we would like to prioritize and/or target for completion during That Conference
Due by August 11, 2016•16/16 issues closedThis milestone will consist of all issues/bugs identified during testing that will be prioritized for fixing. Testing and user acceptance will drive the list of issues here found from the feature complete milestone that precedes it.
Due by August 31, 2016•48/48 issues closedFeature Complete milestone in advance of June 11th Go Live Production Deployment for Washington State Event Support. First we need to get everything implemented for features (this milestone), then test and fix issues before we go live (next milestone)
Due by June 13, 2016•21/21 issues closedWith this milestone, we will close feature development for Release 2 and document and/or fix any issues identified during user acceptance testing and field exercise.
Due by March 7, 2016Minimal Viable Product release of allReady for November 6 - 8. Focus of the November MVP sprint for allReady Base Architecture Focus In addition the functionality below we must fully prepare allReady for our private preview release by focusing the current work that will be culminating the event on: • Full fidelity deployment on azure – ensure all functionality works in deployment and not just on dev machines so that it can be used by external users in private preview • Database and connected services are in place – ensure all data is stored in the db and external services are functional to remove vestiges of early testing only stubs like in memory databases • Third Party Authentication – fully enable authentication with Facebook, Twitter and Microsoft Account to allow non-admin users of the system to access it during private preview Functionality Focus The functional focus areas for the allReady MVP release are as follows in priority order (there are of course other lower priority items to be completed worked on as possible): 1. Preparedness campaign delivery operations management (volunteer to task workflow & delivery of services) 2. Organization Campaign Publication and Dashboards (allow organizations to publish campaigns, create and assign activities and tasks and display metrics/impact information) 3. Volunteer sign-up (allow for campaigns where sign ups come from outside volunteers previously un-engaged in the delivering organizations) “Private Preview” Release Plan When we say we are focused on a Private Preview release of allReady for November we mean the following: Technically we are • Fully functionally complete and unit tested for the scope of effort • Fully deployed and able to be used/accessed ‘live’ on azure with persistence and external services • With little to no documented issues/bugs that would prevent preview use of the application in an preparation exercise as below From the using non-profit organization(s) (Red Cross) point of view we are • Able to user acceptance test the application (does it work for what they want – this will start in earnest on Friday as the release starts to come together and will continue that weekend as needed into the week or so until we can say we have reached the goals above • Then deploying it for preview use in an exercise either or both of a ‘simulation’ to put it through its paces and by tagging one or two of many teams delivering in the field to A/B test the applications real world use • Rapidly iterating to fix any issues/blockers/gaps identified during those exercises so we can rapidly get it to a ‘Public Preview’ release for production use by American Red Cross and other organizations • Goaling the project in achieving this Public Preview release by early December (based upon assumption of issues to be found and timelines including thanksgiving) • Later expand Public Preview with additional organizations and once we have confidence in its use by organizations outside of those involved in its development move to a full production release open to all organizations US wide and ultimately in a later version support internationalization and other requirements to support staged and/or full deployment to international markets.
Due by November 7, 2015•27/27 issues closedThis release will be our second private preview release and includes open, blocking issues from previous releases and the next wave of functionality for Release 2.
Due by February 29, 2016•9/9 issues closedWith this milestone, we will close feature development for Release 1 and document and/or fix any remaining issues blocking move Private Preview Release 2.
Due by February 22, 2016•43/43 issues closedPer documentation in November-MVP milestone this will be the completion of issues need to support private preview in an initial exercise use case
Due by November 18, 2015•16/16 issues closedStarting with this milestone, we are still finalizing the stories and scenarios that will be part of each release.
Due by September 15, 2015•4/4 issues closedDuring ThatConference, we will focus on getting the initial volunteer workflow working on the web version of the product. That is the MVP (Minimal Viable Product) key scenario.
Due by September 8, 2015This milestone encompasses a couple more cleanup tasks before we start sprinting toward the alpha and beta release. Data Management / CRUD: Our staging site runs against an in-memory database. That won't live beyond machine reboots, and we need to clean that up. Automated Tests: There is a test project that has a large number of automated tests on this code. However, that project is not loaded by either solutions, which makes it hard for new developers to find and run the tests.
Due by August 29, 2015•7/7 issues closedThese are the tasks to complete the transition from the code developed during the Visual Studio 2015 Launch "In the code" (https://channel9.msdn.com/Events/Visual-Studio/Visual-Studio-2015-Final-Release-Event?t=in%2Bthe%2Bcode) These involve replacing some hard coded names, getting names correct for the public release, and updating libraries.
Due by August 29, 2015•1/1 issues closed