Welcome to Taskman

Think big, act small, fail fast; learn rapidly

How to use it?

First, get to know the official User Guide.

Our work practices: working with tickets (kanban/lean)

Requests for new projects or any other questions about Agile/Scrum/Kanban/Lean software development please contact Antonio De Marinis at EEA

* What is Agile?

Agile project management is an iterative method of determining requirements for engineering and information technology development projects in a highly flexible and interactive manner. Lean principles originating from the Toyota Production System are also widespread within the Agile methodologies.

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. Visualize 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 Organizations that have not implemented the second level of feedback - the operations review - generally do not see process improvements beyond a localized 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: 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 17 days ago

Software development: Feedback status is now more clear
We have two kinds of feedback now: "needs clarifications" and "Acceotance/Demo".
Added by Antonio De Marinis 18 days ago

Networking tools: Reorganising the Networking Tools project
PBE, VL and Groupware tickets were merged into "Networking Tools"
Added by Alex Eftimie 19 days ago

E-PRTR: Jenkins being migrated to CloudVPS
Jenkins being migrated to CloudVPS - expect build failures for a while
Added by Søren Roug about 1 month ago

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

View all news

Latest projects

  • IDM2 Web Systems (2015-05-12 14:23)

    All development and support for systems managed by IDM2 are under this project.

    Delivery Teams within IDM2:

    • EDW A-Team: This team is managing the EEA website plus other applications. Delivery Team Manager: Antonio De Marinis

    Backlog > Queue > Work in progress > Acceptance/Demo...

  • CDDA data model and INSPIRE (2015-05-11 21:25)

    The project aims to develop the complete data model of the Common Database on Designated Areas (CDDA) data flow in line with the relevant INSPIRE data specification on Protected sites and others, including the necessary elements for the INSPIRE service oriented reporting. The project will deliver redesigned conceptual CDDA UML data model, XML schemas and data sample for the CDDA reporting data flow....

  • E-PRTR dataflow (2015-02-06 10:06)

    Work related to the integration of the Large Combustion Plants reporting into the E-PRTR dataflow. This implies the updating of the XML Schema, QA/QC routines, harvesting routines, E-PRTR data model and other related issues. Documents are shared via <project-library-link>. In this taskman project we manage sprint iterations and tasks workflow....

  • CORDA (2015-01-08 17:08)

    Copernicus Reference Data Access node (CORDA)

  • riparian zones (2014-12-12 09:46)

    Quality assessment of riparian zones. A riparian zone or riparian area is the interface between land and a river or stream.