Software development quotes
What happens if you intervene and they still don’t fix the stand-up? Remember, the accomplishments and bumps are theirs, not yours. Agile works when they learn how to rely on one another. It has nothing to do with you looking good as a coach. So, if they do not improve, …
The ScrumMaster is one of the most undervalued roles in Scrum and Agile. Most teams that are just starting out don’t see the value of having a full-time ScrumMaster, and they try to combine this position with that of a developer or tester so that the ScrumMaster is “working.” It’s …
Have you ever made a decision, implemented the decision, and then been confronted with a raft of questions: “What were you thinking?”, “Why did you not do that?”, or “Why did you do it that way?” How can you avoid this disconnect? Bring the stakeholders together and build the value …
One of the most important expectations to set early on is about involvement in the process. Many project stakeholders accustomed to traditional-style development view their role in a software development project as akin to dropping a car off for service: You tell someone what you need done and come back …
Although many organizations are certified at SEI CMM Level 5, when a team hits a production snag, those certificates don’t carry much weight. People need IT heroes in the team to pull things through. Dependencies on folks who are technically competent, can think on their feet, and can manage time …
Experience shows that architecting is not something that’s performed once, early in a project. Rather, architecting is applied over the life of the project; the architecture is grown through the delivery of a series of incremental and iterative deliveries of executable software. At each delivery, the architecture becomes more complete …
