DFG Stock & Financial System Development

This assignment presents a comprehensive sprint retrospective report for the development of a stock and financial management system for DFG. It details the progress made across eight sprints, outlining specific goals, achievements, encountered challenges, and proposed solutions for each iteration. The report covers aspects like cross-platform compatibility, back-end efficiency, remote accessibility, integration capabilities, data format consistency, and cloud deployment. It highlights the Agile methodology's iterative approach, emphasizing continuous improvement and adaptation throughout the development process.

Project Management
Stock and Financial Management System for DFG
Sprint Retrospective
This is a meeting that the scrum master facilitates at the end of the project execution where the
events of the project are discussed and what can be done for the future to achieve grater project
success. The sprint review should end with a documentation of the project, including the team
experiences and areas where improvements can be made. This paper includes the sprint
retrospective for the development of a stock and financial system for the DFA. The retrospective
looks at how the system is being built.
Sprint 1: I need a software system that runs on all major platforms and browsers efficiently; it runs
fast, loads quickly does not slow down

The team s suitable languages to ensure cross platform compatibility of the DFG stock and financial
system with a visual description of the software developed and all platforms listed and what was
required to achieve that. On testing (the system just had static placeholder frames), performance
was poor on Safari and Opera, especially on mobile where the placeholders were smudged and
loaded slowly. Improvements would be to have binary executable files for every platform (for
installations) and use more Python libraries. Testing strategy to be improved and performance on
Safari and Opera improved. Actions to take include external libraries to enhance performance and
use of graceful degradation to enhance performance on different browsers
Sprint ID 2: I need a back-end that runs efficiently and support all user requirements

The team used open source database language and created a database with a few tables and
elements and tested it. Different platforms envisaged and database tested with a back end user
interface and code extended for Linux compiling. Improvements are due for user interface and
Jquery and PHP for database access at interfaces. Loading time on slow web connections. Actions
are to refine code and use HCI principles to design interface and improve single code base
Sprint ID 3: I need an application that can be accessed remotely from any location with a web
access

Sprint ID 4: I need an application system that can be integrated with other systems easily

Sprint ID 5: I need a system that can be expanded and be used in different geographic areas and
stores and work with other sub systems
Data access bug and clustering architecture problems experienced during testing. The actions to
solve included using micro services design for improved testing because the application was
developed in much bigger chunks, making testing a challenge
Sprint ID 6: I need a system in which data is transferred and stored in a similar format

Challenges with data format when being extracted using other systems; action to solve include
changing to SQLite data format and using Python external libraries to enhance automated functions
performance
Sprint ID 7: I need a complete functional software system with web access from a cloud platform

Entire system compiled and tested under different loads (requests); payment processor slowing and
action to solve is using open source cart management systems of better performance than what was
designed in house
Sprint ID 8: I need all my requirements well captured and implemented

Prototype tested in real conditions and customer asked to test system under different conditions. The
client asked about security of information and data; team resolved to implement default encryption
and provide support for this. Test successful; documentation made for support with new patches
scheduled while the system is running to take care of client concerns.