Scrum Methodology Quotes

Agile Manifesto.” It declared the following values: people over processes; products that actually work over documenting what that product is supposed to do; collaborating with customers over negotiating with them; and responding to change over following a plan. Scrum is the framework I built to put those values into practice. There is no methodology.

when agile projects fail, it’s often because of cultural and philosophical differences between waterfall and agile methodologies.

Managers of programming projects aren’t always aware that certain programming issues are matters of religion. If you’re a manager and you try to require compliance with certain programming practices, you’re inviting your programmers’ ire. Here’s a list of religious issues: ■ Programming language ■ Indentation style ■ Placing of braces ■ Choice of IDE ■ Commenting style ■ Efficiency vs. readability tradeoffs ■ Choice of methodology—for example, Scrum vs. Extreme Programming vs. evolutionary delivery ■ Programming utilities ■ Naming conventions ■ Use of gotos ■ Use of global variables ■ Measurements, especially productivity measures such as lines of code per day

We’ve lost our way” is how another manifesto author, Andrew Hunt, put it in a 2015 essay titled “The Failure of Agile.” Hunt tells me the word agile has become “meaningless at best,” having been hijacked by “scads of vocal agile zealots” who had no idea what they were talking about. Agile has split into various camps and methodologies, with names like Large-Scale Scrum (LeSS) and Disciplined Agile Delivery (DAD). The worst flavor, Hunt tells me, is Scaled Agile Framework, or SAFe, which he and some other original manifesto authors jokingly call Shitty Agile for Enterprise. “It’s a disaster,” Hunt tells me. “I have a few consultant friends who are making big bucks cleaning up failed SAFe implementations.” SAFe is the hellspawn brainchild of a company called Scaled Agile Inc., a bunch of mad scientists whose approach consists of a nightmare world of rules and charts and configurations. SAFe itself comes in multiple configurations, which you can find on the Scaled Agile website. Each one is an abomination of corporate complexity and Rube Goldberg-esque interdependencies.

Most literature on the subject of agile methodology... is written from the viewpoint of software developers and programmers, and tends to place its main emphasis on programming techniques and agile project management—testing is usually only mentioned in the guise of unit testing and its associated tools. ...However, unit tests alone are not sufficient and broader-based testing is critical to the success of agile development processes.

Scrum is either of two types, understanding what is required, or telling what is delivered.

Scrum is about plotting your TO-DOs in calendar and ticking them off.

Scrum refers to; orderly crowd or disorganized team.

Scrum is like a roundtable; with agenda, followed by minutes.

In a scrum team, no one is boss but a partner, for the success of a project.

To keep growing; keep evolving.

Scrum, in simple terms is managing a TO-DO list.

Every role in a scrum team is either a producer or a consumer, within.

people over processes; products that actually work over documenting what that product is supposed to do; collaborating with customers over negotiating with them; and responding to change over following a plan. Scrum is the framework I built to put those values into practice. There is no methodology.

Synonyms for Scrum Ceremonies are what, when, who, how, why.

Agile has become the salt and pepper for the world of projects.

Being Agile; piece by piece, step by step.

many software companies now deploy the Scrum project management methodology, which replaces a lot of this ad hoc messaging with regular, highly structured, and ruthlessly efficient status meetings (often held standing up to minimize the urge to bloviate).

Brainstorming is to aim for alternatives.

Brainstorming is not about HOW; but How-To-Wow.

Tougher the project; Agiler the approach.

Agile; a little fragile; handle with care.

Some web development organizations, particularly those following Agile development methodologies, don’t like this advice. “You Ain’t Gonna Need It,” they say, quoting the YAGNI principle of waiting until you definitely need a feature or plan before starting to work on it. “Who knows if we’ll ever get attacked? Working on a plan now could end up just being wasted time. We’ll deal with this issue if it ever happens.” That’s fine—if you don’t mind getting your team together for an ad-hoc scrum meeting at 3:00 A.M. on Christmas morning.

The Agile project manager plays a crucial role in ensuring the successful delivery of projects using Agile methodologies. They act as facilitators, coaches, and leaders, guiding the team through the iterative development process. Here are some key responsibilities of an Agile project manager: Orchestrating the project's lifecycle: This involves planning and breakdown of work into sprints, facilitating ceremonies like daily stand-ups, sprint planning, and retrospectives, and ensuring the project progresses smoothly towards its goals. Promoting collaboration and communication: Agile thrives on open communication and collaboration. The project manager fosters an environment where team members feel comfortable sharing ideas, concerns, and updates. They actively remove roadblocks and ensure everyone is aligned with the project vision and goals. Empowering the team: Agile teams are self-organizing and empowered to make decisions. The project manager provides guidance and support but avoids micromanaging. They trust the team's expertise and encourage them to take ownership of their work. Stakeholder management: The project manager acts as a bridge between the development team and stakeholders, including clients, sponsors, and other interested parties. They keep stakeholders informed of project progress, manage expectations, and address their concerns. Continuous improvement: Agile is an iterative process that emphasizes continuous improvement. The project manager actively seeks feedback from team members and stakeholders, analyzes project data, and identifies areas for improvement. They implement changes to the process and tools to enhance efficiency and effectiveness. Overall, the Agile project manager plays a vital role in driving successful project delivery through Agile methodologies. They wear multiple hats, acting as facilitators, coaches, leaders, and problem-solvers, ensuring the team has the resources, support, and environment they need to thrive.