Cry Me A River: You Can’t Escape Documentation

A company's team members, project goals, time constraints, budget limitations, and resources influence the methodology most suitable for building software. Changes in the plan cost money in any methodology. It would be a mistake to blindly state that waterfall is outdated, just like it is premature to blindly state that agile is automatically unorganized and unprofessional. Waterfall works well for companies developing first-time websites or applications on a fixed timeline or budget. Agile works well for large companies performing team-driven website maintenance that includes development with limitless project budgets, no hard deadlines, and job security where everyone receives payment regardless of unlimited changes to the project life cycle.


Personality makes the perfect company culture subjective to the developer. For example, I am more productive without morning meetings, while morning meetings help others feel focused and supported. Some people enjoy having a step-by-step process to keep them on track during a writing or development process; however, I would never want to have to turn in every paragraph before my work has a chance to develop. I contribute my best work when I have a positive employer who respects my time and believes in the quality of my work. Many companies believe in producing low-quality products for the sake of time, but I find fulfillment in working on projects that invest the time to develop quality products.


The waterfall method addresses changes during designated times. When using the waterfall method, the customer feels more secure if customer involvement exists as a planned part of the process. During the implementation phase, customers who request constant changes indicate a need to revisit the mind map to provide security and ensure that the correct product is being built. Waterfall does not automatically mean ignoring the customer and discarding feedback. The customer should still be updated, and communication should remain open. Requirements can be revised. Feedback should be organized and controlled. Wireframes and mind mapping assist a company in producing the right product for the customer. Customer feedback and revision must be a part of any good process; however, organization and documentation are necessary. Planning and agreeing on the work that will be done is a sign of good business practice that protects a developer from not being paid for a project. Using the waterfall method, I would handle changes by planning with the customer upfront, sending the customer update emails, revisiting the mindmap when necessary, and paying attention to feedback during the acceptance meeting. 


No single method is right or wrong from one team to the next. Teams are made up of unique personalities. When considering methodology, understand that there are a hundred ways to skin a cat. Work for a company that makes you feel respected and supports your growth. Who knows, quitting a terrible working environment might even get you a raise.

Comments

Post a Comment

Popular posts from this blog

SalonAboutBeauty: Less Integration for Consistent Styling Across Components

Ensuring Consistent Variables Less provides several advantages for organizing CSS to ensure consistency across a website. The variables.less file defines reusable properties that allow a developer to easily communicate and maintain styles according to a style guide or theme.  The Less Web Development Cookbook describes properties in the variables.less file in relation to other programming languages: “Variables in Less are defined as the equivalent to statics in other programming languages. You assign a value to a variable once and use it everywhere in your code” (Meyghani & Jobsen, 2015, p. 50). It suggests that less allows a developer to set properties, such as colors and length, to variable names that retain their meaning and can be used everywhere in the code. Examples: @base-color: red, @primary: green.  By providing these definitions in a central location, developers create code consistency in all areas of the website. Creating an Organized File St...
Read more

Why “Human Error” Is Usually a System Design Problem

In complex systems, failure rarely comes from a single bad decision. It comes from problems that evolve slowly, cross boundaries, and remain unresolved while everyone involved behaves reasonably. Managing risk in these environments means managing trajectories, not just incidents. When ownership is divided strictly by role, function, or severity threshold, gaps are inevitable. Those gaps are where issues linger, age, and quietly accumulate risk, not because they were ignored, but because no one was responsible for carrying them forward end to end. This is common in healthcare, where delay is often necessary. A patient may require observation, referrals, or time to clarify diagnosis. The failure is not that care takes time; it is that the trajectory of care becomes fragmented. Each clinician escalates correctly within scope, yet no one owns the evolving picture across visits, domains, and decisions. The patient is evaluated repeatedly, reassured locally, and sent away without continuity ...
Read more

Challenges in Prosecuting Deep Web and Darknet Crimes: The Case of Ross Ulbricht and the Silk Road

  The deep web represents online information that is not easily accessible through search engines. Prosecuting crimes on the deep web is no more challenging than prosecuting crimes for any standard website because law enforcement can still track the user's location through a domain or IP address. Alternately, the darknet poses a challenge for law enforcement to address illicit activity because while the darknet is a web-based system, it is accessible only through the Tor protocol that encapsulates HTTP and HTTPS traffic, much like a VPN that hides a user’s location and identity. The Tor protocol, often called the Onion Router, contains methods for encrypting and routing traffic between peers. The purpose of the Tor protocol is to make web browsing anonymous by routing each request through multiple peers and altering encryption at various steps until the request reaches its destination. Subsequent requests may hop through different peers, making traffic appear random, unpredictable,...
Read more