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
How to add new member to a project and what role to give: See instructions
* 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.
IDM3-Team (2016-01-27 16:02)
Projects managed under IDM3. Spatial data infrastructure.
Action Plan 2016 (2016-01-26 09:30)
The aim of this project is to support coordination of ETC-ACM activities in the context of the Action Plan 2016.
ETC-ACM (2016-01-26 08:45)
The aim of this project is to support coordination of ETC-ACM activities in the context of the Action Plans and in particular:
1. Manage the ETC and ensure that the deliveries and contribution of the ETC are in line with Action Plans.
2. Review ETC capacities and expertise in connection with objectives and requirements of the annual management plan....
Climate ADAPT Content Maintenance (2016-01-22 16:04)
EIONET in situ task force - In situ database review (2015-12-08 11:11)
The main objective of this service contract is to evaluate if the current Copernicus in situ database, developed by the GISC1 project, is sufficiently capable of a) providing a suitable overview of the Copernicus in situ component, b) capturing information (metadata) about all Copernicus services’in situ data requirements and relevant data sources in an appropriate and efficient manner, and c) providing the necessary basis for in situ data gap analyses....