nsf-open / nsf Goto Github PK

User story

As a someone working on the NSF project, I need to know how visual design directions were developed so that I can make better design decisions in the future

Acceptance criteria

• InVision prototypes and design files are documented in the NSF wiki

Definition of done

• Work in progress visual design artifacts are documented in the NSF wiki
• The NSF and 18F team are aware that design directions are not final and more work needs to be done.

User story

As a member of the team, I want to know when the mid-point checkin is and what will be covered so I can plan accordingly.

Acceptance criteria

• Given I want to attend, we'll need to select a date that works for everyone
• An agenda is agreed to
• Expectations around who should attend are shared so I'll know who to invite

Definition of done

• Date is confirmed and selected
• Agenda is completed and circulated
• Audiences for workshops are identified

User story

As a team member, I need to know when meetings are so that I can plan accordingly.

Acceptance criteria

Given that there are a lot of upcoming meetings involved in establishing our cadence, we need to get some things on the book:

• A date and time for sprint planning and retros is selected
• A calendar invitation is sent to the rest of the team

Definition of done

• The team accepts the meeting invitation
• The NSF accepts relevant meeting invitation

User story

As an attendee of the recent mid-point workshops, I'd like a summary of what we learned so that I can understand our next steps and how they apply to me.

Acceptance criteria

• Given that the workshops are completed, and
• We have a list of next steps,
• a written report will help the team document and track our progress against our goals.

Definition of done

• Write-up of findings is completed
• Write-up is delivered to NSF for comment / feedback

User story

As a user researcher, I want to conduct a remote user research workshop with NSF so I can better prepare them and the team for future research work.

Acceptance criteria

• An invite / brief to the remote workshop has been written that explains the value of the workshop.
• An agenda is created
• Relevant OLPA and IDB staff should be identified and invited to the workshop.
• A date and time is selected.
• A calendar invitation is sent

Workshop prep

• Intro slides for workshop
• Final agenda distributed
• Supplies confirmed
• Final slide deck complete

Definition of done

• The date, time and agenda are agreed to and scheduled.
• The remote workshop is conducted.

User story

As a visual designer, I want to create a moodboard to aid with visual design concepts for the nsf.gov website so that we can discuss different design concepts with stakeholders

Acceptance criteria

• Conduct a visual design audit science media/content comparative analysis
• Understand initial user needs based on preliminary user interviews
• Archive visual design elements into a moodboard
• Create moodboard to show on InVision

Definition of done

• Three different concepts and rationale have been added to the moodboard
• Vetting concepts with the team to get feedback

---

Links on InVision (Work in progress)

Moodboard

• moodboard

User story

As a user researcher, I want to set up a website recruitment test so that I can see if we can recruit users in real time from the website.

Acceptance criteria

• Have conversation with NSF's website recruitment test provider
• Schedule conversation with NSF website owners, website technical contact
• Confirm availability of NSF folks, and make proper introductions (NSF)
• Choose pages to target for recruitment
• Finalize implementation details
• Follow up with NSF on where we are in terms of discussions with external users (s). (When we do reach out via research plan, make sure to give NSF a head’s up!)

Definition of done

• Confirmed plan with NSF's website recruitment test provider
• Conversation with involved parties on NSF is scheduled, and availability confirmed by NSF
• Page for recruitment is selected
• Implementation details finalized

User story

As a visual designer, I want to demonstrate the value of visual design to the NSF project team so that visual design is an integral part of a redesign.

Acceptance criteria

• Pull together basic principles of design
• Add first draft mockups
• Sync with team to make sure it flows with project timeline

Definition of done

• Complete presentation to talk about the value and process of visual design
• Add first draft mockups [if needed]
• Vetting concepts with the team to get feedback

---

Links on InVision (Work in progress)

Slides

• Visual design kick off

User story

As a site administrator, I want to understand how other similar organizations are handling visual design so that I can make informed decisions about what appears to work well and what doesn't.

