Teamwork in Software development can smooth, if you keep the overview of your currently ongoing tasks. A workflow derived from scrum is the development process described below. This Workflow reduces confusion and brings focus to your teammembers
Creating Big containers first: Create milestones, then add Tasks using Tickets
- Peparation milestones
- Create all currently planned milestones
Fixed Milestones: Ideas, Backlog
- Create all currently planned milestones
- Development milestones
- Weekly milestones: for small tasks
- Project milestones: for Tasks that contain more subtasks
- Deployment
- Using Ticket Lable “for Beta”
- Using Ticket Lable “for Live”
Milestone Workflow: How tickets are moving
- Ideasmilestone: All Tasks that are “Todo, but not yet properly described”
- Ideas: Can Create new Tickets: Anyone
- Ideas: Can Manage / Change Tickets: Project Management
- Backlogmilestone: – Created by
- All Tasks properly specified.
- Engineers should add their time estimates.
- Maximum Ticket Size is 2 – 8 hrs
- Backlog: Can Create new Tickets: Anyone
- Backlog: Can Manage / Change Tickets: Project Management
- Deploymentmilestones
- Backlog: Tickets moved from Backlog to Deployment: Project Management. Priorities set by Management
- Backlog: Update Tickets: Engineers
- Completed with “for Beta” Lable”
- Releaseworkflow
- Tickets marked with “for Beta” are tested by Developer, Client and Testers.
- After Feedback, marked with “for Live” and then deployed to livesystem
Create a new Filter for Tasks in Active Collab 3
Important Active Collab Queries:
Your Tasks in overview:
http://pm.mydomain.at/public/index.php?path_info=
Your “Yumpu.com” Tasks, only for your user
http://pm.mydomain.at/public/index.php?path_info=projects%2Fyumpucom%2Fuser-tasks
Your “YouBuy.com” Tasks, only for your user
http://pm.mydomain.at/public/index.php?path_info=projects%2Fyoubuycom%2Fuser-tasks
Create a Custom Search for Tasks:
http://pm.mydomain.at/public/index.php?path_info=&homescreen_tab_id=3