Welcome to Taskman¶
Think big, act small, fail fast; learn rapidly¶
Taskman is a web application that facilitates Agile project management for EEA and Eionet projects.
Taskman is mostly used for software development but the principles are generic and therefore Taskman suits any project that needs a flexible project management web application.
On Taskman we aim to host all the EEA projects which have a software component.
How to use it/Would you like to have your project here?¶
If you have any questions regarding Taskman (e.g. you need a new project) or how to use it in combination with 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
Latest newsView all news
- BISE 2015 countries (30 Jan 2015 13:25)
CORDA (08 Jan 2015 17:08)
Copernicus Reference Data Access node (CORDA)
riparian zones (12 Dec 2014 09:46)
Quality assessment of riparian zones. A riparian zone or riparian area is the interface between land and a river or stream.
- Urban Adaptation Report 2016 (24 Oct 2014 08:58)
Mitigation actions, GIO land HRL grassland (07 Oct 2014 18:03)
Framework Service Contract EEA/SES/12/003/Lot3 (Specific Contract No. 3436/B2014/RO-GIO/EEA.55844)