Acceptance criteria

• Begin researching comparable solutions.
• Document comparable solutions.
• Create a matrix for a comparative analysis of other science sites/resources.
• Conduct a visual design audit of other science sites/resources.

Definition of done

• A first draft of the comparative analysis is completed.
• The draft has been circulated for comment.
• Major conclusions are communicated to the NSF team.

Notes

• This isn't dependent on #11 but it's in the same doc and related.
• Visual Design audit in the screenshots tab of Kate's doc
• Aesthetics in NSF comparative analysis takeaways in Kate's doc

User story

As an NSF team member, I want to narrow down the universe of CMS options and identify/prioritize key considerations for getting to the next step.

I want a draft core CMS feature recommendation doc to track tie-in between hypothesis, prototype and final recommendations for CMS.

Acceptance criteria

• this should become part of the final CMS recommendations at the end of the engagement
• Initial conversations with CMS SMEs at 18F are held;
• Initial conversations with AcqStack at 18F are held.
• The document should identify CMS options and what to consider in choosing a CMS
• Document outlines how to select CMS taking into account user needs as the top priority
• CMS should allow for hosting in a cloud environment
• Understand, schedule and align and staff technical expertise / cloud.gov elements for the next month’s CMS prep
• Narrow down the universe of CMS options and identify/prioritize key considerations for getting to the next step
• CMS matrix for comparison and functionality prioritization

Definition of done

• A draft CMS template / doc is delivered.
• Document identifies a clear recommendation on how to move forward.

User story

As a someone working on the NSF project, I need to know see how NSF visual styles would be incorporated into a U.S. Web Design Standards prototype.

Given that the beta is to be essentially a MVP, it is assumed that:

1. The US Web Design Standards will be employed; and
2. Any additional design at this point will be minimal and geared predominantly to ensuring the use of the beta is pleasurable and intuitive.

The goal of design work for the beta is not to duplicate the design of the current nsf.gov website. In order to do this, we need to determine:

• If any additional design is needed, who will be leading that work;
• If there are any brand guidelines established by NSF (including logo usage, palette, typography, other UI components), they are clearly defined and have been provided;
• Design LOE is agreed to between 18F and NSF.

User story

As a visual designer, I want to concept different styles for the nsf.gov website so that we can discuss different design concepts with stakeholders

Acceptance criteria

• Conduct a visual design audit science media/content comparative analysis
• Understand initial user needs based on preliminary user interviews
• Mockup concepts and post them on InVision

Definition of done

• Three different style tiles (typography, style goals, similar sites, content type, and color palette)
• Rough mockups incorporating that particular style using the USWDS template
• Vetting concepts with the team to get feedback

---

Links on InVision (Work in progress)

Style tiles

• concept 1
• concept 2
• concept 3

Mockups

• homepage based on concept 1
• homepage based on concept 2
• homepage based on concept 3

User story

As a user researcher, I want to begin identifying interview participants so that I can understand what educators and science influencers need from a future nsf.gov website.

Acceptance criteria

