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.
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:
- 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.
- 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 Organizations that have not implemented the second level of feedback - the operations review - generally do not see process improvements beyond a localized 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
Taskman upgraded: faster and new features available
Taskman system Redmine has been upgrade to latest version and brought lot of bug fixes and some new features.
Who can see private tickets and private notes
It is now possible for all project members to see private tickets. Anonymous and non-members of a project will not see the private issues and notes.
CCA (Plone) (2015-06-23 16:57)
Migrate Climate Change Adaptation Portal to Plone
WISE SoE Monitoring Stations and INSPIRE (2015-06-15 17:33)
This project aims to evaluate the data models of monitoring stations in both reporting data flows (WFD, WISE SoE) and provide the mapping rules for transformation of monitoring stations in WISE SoE into relevant INSPIRE conformant spatial
data sets. It will provide a common data model covering the WISE SoE, WFD and INSPIRE requirements....
IDM2 Web Systems (2015-05-12 14:23)
All development and support for systems managed by IDM2 are under this project.
Our workflow policies: Working with tickets in Taskman
Delivery Teams within IDM2:
- IDM2 Team: This team is composed of only IDM2 staff and work that is not meant for the other dev-teams. Delivery Team Manager: Søren Roug, Delivery Managers: Antonio De Marinis, Christian Prosperini, Mauro Michielon, Marie Jaegly, Michael Noren...
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....