I want to share with you a series of formats that I have been building and adapting to my needs as a trainer in software developmentThey helped me a lot and maybe they can help you too.Since 2014 I have been dedicated to providing technical and technological training around software development, previously I worked as a development engineer in a software factory in which I had to go through the different phases of software life cycle (Problem Statement, Analysis, Design, Implementation, Test – Debug, Delivery) I started as a developer but also carried out requirements gathering and construction tasks, testing, integration, installation and other activities that gave me an overview of this lifecycle directly in a business environment, interacting from different functions and using fundamental formats and tools for each step.
When I changed my role from instructor profile, I had the challenge of transmitting the knowledge acquired in that real world but already in an educational context where students must learn from scratch to build fully functional software.
As part of this process, aspects such as the use of methodologies, design patterns, programming languages, quality, good practices and other elements are addressed.
As mentioned, the idea is to train software development from scratchfrom the most basic concepts and going through each of the stages of the software life cycle, applying the necessary concepts until arriving at the delivery of a product, it was at this point that I had as a reference the way each process is carried out in my previous work, so I've designed some formats that will make it easier to manage each step based on the needs of my training groups and project characteristics.
Documentation is perhaps one of the most boring steps for many of us, especially those who like to be in the action building things through programming, however this is a very important part that helps manage the system by facilitating traceability in different stages.
Obviously these formats were not built just from my perspective and experience, for that I relied on both traditional and agile methodologies, so some formats have elements or diagrams in their content. UML what is more characteristic ICONIX any OR and others are better adapted to work with scrum where it is most common to use user stories.
As a result of all this, more than 10 formats were created, from problem statement, requirements survey, project document, tests, delivery, installation, user manuals, among others that, as I mentioned at the beginning, facilitate project documentation. .
Inside this link from my github repository You can download the formats, I share them completely free for you to use if you need to.
Likewise, if you want to know more about the software lifecycle, I will share with you this video what might interest you or this playlist on project management.
Finally, I invite you to visit codejavu.blogspot.com, to visit my channel Cristian Henao and that they are very aware of the new sequels
It may also interest you.
Is there anything you want to add or comment about this entry? feel free to do….and if you liked it, I invite you to share it y Subscribe by clicking on the “Join this site” button to hear more posts like this one 😉