-
Notifications
You must be signed in to change notification settings - Fork 4
Home
Welcome to the Backlog wiki!
-
Quality Assurance engineers want to create test plans that ensure product quality, and have high-quality code to test.
-
Project Managers want a process that is easy to plan, execute, and track.
-
Product Managers want features implemented quickly, with no bugs.
-
Services and Support personnel want to know exactly what is in all product releases, and have a reliable means to satisfy customer requests for bug fixes and enhancements.
-
Customers want all of their feature requests and bug-fixes done quickly.
-
Executives, Program Managers, and PMO personnel want to know exactly what is happening, and what is planned to happen.
-
Team satisfaction and productivity are maximized when effort spent on non-deliverable items (e.g., internal documentation) is kept to a minimum.
-
Maximizing quality at each stage minimizes re-work at following stages, and maximizes product quality seen by customers.
-
Responsiveness is best achieved by fulfilling customer requests quickly.
-
Project status and plans should be visible to everyone who has an interest in them.
- Natan Braslavskiy
- Dima Movchan
- Anton Litovka
- Danil Iskusnov
- Intel Jerusalem
- Collaborating, supporting and respecting one another.
- Communicating openly, honestly and frequently.
- Developing a highly motivated, valued and diverse workforce.
We divided the project into the stories, and each story into the tasks. For each story we have one teammate, that responsible for this story. Also the stories and tasks have priority, in which we have to perform them. So we making little steps to our goal with communication and helping to each other.
- We have a meetings at least two times per week.
- We have a briefing each day for 15 mins, where each team member reports how is going his tasks.
- Using cellphones, skype, chats, and email.
Scrum:
- Sprint managemant (logic part).
- Liniar graph and columnar graph.
- Database - contain information about the sprint, programmers and etc.
- GUI - Display the data from the DB in a convenient form.
- Database will be managed via ADO.NET, in which we going to save data about the sprint.
- Logic part is responsible for the connection between DB and external view of the program (GUI), for math calculations and for sprint managing. Will be implemented in C#.
- GUI will display information about sprint, for example: a stories, tasks, working dates and etc. Also will display graphic of the progres. Also will be implemented in C#.
- Installed all need software (like Visual Studio).
- Prepared ERD, figure entities to match to external view of the program.
- Created an example of DB, GUI, writed some code in Visual studio (C#).
Our team faced the problem of synchronization code, we created a database and writed some code that connect to DB and transfer data to Gui, as result we discovered that code is not appropriate, and we have to do a lot of changes.