-
Notifications
You must be signed in to change notification settings - Fork 0
Iteration_1
lauragrace949 edited this page Jul 9, 2019
·
42 revisions
- Iteration Goals
- Team Roles
- Task Management
- Documentation
- Meeting Summaries
- Retrospective
- Process, Methods & Tools
- Next Iteration Planning
Iteration Goals[ex1]
The goal of the first design iteration was to create and document the creation of a prototype focus group system. This system would compose of both a website for company-side use and an android application for focus group participant use. A summary of the iteration goals is provided below:
Our design process included:
- The roles of each of our team members;
- Our initial project requirements, including the scope of the project use cases, user stories and functional and non-functional requirements;
- An overview of our design, including system flow charts and paper prototypes, user interface
- Beginning a comprehensive and detailed wiki outlining the project
- Focus on main functions to begin designing
- A functional server
- A login, welcome, preferences and user profile screen
- App features that allow users to communicate with each other and share events
Team Roles[ex1]
Name | Degree | 1st Role | 2nd Role |
---|---|---|---|
Eliza Bennett | Software Engineering // Business Management | Manager | Programmer |
Leon Karstens | Software Engineering | Programmer | Designer |
Nikita Lisovetin | Software Engineering | Programmer | UI documentation (concept description) |
Laura Davis | Electrical Engineering // Bachelor of Arts | Programmer | Technical documentation |
Brae Webb | Computer Science (Honours) | Lead Programmer | Quality control |
Daisy | Human Resource | Related Documentation in wiki(Besides Technical's knowledge) | Business Plan |
Leo | Software Engineering | Programmer | User interface |
[Trello]
A team Trello board was created for effective time and task management. Click here to view the board.
Total Estimation[ex1]
Relevant docs. diagrams
- Our team Analysis APP’s users.
- Make sure user’s requirements and divide different roles of users.
- Make sure personal role in team
- Divide personal responsibility
- Begin to build basic structure
- Eliza: View function
- Laura: Friend Verification
- Brae: Filter based on param
- Nikita: UI design,database design
- Leon: UI design
- Eliza: Mobile login/signup Screens
- Laura: User profile
- Nikita: Set up AVD, Add a new event
- Brae:set up remote server, Fixing Eliza
- Leon: Prototype
- Daisy:User documentation
- Leo:Database PHP
- Eliza: Mobile login/signup Screens,Fixing Brae
- Laura: User profile
- Nikita: Set up AVD, Add a new event
- Brae:Fixing Eliza, set up remote Server
- Leon: Prototype
- Daisy:Related doc.
- Leo:Database PHP
- Our group discuss the specific task about wiki, and added new task this week.
- Brae pushed some breaking changes to master, so everyone should pull before they get to start.
Retrospective[ex1]
- After first week and second, we understand our team and team member more clear. And we found some problem about team work. 01/07/19
Keep | Problems | Try |
---|---|---|
Division of jobs based on everyone skill and technology, it makes progress faster and efficient. We help each other. | Different language probably make team communication not easy. | We are trying to communicate actively. |
Next Iteration Planning[ex1]
- Link to Iter2 page