CS-250 Portfolio

How do I interpret user needs and implement them into a program? How does creating “user stories” help with this?

Interpreting and implementing user needs into a program involves understanding what the end user wants to achieve with the software. This understanding typically comes from direct user communication or detailed market research. Once we know what the users want, we can incorporate these needs into the software design and development process. Creating "user stories" is a crucial part of this process. A user story is a tool used in Agile development that describes a software feature from an end-user perspective. Each user story describes the type of user, what they want, and why, helping us ensure that we are building software that meets the users' needs and provides value. User stories focus on the user, encouraging the development team to build software from the user's perspective.

How do I approach developing programs? What agile processes do I hope to incorporate into my future development work?

My approach to developing programs starts with understanding the project's scope and requirements. I then break down the project into smaller, manageable tasks. I use an iterative development process, which allows for regular review and refinement of the software as it is being built. Using Agile development methodology promotes flexibility, continuous improvement, and high-quality software. In the future, I hope to incorporate more Agile processes into my work, such as Scrum for team collaboration and task management, Test-Driven Development (TDD) for ensuring code quality, and continuous integration/continuous deployment (CI/CD) for automating the stages of software delivery.

What does it mean to be a good team member in software development?

Being a good team member in software development means more than just writing code; it involves actively collaborating with others, sharing knowledge, and supporting each other in achieving the project's goals. A good team member communicates effectively, is reliable, and respects the work of their peers. They are open to feedback and willing to learn from others, recognizing that everyone on the team has valuable skills and insights to offer. In Agile development, being a good team member also means embracing the Agile principles of iterative development, customer collaboration, and responding to change while working towards delivering a high-quality software product.