Posts

Software Process Management Blog #5

By on
 For my 5th Software Process Management blog, I reviewed “There’s got to be a better way: your guide to process improvement” by Lauren Moon This blog post on process improvement frames process work as a disciplined, iterative activity that blends feedback, metrics, and small experiments to make teams more effective. The post defines process improvement as intentionally evaluating workflows and tools, collecting feedback from stakeholders, and running incremental changes (experiments) to remove friction and increase value delivery. It surveys concrete tactics, mapping workflows, identifying pain points, prioritizing improvements that unblock flow, and measuring outcomes, and shows how familiar Agile practices (retrospectives, small batch sizes, and continuous feedback) fit into a larger process-improvement lifecycle. The article stresses that process improvement is not a one-time audit but a cultural habit: document existing flows, try minimally invasive changes, measure results, an...
Post a Comment
Read more

Software Process Management Blog #4

By on
 For my 4th Software Process Management blog post, I reviewed “Continuous Integration” by Martin Fowler.  Martin Fowler’s long-form blog on Continuous Integration lays out the practice as a cornerstone of modern software process management: developers integrate small changes frequently into a shared mainline, and each integration is verified by an automated build and test suite so integration problems are discovered early. Fowler explains the motivation (which is reducing integration hell and long rebasing cycles), the mechanics (frequent commits, automated builds, fast tests, and a visible build status), and practical patterns and anti-patterns that teams encounter when adopting CI. He walks through how CI reduces risk by shortening feedback loops, how it supports other practices (like trunk-based development and test automation), and common traps, slow test suites, poor branching strategies, and insufficient test coverage, that blunt CI’s value. The piece mixes concrete prac...
Post a Comment
Read more

Software Process Management Blog #3

By on
  For this blog, I reviewed “Why your team needs a software development process” by Anabelle Zaluski. A short summary of the blog: This blog entry explains how a well-defined software development process exists because software projects often evolve in unpredictable ways, and without structure, even highly experienced teams can find themselves overwhelmed. Scope changes, emergent bugs, shifting stakeholders, and unclear responsibilities can easily derail progress, especially in fast-paced development environments. The blog emphasizes that a clearly articulated lifecycle—covering planning, design, implementation, testing, deployment, and maintenance—provides stability in the midst of complexity. Such a lifecycle functions like a shared map that every team member can follow, ensuring that expectations are transparent and that work flows logically from one stage to the next. This clarity not only prevents confusion but also minimizes the risk of tasks being overlooked or mis prioritiz...
Post a Comment
Read more

Software Process Management Blog #2

By on
  For this post, I reviewed "How NC State’s Tech Transfer Office Cut Compliance Risk & Recovered $200K" by Kate Meda. This blog covers a compelling transformation in academic operations. Faced with mounting compliance challenges and fragmented documentation, NC State’s Office of Research Commercialization turned to Process Street to automate workflows and standardize procedures. This shift enabled the team to streamline interdepartmental coordination, especially between finance and legal, while reinforcing governance and accountability. As a result, the office recovered $200,000 in previously lost revenue and significantly reduced compliance risk. Staff engagement improved as roles became clearer and documentation more accessible. Assistant Director Nicholas LeBlanc emphasized how automation brought their SOPs “to life,” making processes not only more efficient but also more transparent. I think this blog is a powerful example of how software process management can di...
Post a Comment
Read more

Software Process Management Blog #1

By on
For this blog post, I reviewed "6 Project Management Best Practices to Drive Successful Software Development" by Manan Thakkar. Manan Thakkar’s blog, “6 Project Management Best Practices to Drive Successful Software Development,” outlines the core management principles that help ensure successful outcomes in software projects. The blog emphasizes the importance of strong communication and collaboration among stakeholders, noting that clearly defined roles, responsibilities, and regular meetings prevent misunderstandings and keep teams aligned. Thakkar stresses the need for thorough planning that balances realistic expectations with project goals, accounting for risks, dependencies, and external factors that could affect timelines. Another major focus is change management, highlighting that software projects evolve constantly and require structured processes to evaluate and control scope changes without disrupting delivery. The blog also underscores the importance of providing...
Post a Comment
Read more

Software Introduction Post

By on
Hello, this is my introduction blog for my CS-348 class. 
Post a Comment
Read more

CS-443: Blog 4

By on
 CS@Worcester CS-443 For this post, I reviewed "Why is quality assurance a key to software development success?" by Emily Dobutović    The article explains how quality assurance (QA) is a fundamental aspect of software development, ensuring that products meet both business and technical requirements while maintaining high standards of reliability. It emphasizes that QA is not just about detecting bugs but involves a structured process spanning multiple phases, including requirement analysis, test planning, development, execution, and maintenance. QA engineers play a crucial role in improving quality control and testing, helping companies reduce post-launch defects and enhance user satisfaction. The article also highlights the importance of automated testing, which accelerates delivery and minimizes manual errors, making software development more efficient. Additionally, the article explores various testing methodologies and tools that contribute to successful QA implement...
Post a Comment
Read more