Repository navigation
Project Plan
Responsible for overall project management, communication with the customer (Cybernetica), and the development of the DSL and parser in Rust.
Oversees the technical aspects of the project, designs the architecture, and leads the development of layouting. Responsible for code quality and architectural decisions.
Ensures the layouting output is correctly converted to BPMN diagrams and writes test cases to verify correctness. He also ensures the product meets performance and usability requirements.
Responsible for maintaining and organizing the Wiki, including meeting notes, requirements and documentation. Additionally responsible for the layouting process.
- Platform: Discord
- Frequency: Every other day stand-ups and weekly in-depth meetings
- Platform: Email, jitsi meet and Signal
- Frequency: Twice a week
This work process outlines how we effectively collaborate with the client, ensuring their understanding of the project goals. To visualize our work, we use tools like draw.io to create diagrams that represent the BPMN parser and the DSL architecture. Sample BPMN diagrams are regularly shared to demonstrate the capabilities of the tool.
We initiate the project by discussing requirements with the client, which are then formalized in documentation and validated during meetings. Regular reviews help maintain transparency. To secure acceptance from the client, we deliver documentation that describes the functionality and BPMN 2.0 compliance of the tool, along with sample outputs for evaluation.
- Task Assignment: Jens allocates tasks based on expertise. Albert and Morris focus on the layouting process, Andrei ensures that the layout converts correctly into BPMN diagrams.
- Development: The team follows best practices for implementation, testing, and documentation. Snapshot and integration tests are run to validate the correctness of each component.
- Testing: Andrei is responsible for validating that all outputs meet the required BPMN standards.
-
Completion Criteria: A task is considered “DONE” when:
- It meets the agreed acceptance criteria.
- Passes all tests.
- Is peer-reviewed.
- Is documented appropriately.
We gather feedback through regular meetings, email updates, live demonstrations, and issue-tracking systems to ensure transparency. We consider a deliverable ready for customer review once it has been peer-reviewed, passes all tests, is documented, and demonstrates compliance with BPMN 2.0 standards. Regular feedback loops and discussions ensure that client expectations are met before formal delivery.
23.09 - 4h
25.09 - 5h
27.09 - 3h
02.10 - 1h
07.10 - 1h
09.10 - 2h
15.10 - 4h
22.10 - 4h
29.10 - 4h
05.10 - 4h
12.10 - 4h
19.10 - 4h
26.10 - 4h
Total: 44 hours.