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?

Flow process - How to get your tickets flowing

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)

What project methodology does EEA use for IT-projects?

At EEA we use the Agile/Lean-based methodologies for managing software development. We use a mix of Scrum, Kanban and Lean which are all lightweight methods.

The core principles of Agile project management are:

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

The core principles of Kanban:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.

Read more on Agile
Read more on Lean
Read more on Scrum
Read more on Kanban

Taskman (this site) main features

Taskman is based on the flexible Redmine software. Read more about Redmine features

Latest news

Reportnet platform: Reportnet project is now private
Added by Antonio De Marinis over 1 year ago

CORDA: Check the new Agile Boards in CORDA wiki (1 comment)
Three Agile boards have been created for planned tasks, personal planned tasks and for the Helpdesk area. Check it in
Added by Iñaki Diaz de Cerio almost 2 years ago

CORDA: Interesting links
Added by Iñaki Diaz de Cerio almost 2 years ago

Reportnet platform: Changes to ticket status: Feedback split into two
We have two kinds of feedback now: "Needs clarifications" and "Acceptance/Demo".
Added by Søren Roug about 3 years ago

Reportnet platform: Jenkins being migrated to CloudVPS
Jenkins being migrated to CloudVPS - expect build failures for a while
Added by Søren Roug about 3 years ago

View all news