Page History

Today we had a meeting to identify and prioritize issues that keeps us from working at optimal efficiency.
We came up with the following:

Scrum process related issues:

1. We need well defined user stories and scenarios for a couple of reasons:
   1. To speed up the poker planning phase we have on the start of each sprint
   2. For communication to users, stakeholder and the developers
   3. To get more insight on the related tasks
2. We need well defined tasks for the developers in JIRA. These tasks should have good descriptions, screen mock-ups when available and when it involves error issues then we also need the steps to reproduce the error.

...

• User stories should be available on wiki under sprint page
• Tasks must be defined in JIRA
• Tasks need a reference to the wiki user story
• User stories should have references to the JIRA issues
• User stories and tasks should have good descriptions and preferably examples and applications
• Optionally user stories should have use case scenario's ie. Steps to take to reach your goal

General development issues:

1. We need a well defined "definition of done" document which every developer must use as a check list to improve code quality.

...

As a team we need to define code design rules for ReSharper or StyleCode.
We should use these tools to automate the task of checking code design rule violations.

Other actions...?

DeltaShell framework issues:

1. We need an oversight overview or visual map of the high level architecture and the framework(s) and their dependencies being used. This can help developers to see the bigger picture and to quickly identify the context we work in.
2. We need to split up the solution in smaller parts so that they can grow and evolve independently. This means grouping or even merge sub projects.
   1. This encourages a better loosely coupled architecture
   2. Smaller parts should result in quicker builds
3. It's not always clear what a unit test data access or integration test is. Furthermore some tests are slow and some result in "out-of-memory" exceptions.
4. We should simplify existing complex dependent classes when possible. Candidates are:
   1. FunctionBindingList
   2. GuiCommandHandler
   3. (Project)TreeView and their node presenters
   4. ModelBase
   5. Function model API
       

...