Versions Compared

Old Version 24

changes.mady.by.user user-c2913

Saved on

compared with

New Version 25

changes.mady.by.user user-c2913

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Stand-ups occur daily at 9:15 AM EST. (877) 847-0013,8518026#
  • Sprint planning meetings occur as part of the EED2 EED-2 SAFe efforts. Typically on the first day of each sprint.
  • Retrospectives typically take place after the first standup following sprint demos.
  • Developers should use EOSDIS Slack accounts for chat and join the #edsc-dev channel for team communication. See your team lead for an invitation to the channel.

...

We have periodic retrospectives, but more importantly, we try to maintain direct communication and adjust for problems as they arise.

...

  • Story: A user-visible requirement which ought to be achievable by a single developer in a couple of days. These are captured in a consistent format, "As a [user type] user, I should <feature description> so that <value to user>". For instance, "As a user, I should be able to log in so that I may access information saved with my account."
  • Epic: Groups similar stories into less granular pieces of functionality.
  • Bug: A user-visible implementation problem which that causes clearly broken behavior. Examples: a button that does not work, severely degraded performance, a security hole.
  • Improvement: A user-visible implementation problem whichthat, while not clearly broken, poses usability challenges. These are almost exclusively reserved for interface design issues , since we often have a backlog of features which have been implemented but need UI polish. Improvements are optional and we could ship without them. Examples: a button which that looks out of place, text that needs styling.
  • Task: Necessary work that is not user-visible. Examples: Setting up a CI environment, research to make a recommendation, documentation.
  • New Feature: Not used.

...