Hi, my name is Nathan and I am in my Junior year here at WSU studying CS. This blog page will be used to discuss and research the topics that will relate to Software Development.
From the blog CS@Worcester – function & form by Nathan Bui and used with permission of the author. All other rights reserved by the author.
This is my personal blog…
From the blog CS@Worcester – CS Today by Guilherme Salazar Almeida Nazareth and used with permission of the author. All other rights reserved by the author.
Having never really used this blog during my time studying engineering, I suppose this will be the start of a CompSci dedicated blog. For the time being, these posts will be relating specifically to the CS-348 course at Worcester State, most likely to record and catalogue all of our learnings and group assignments.
I’ll likely try to find a way to move this site off of umasscreate eventually, and probably repurpose the entire site, but until then I’d like to keep all my things together. Probably also pick a nicer page color.
From the blog CS@Worcester – Justin Lam’s Portfolio by CS@Worcester – Justin Lam’s Portfolio and used with permission of the author. All other rights reserved by the author.
Hey. I am a student at WSU taking CS 348. This is a test post to introduce the blog and make sure it appears on the CS@Worcester blog.
From the blog CS@Worcester – Mr. Lancer 987's Blog by Mr. Lancer 987 and used with permission of the author. All other rights reserved by the author.
Hello again, it’s like we’ve met before. Once more, my name is Oanh Nguyen. At this point and time, a student at the university of Worcester State. I major in computer science and minor in business administration. Nothing much changed. However, I would to point out that I’m also taking ‘Software Process Management’ on top of my other class. Many further blog will be related to this class. Which will be tagged accordingly.
I won’t take up your time any more than this. It’s nice to meet you all again, those reading this. Thank you.
From the blog SoftwareDiary by Oanh Nguyen and used with permission of the author. All other rights reserved by the author.
This is my blog for CS-348 Ben Gelineau
From the blog CS@Worcester – WSU CS Blog: Ben Gelineau by Ben Gelineau and used with permission of the author. All other rights reserved by the author.
This is my blog, A Bostonians Blog. I couldn’t think of a better name than this but this blog is my personal space to share insights, experiences, and discoveries as I progress through my coursework, particularly focusing on Computer science at Worcester State University.
From the blog CS@Worcester – A Bostonians Blogs by Abdulhafeedh Sotunbo and used with permission of the author. All other rights reserved by the author.
I’m Joanna P. and I’ll be using this blog to talk about my journey though learning computer science.
From the blog CS@Worcester – My Journey through Comp Sci by Joanna Presume and used with permission of the author. All other rights reserved by the author.
Hello World, my name is Santiago Donadio and this is my first blog post.
I am currently taking CS348 – Software Process Management with Professor Wurst.
From the blog CS@Worcester – Programming with Santiago by Santiago Donadio and used with permission of the author. All other rights reserved by the author.
Introduction
As we conclude Sprint 2, it’s essential to take stock of our journey, examining both our successes and the challenges we’ve encountered along the way. This sprint, our primary focus was on scaling up productivity and initiating the UI development process. Despite its longer duration compared to the previous sprint, Sprint 2 felt back-heavy due to delays in commencing frontend work until we obtained access to the new template.
Challenges Faced and Lessons Learned
Both sprints presented us with unique challenges, contributing to our team’s growth and development. One significant challenge in Sprint 2 was the unexpected complexity encountered while coding a UI component. Initially deemed a simple task, unforeseen changes in the source code necessitated extensive adjustments, resulting in delays and frustration. However, this challenge provided valuable lessons in flexibility and adaptability. By grappling with the intricacies of the component and adapting to evolving requirements, we honed our problem-solving skills and gained a deeper understanding of UI development.
Another challenge stemmed from the weight of certain child issues, which had a more substantial impact on our workflow than initially anticipated. This highlighted the importance of thorough planning and assessment when breaking down tasks and allocating resources. Moving forward, we recognize the need for a more nuanced approach to issue prioritization to ensure each task receives the appropriate attention and resources.
Team Dynamics and Communication
Effective communication emerged as a cornerstone of our approach throughout both sprints. We found that tackling problems collectively as a group significantly eased the resolution process. Whether through online discussions or face-to-face meetings, open dialogue and transparent communication channels were maintained, ensuring alignment and informed decision-making. We intend to prioritize effective communication, proactive problem-solving, and meticulous planning in future endeavors.
Strategies for Improvement
Team Improvement
Personal Improvement
Moving Forward
As we look ahead, we are committed to leveraging the lessons learned from Sprint 2 to inform our approach in subsequent iterations. Documenting challenges, solutions, and key takeaways in a “lessons learned” repository will serve as a valuable resource for future sprints, enabling us to anticipate and mitigate potential obstacles more effectively. With a shared commitment to continuous improvement and a supportive team environment, we are confident in our ability to overcome challenges and achieve our goals collectively.
From the blog CS@Worcester – CS: Start to Finish by mrjfatal and used with permission of the author. All other rights reserved by the author.