Personnel Unit Groupings - nordquip/sousms GitHub Wiki

Team Meeting Times

See http://cs.sou.edu/~nordquip/NordquistSchedule.htm

These are the teams I think we might need.

The number in parentheses after the group name indicates an estimated group member count. This estimation is not hard and fast by any means. The number in parentheses after a person's name indicates levels of preference for each job, with "1" being highly preferred.

If you think we need additional groups, add your ideas to the bottom of this page.

Data Feed Capture (2)

Responsible for receiving and storing ticker data.

  • Bret Leduc (1)
  • shaunwolff (1)

Database Administration (4)

Standard Database Administration

  • Martin DeWitt (1)

  • Scott Williams williams3(1)

  • kuhlk (1)

  • Emily Parrish(1)

  • Josh Carroll (1)

  • Nick Patterson (2)

  • shaunwolff (3)

  • Morucker (4)

Overall Look & Feel, Graphics (4)

Responsible for page layouts, artwork, and user interface standards.

  • JesseAllred (1)

  • TreaganP (1)

  • dadolym (1)

  • Tamarra Phillips phillipta (1)

  • brwhale (2)

  • daveer (2)

  • mikeRupp (2)

  • jrkarmy(4)

  • Jian Rossi (5)

  • Morucker (3) *wernermichael(3)

User Accounts and UI (6)

Manages user account creation, modification, and deletion, as well as user data storage.

  • lpeery (1)

  • JesseParks (1)

  • robinsoc1 (1)

  • JoeCaudill (1)

  • Justin Bezuhly (1)

  • wernermichael (1)

  • kuhlk (2)

  • dightonb(2)

  • Nickolaus D. S. (3)

  • Emily Parrish(3)

  • Martin DeWitt (3)

  • Scott Williams: Williams3 (3)

Trade Engine and UI (6)

_Processes user commands, and performs trades. May involve coding a simple buy/sell scripting language for users to take advantage of._ *** Meets Mondays at 12:30 pm in the CS Lab.

  • jrkarmy(1)
  • dightonb(1)
  • Jeremy Barnes (1)
  • AnthonyKaiserman (1)
  • millerj3 (scriptar) (1) - mashups
  • Nickolaus D. S.(2)
  • benjaminharris1 (1)
  • Ryan5732(2)
  • Nick Patterson (3)
  • lpeery(2)
  • JesseParks(2)
  • robinsoc (2)
  • JoeCaudill (2)
  • wernermichael(2)

Mobile Development (4)

In charge of developing a mobile app that tethers to the trade system.

  • Sean Ewing (1)
  • Nick Patterson (1)
  • Cody Shilts (1)
  • Jian Rossi (1)
  • Jeremy Barnes (3)
  • AnthonyKaiserman (4)

Testing & Quality Assurance (6-8)

Testing

  • Ghenaj1 (1)
  • brwhale (1)
  • daveer (1)
  • mikeRupp (1)
  • MIKEPArA (1)
  • morucker(1)
  • blakelyh (2)
  • jeremy-french (2)
  • raines-terak (1)
  • carlsonjohn (2)
  • hawkins-brandon (2)
  • blykins (2)
  • dadolym (2)
  • jrkarmy(2)
  • dightonb (3)
  • Jian Rossi (4)
  • John Rekow (3)
  • Emily Parrish(2)

Build / Revision Management (2)

Manages the build process, assists with module compatibility.

  • Ryan5732 (1)

  • Bret Leduc (3)

  • John Rekow (4)

  • JesseAllred (3)

Other Major Application Functionality (4)

Sneaky ninjas that fix & write random stuff.

  • brwhale (3)
  • daveer (3)
  • mikeRupp (3)
  • Jeremy Barnes (4)
  • AnthonyKaiserman (3)
  • raines-terak (3)
  • blakelyh (3)

Project Leads / Project Management / Special Ops (4)

Project Management

  • jeremy-french (1)

  • Nickolaus D. S. (1)

  • Martin DeWitt (2)

  • Scott Williams williams3(2)

  • shaunwolff (2)

  • Tamarra Phillips phillipta (2)

  • Jian Rossi (3)

  • Morucker (2)

Website Development (2+) -- Add to overall look and feel group

HTML code, page templates & layouts

  • Justin Bezuhly (2)

  • John Rekow (1)

  • Cody Shilts (2)

  • Jian Rossi (2)

  • Sean Ewing (2)

  • JesseAllred (2)

  • Bret Leduc (2)

  • Melissa Dadoly (3)

  • Josh Carroll (2)

  • Jeremy Barnes (2)

  • AnthonyKaiserman (2)

##Security (4) Security

  • blakelyh (1)

  • Judy Weaver (1)

  • blykins (1)

  • carlsonjohn (1)

  • hawkins brandon (1)

  • raines-terak (2)

  • jrkarmy(3)

  • Justin Bezuhly (2)

  • John Rekow (2)

New Group Suggestions, Random Comments

New Group Suggestion: What about a documentation guy/gal? Yea, everybody should be writing documentation for their own section of the project, but still, seems we would benefit from having a single person in charge of combining and editing the documentation into a single uniform resource. This person would also be responsible for writing important documentation that does not specifically belong to any particular group. Thoughts?

The web team will take this task on.