• Reach out to NSF for list of possible participants
• Receive lists from NSF
• Start a plan for remote gathering of user vision from OLPA/etc (and back-up plan for asynchronous remote
• Email PTE to suggest remote user-def workshop with OLPA and IDB staff

Definition of done

• List of participants received from NSF
• Script developed and accepted
• Get alignment on user groups - keystone activity for starting recruitment; Identify groups, channels for outreach to people unfamiliar with NSF
• Conversation held with NSF and maybe Legislative Affairs rep
• Send a prioritization list to NSF, and outreach plan (Kate)

User story

As an NSF member of this team, I want to join Github so I can participate in the issues as assigned.

Acceptance criteria

• Get list of NSF users, and reach out to them
• Invite NSF folks to GitHub project board

Definition of done

• NSF team is invited
• NSF team joins!

User story

As an NSF employee, I want to see how the user recruitment form looks and behaves on a sample page so that I can understand the impact the recruitment will have on the NSF page.

Acceptance criteria

• Given that I am an NSF employee, I should know how the form will look and behave
• The form elements shouldn't obscure or conflict with other elements on the page
• The form should behave in a manner that is unlikely to cause annoyance to NSF.gov site visitors

Definition of done

• The sample content page is selected and deployed on Federalist
• The form is implemented on the sample content page
• The form is determined by NSF to behave the way it should and is accepted.

User story

As a user researcher, I want to begin scheduling interviews for week 2 of this sprint so that I can be prepared to test our first prototype(s).

Acceptance criteria

• We have individuals identified for user research; and
• We have a prototype ready to test; and
• We have modified our research plan accordingly.

Definition of done

• Individuals are contacted and interviews are scheduled.

User story

As a content designer, I want to develop a more in-depth understanding of NSF's content types, editorial calendar, and social media strategy so I can integrate this information into content strategy recommendations.

Acceptance criteria

• Complete list of NSF content types/observations
• Review NSF's editorial calendar
• Review NSF's social media plan
• Get answers to outstanding questions

Definition of done

• Share content types document with team
• Review editorial calendar
• Review social media strategy doc
• Send questions to NSF

User story

As a team member, I need to have a high-level sense of the project timeline so I can plan my work.

Acceptance criteria

• Broad schedule of goals and questions is drafted
• Identify next round of workshop type(s) and dates, confirm availability with team and NSF

Definition of done

• Schedule is shared with team
• Scheduled is provided to NSF
• Potential scheduling risks and opportunities are identified

User story

As someone responsible for the web recruiter, I want to confirm the recruiter is set up and working properly so I can deploy it on more pages.

Acceptance criteria

• The web recruiter exists and is avaiable on NSF.gov
• The form is set up and working properly
• Recruiter appears to be wired correctly

Definition of done

• Team confirms web recruiter is reviewed and is working correctly
• Recruiter is deployed on correct pages off NSF.gov domain

User story

As a designer / developer on the team, I want to know what early indications of hypotheses might be so that I can start planning for the first prototype.

Acceptance criteria

• Given that the user interviews will help uncover early trends that might warrant exploring with a prototype, I want to vet these early trends with other members of the team; and
• I'll need to understand what kinds of hypotheses might make for good, eventual candidates for prototypes; and
• which prototypes might ultimately be the most useful to the NSF's discussion around managing content in the future.

Definition of done

• Early trends have been identified
• Early thoughts on hypotheses are generated and shared

User story

As a someone working on the NSF project, I need to know when and where the kickoff meeting will be that I can plan on attending.

Acceptance criteria

• A date and time for the kickoff meeting is selected and scheduled
• A calendar invitation is sent to the rest of the team
• An agenda is developed for the kickoff meeting
• Room / location is scheduled
• Travel requests are submitted

Definition of done

• The team accepts the meeting invitation
• The NSF accepts the meeting invitation
• NSF approves the agenda
• Travel is approved

User story

As an NSF member of the team, I want a place where I can access all the related reports and documentation so that I can refer to it easily now and in the future.

Acceptance criteria

• I want a place where I can access information easily.
• The information should be available for internal consumption by NSF staff.

Definition of done

• Documents and folders are created and uploaded to the NSF wiki.

User story

As a member of the NSF team, I'd like to schedule regular in-person checkins so that we can continue to communicate the goals of the project with our stakeholders.

Acceptance criteria

• Given that in-person checkins can help us provide updates, attend certain working group meetings and answer questions; and
• We have a good foundation for our prototyping effort, we believe these in-person checkins will help us be available for issues / questions periodically as they come up.

Definition of done

• checkins are scheduled
• travel is arranged and team members selected

User story

As a designer / strategist, I want a style guide / design guide / content guide so that we have a uniform way of delivering product.

Acceptance criteria

• [ ]
• [ ]
• [ ]

Definition of done

• [ ]
• [ ]
• [ ]

User story

As a <type of user>, I want <a goal> so that <benefit>.

Acceptance criteria

• Given that the user research is synthesized and the workshops are complete, the team has developed three initial hypothesis; and
• given that the initial prototyping environment and design assets (e.g. USWDS) are pre-staged;
• I can begin making headway on further defining roles and responsibilities for prototype development with the team; and
• the team is ready to start working on prototype development.

Definition of done

• Workshop is complete
• Initial hypotheses are agreed to
• Work plan is in place for first prototypes

User story

As a team member, I want a platform that allows me to rapidly prototype ideas.

Acceptance criteria

• Platform is selected that allows quick prototyping from a Github repository
• Platform is set up
• Rights are granted for relevant team members

Definition of done

• The platform is selected, presented and accepted by the team members
• Access instructions are provided to relevant team members

User story

As a user researcher, I want to know when outreach to lists is successful so I can plan on a new release to the next listserv on the priority list.

Acceptance criteria

• Users for a given list are contacted, and recruitment catches up with responses
• An outreach list exists
• Given that recruitment is happening via Twitter, web recruiter and listservs, a tally of our user types is kept so we know which ones need additional outreach

Definition of done

• NSF is contacted when each recruitment effort is finished for any given list.

User story

As a team member, I need to know what the first hypothesis is so that I can start developing a prototype to test.

Problem Statement

We believe that people interested in science information and news do not visit NSF.gov on their own. We suggest that by making science information and news more discoverable through the channels they are already using, and written in a way that is more appealing to a broader audience, we can increase the visibility of NSF.gov amongst a wider range of individuals interested in science news and information.

Hypothesis #1

Option 1: Improving the article page [page icon in Mural]
We believe that improving the website experience for users who reach articles from social media will result in more engaged readers who are interested in pursuing further information about NSF. We will know this is true when we see users click on other articles, pursue related resources, or subscribe to similar news.

• How related content is displayed
• Other articles
• Further reading/deeper dive for reporters and science learners
• See the research sidebar
• Calls to action for RSS feeds or other subscriptions
• Page element tying article to NSF mission (“how NSF makes this possible”)
• Summary/tl;dr — top level points for science communicators
• Connection information
• Entry point for people who want to reshare them
• Better multimedia

Candidates:

https://www.nsf.gov/discoveries/disc_summ.jsp?cntn_id=242898&org=NSF&from=news
https://www.nsf.gov/discoveries/disc_summ.jsp?cntn_id=242850&org=NSF&from=news
https://www.nsf.gov/discoveries/disc_summ.jsp?cntn_id=243064&org=NSF&from=news
https://www.nsf.gov/news/news_summ.jsp?cntn_id=243121&org=NSF&from=news

Acceptance criteria

• First hypothesis is identified and agreed to; and
• Ideas around the hypothesis are sufficiently developed enough to allow us to start developing the prototype;
• Content type is selected (news page? topic page? article page? jellys article?)
• Calls to action for subscription
• An NSF person is identified as the lead on the article page;
• If someone would share what they find;
• Statement that explains the deeper connection to NSF, and further reading;
• Tweets are written;
• Page is redesigned (but still complimentary to the existing NSF page);
• Page is launched on Federalist;
• We have rewritten the content; and
• We can conduct moderated user testing.

Definition of done

• The first iteration of the first prototype is complete and published

User story

As a team member, I want to understand how work moves between UX/content > visual design > front end dev for a sprint cycle.

Acceptance criteria

• A cadence of moving items ready for review between UX/content > visual design > front end dev is identified and documented
• The flow is presented to the team for review
• The team suggests any modifications and they are made

Definition of done

• The team has agreed to the cadence
• The cadence has been documented on the NSF wiki.

User story

As a content designer, I want to demonstrate to NSF the value of user-centered content design so that they can adopt some user-centered principles, if they prefer.

Acceptance criteria

• Create content-focused portion of presentation deck
• Get/incorporate team feedback on presentation
• Present to NSF team during onsite workshop
• Document next steps

Definition of done

• Present during onsite workshop (9/19)
• Document next steps + turn them into action items

User story

As a member of the project team, I want recruiting email templates available so that I can start recruiting interviewees as quickly as possible (thereby saving time down the line).

Acceptance criteria

• Draft initial invite email
• Draft follow-up email for interested folks
• Draft final pre-interview confirmation email (if necessary)

Definition of done

• Drafts of emails are written
• Drafts are shared with team for feedback

User story

As an NSF member of this team, I want to learn about how Github is used so I can participate in the issues as assigned.

Acceptance criteria

• NSF team members should have Github accounts established.
• NSF team members should understand how to use Github within the context of managing the board's tasks.

Definition of done

• A date for a short walk-thru of Github is chosen, and NSF is invited
• A short walk-thru is conducted!

User story

As a site administrator, I want to understand how other similar organizations are handling content so that I can make informed decisions about what appears to work well and what doesn't.

Acceptance criteria

• Begin researching comparable solutions.
• Document comparable solutions.
• Create a matrix for a comparative analysis of other science sites/resources.
• Conduct a first draft scoring of the comparative analysis.

Definition of done

• A first draft of the comparative analysis is completed.
• The draft has been circulated for comment.
• Major conclusions are communicated to the NSF team.

User story

As a team member, I need to know what the second hypothesis is so that I can start developing a prototype to test.

Option 2: Tell the story of NSF’s impact [lightbulb icon in Mural]

Possible prototype: "Impacts" type page or homepage element that explains NSF's work or what "basic research" means in a powerful way. / What NSF means to me
“Why do I care?”

Hypothesis

We believe that providing more personally relevant content will result in **more interest in learning about the NSF.gov and relevant topics. ** We will know this is true when **we see more engagement with NSF materials and click-thrus. **

Similar

We believe that showing the NSF funding provided for NSF-funded research will result in a better understanding of what funding science leads to in everyday life (and, in turn, greater public support for NSF).

We believe that explaining govt’s role in basic research for users will result in a more positive attitude toward science.

We will know this is true when we see a measured increase in public attitudes.

Acceptance criteria

• Second hypothesis is identified and agreed to; and
• Ideas around the hypothesis are sufficiently developed enough to allow us to start developing the prototype.
• Strategy is identified

Definition of done

• The first iteration of the second prototype is complete.

User story

As someone responsible for the web recruiter, I want to confirm the recruiter is set up and working properly so I can deploy it on more pages.

Functionality

• The user to clicks the tab "Help improve this site" in the lower right of the page on Science360
• Upon clicking the tab the user would be taken to the web-design-labs page of NSF https://www.nsf.gov/web-design-labs/
• Once on the https://www.nsf.gov/web-design-labs/ page the user could click the button "I'd like to chat" to complete the form

Pages/URLs to deploy on:

https://news.science360.gov/
https://science360.gov/radio/
https://science360.gov/files/

Acceptance criteria

• The web recruiter exists and is available on Science360.gov
• The form is set up and working properly
• Recruiter appears to be wired correctly

Definition of done

• Team confirms web recruiter is reviewed and is working correctly
• Recruiter is deployed on correct pages off Science360.gov domain

User story

As a user researcher, I want to begin drafting a research plan so that I can begin recruiting participants.

Acceptance criteria

• Develop shell / template for research plan
• Start a plan for remote gathering of user vision from OLPA/etc (and back-up plan for asynchronous remote
• Gather user-independent tactics for research plan
• Document tactics in the draft plan
• Distribute the plan to the team for comment
• Get alignment on user groups - keystone activity for starting recruitment; Identify groups, channels for outreach to people unfamiliar with NSF

Definition of done

• Plan has been distributed for comment to 18F team
• Plan has been distributed to NSF for comment
• Plan accepted by 18F and NSF
• Document is exists in the team folder
• Next steps have been identified

Key points:

Current site is a very content-heavy site, and NSF will need help developing a content/communications strategy — much of this discovery should be about what content types they need, and what content best serves their needs.

"CMS Discovery" is a bit of a misnomer. This discovery will inform a CMS decision, but much of the discover will be focused on what kinds of content/communication their external-facing site should include.

Broadly, this task includes helping facilitate the CMS conversations and provide advice.

User story

As a team member, I want a prototype strategy so that I understand how we will gain understandings from tests that will drive recommendations.

Acceptance criteria

• we have a research / hypothesis workflow identified;
• [ ]

Definition of done

• A strategy is documented
• [ ]
• [ ]

User story

As a someone working on the NSF project, I need to know how brand guidelines are developed and maintained so that I can incorporate them throughout the project

Acceptance criteria

• Brand assets (e.g. brand guidelines, style guide, pattern library, Sketch files, Photoshop files, button templates, etc.) are delivered to the 18F team (agency provided color palette -
  https://drive.google.com/a/gsa.gov/file/d/0B-tWFsKyyEsKc3gzX1dBa0l2Wms/view?usp=sharing)
• A primary visual design stakeholder (e.g. art director) has been identified

Definition of done

• Visual design stakeholder is engaged on branding questions
• The integrity of NSF brand guidelines, and other design material is incorporated throughout this engagement

User story

As a team member, I want to know what visual design related tasks we might need to plan for this sprint so I can assign tasks as necessary.

Acceptance criteria

• We've identified any loose ends / visual design tasks.
• [ ]
• [ ]

Definition of done

• Tasks are identified
• Backup visual designer identified
• [ ]

User story

As an NSF person interested in attending user interviews, I want to know when they are scheduled and the type of user that will be interviewed.

Acceptance criteria

• NSF attendees are added to cal invites
• Type of user identified in cal invite (science influencer, etc.)

Definition of done

• Cal invites for future interviews are distributed

User story

As an attendee during the recent user research workshop, I'd like to see a summary on major findings from the event.

Acceptance criteria

• Given I attended the workshop, I should have a summary of information derived from it.

Definition of done

• Deck / document is delivered for review!

User story

As someone interested in participating in the research, I want to learn about the research and leave my contact information.

Acceptance criteria

• There is a place I can go to learn more about the research
• I can provide contact details for follow up easily

Definition of done

• Content for page created
• Form created
• A page is designed
• ATO 👍
• Page is launched

User story

As an NSF employee, I want more information about different (& pertinent) editorial strategies so that I can understand how they might impact a CMS decision/NSF's future web presence.

Acceptance criteria

• Complete list of NSF content types/observations
• Get answers to questions related to various content types
• Compile a list of best practices for editorial planning
• Likewise, compile a list of awesome editorial practices w/r/t individual pieces/various content types
• Examine why these best practices are successful and relate them to NSF's work

Definition of done

• Document exists in team folder
• Share recommendations doc with 18F team for feedback
• Distribute to NSF
• Identify next steps!

User story

As a team member, I want a revised research report based on the findings of the workshops so that I can understand how these findings impact this project.

Acceptance criteria

• user research synthesis is complete; and
• research report is updated to include any new findings, adding in how these, coupled with what we learned during the workshop activities about business goals and hypotheses, inform our hypothesis generation process

Definition of done

• Research report is revised and delivered to NSF.
• Research report is uploaded to the wiki.

User story

As a user researcher, I want the correct NSF people invited to user interviews so they can observe the interviews and make recommendations accordingly.

Acceptance criteria

• Identify correct ppl from NSF to attend user interviews
• Send invitations to upcoming interviews

Definition of done

• NSF ppl are identified and invited

User story

As a team member, I want a schedule of more coworking slots so that I can work in tandem with the rest of the team on a more regular basis.

Acceptance criteria

• Acceptable time slots are identified.
• [ ]
• [ ]

Definition of done

• Calendar invitations are distributed and accepted.
• [ ]
• [ ]