Welcome to Taskman!¶
Think big, act small, fail fast; learn rapidly¶
This is the place where EEA manages most of its IT-projects. It is here where the big ideas are realised one task at the time.
How to use it?¶
Working with tickets (Flow)
Requests for new projects or any other questions regarding Taskman please contact Antonio De Marinis at EEA
How to add new member to a project and what role to give: See instructions
Agile boards across all projects¶
Quick links to Agile boards showing the current flow of work on different teams across all projects (you should login in order to see all your tickets)
- Personal Agile Board - assigned to me
- Personal Agile Board - reported by me
- Workload Bilbomatica
- Workload EauDeWeb
- Workload Eworx
- Workload Fastdigitech
- Workload IDM2
- Workload IDM3
- Workload Tracasa
What project methodology does EEA use for IT-projects?¶
The core principles of Agile project management are:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
The core principles of Kanban:
- Visualise Work By creating a visual model of your work and workflow, you can observe the flow of work moving through your Kanban system. Making the work visible—along with blockers, bottlenecks and queues—instantly leads to increased communication and collaboration.
- Limit Work in Process (WIP) By limiting how much unfinished work is in process, you can reduce the time it takes an item to travel through the Kanban system. You can also avoid problems caused by task switching and reduce the need to constantly re-prioritize items.
- Focus on Flow By using work-in-process (WIP) limits and developing team-driven policies, you can optimize your Kanban system to improve the smooth flow of work, collect metrics to analyse flow, and even get leading indicators of future problems by analysing the flow of work.
- Make policies explicit Until the mechanism of a process is made explicit, it is often hard or impossible to hold a discussion about improving it. Without an explicit understanding of how things work and how work is actually done, any discussion of problems tends to be emotional, anecdotal and subjective. With an explicit understanding it is possible to move to a more rational, empirical, objective discussion of issues.
- Implement feedback loops Organisations that have not implemented the second level of feedback - the operations review - generally do not see process improvements beyond a localised team level.
- Continuous Improvement Once your Kanban system is in place, it becomes the cornerstone for a culture of continuous improvement. Teams measure their effectiveness by tracking flow, quality, throughput, lead times and more. Experiments and analysis can change the system to improve the team’s effectiveness.
Taskman (this site) main features¶
Taskman is based on the flexible Redmine software. Read more about Redmine features
Check the new Agile Boards in CORDA wiki
Three Agile boards have been created for planned tasks, personal planned tasks and for the Helpdesk area. Check it in https://taskman.eionet.europa.eu/projects/corda/wiki