Alladdin
Work in progress
Site en construction
الموقع قيد الإنشاء
Work in progress
Site en construction
الموقع قيد الإنشاء
A sprint is a short, fixed period, usually one to four weeks, in which the team commits to a set of tasks. In Alladdin you keep the backlog of everything still to do, pull the most important items into the sprint and follow them to done.
List everything that needs doing: features, fixes, client requests. Put the most important at the top.
Set the dates and a goal in one sentence. Drag the top items from the backlog into the sprint, as much as the team can finish.
Each person moves their tasks across the board and logs the hours spent.
At the end, check what was done against the goal. Move unfinished tasks to the next sprint or back to the backlog.
"Online booking live for the riad's website" says more than a list of twelve tasks. Write the goal when you plan, and use it to decide what gets in and what waits.
Estimates
Give each task an estimate in hours so the sprint holds what the team can finish.
Owners and dates
Every task in the sprint has someone responsible for it.
Compare the hours estimated with the hours logged, see what was left over and note what to change. The next plan is better because it starts from real figures.
Time logged per task
Timers and timesheets show where the sprint's hours went.
Notes for next time
Keep the team's review in the project discussion.
A fixed period, usually one to four weeks, in which a team commits to finishing a chosen set of tasks. It gives the work a steady rhythm and a regular moment to review.
No. Sprints suit teams that deliver in iterations, such as software or marketing teams. Many projects run fine on a board or a timeline alone.
At the end of the sprint you move them to the next sprint or back to the backlog.
Yes. Estimate tasks in hours, then compare with the hours actually logged.
List your backlog, pick the top items and give the sprint a goal.