Personal Reflection On Software Engineering Skills For Software Development

1246 Words 5 Pages
Name
Instructor
Course
Date
Personal Reflection/ Project Response Essay
Recently, I attended a software engineering development course. Indeed, the course was valuable to imparting the desired software engineering skills for aspiring software engineers. Today, software systems continue to evolve in terms of features and supportive tools. Difficulties in managing software development can be attributed to the challenges inherent to planning activities as software features evolve over time. Previously, software engineers would utilize on frameworks and tools to plan tasks methodically. It is widely recognized that software features have dependencies, but still, the process of software development is largely based on “learning by practice (Domann
…show more content…
The team of developers implemented the requirements of the project through the time limits defined within the sprint tasks. The project’s situation was evaluated after completing every sprint task to provide informed judgment on when to refine the product backlog (Jullig 7). Most importantly, the learners appreciated the division of each sprint into Daily Scrums where previous undertakings would be discussed (Domann et al. 929). In these scrums, the team members would also highlight the problems encountered as well as the applicable solutions. This exercise exposed leaners to effective communication skills through team engagement. As a result, work transparency was nurtured. In addition, it was possible to undertake informed rhythmic evaluations of the software development project based on the frequency of the Group …show more content…
This was an added advantage to the software development cycle. A limitation of the Scrum model is the difficulty in sub-dividing mutually-dependent tasks. Another limitation observed in the model is that the hierarchy demanded a lot of synchronization and communication (Domann et al. 929). Further, Scrum assumes that the team members work synchronously within similar working hours, and this may not necessarily be the case (Domann et al. 930). However, Scrum remains for small groups of teams working on a specific project. In addition, the framework addresses the probability of changing project requirements, which is an added advantage (Domann et al. 930).
This course introduced learners to acceptable coding standards, which was the foundation to work as a team. If the team had followed the required coding standards, then there would have been no need to waste time on merging codes from different team developers. Based on the outcomes of the project, most of the learners can now distinguish an excellent code from a poor one. Simply stated, WTFS/min is the only valid measure of code

Related Documents