Discussions on Agile theory and Agile approaches
Scrum has been too often shoved into situations where it has no business being. I know Scrum proponents will often tell you Scrum is versatile and it can go anywhere – it can’t. There are jobs that are too big for Scrum. Scrum is a lightweight approach. It […]
*The following is written by guest blogger Tammy Ziemba With the assistance of Feature Driven Development, you can make the design, code, and code inspection plans without going into expounding administrative work. Here the focus is more on depending on individuals and their work for development. *More […]
*The following is written by guest blogger Tammy Ziemba Extreme Programming (XP) is an agile software development framework that aims to deliver higher quality software and higher personal satisfaction for the development team. XP is the most explicit of the frameworks in regards to suitable design practices for […]
What is Flaccid Scrum or Flaccid Agile? In the beginning, Scrum teams are moving along fast. They are doing most of what they say they will do in a Sprint and churning out code like a virtual code factory. As time goes on, they may start to get […]
*The following is written by guest blogger Tammy Ziemba Test Driven Development (TDD) is a moderate programming advancement process that is driven by a computerized test case which characterizes the ideal improvement to the system. The test is first executed to come up short. The developer at that […]
*The following is written by guest blogger Tammy Ziemba Agile development is based upon a value system and specific core practices, that when reliably connected, result in high performing software development organizations. Build up Wildly Important Goals: A team can concentrate on 1-3 things at any given […]
Agile is a generic or “umbrella” term for an operational framework or methodology that strives to keep a focus on requirements by using adaptive approaches and continuous improvement practices. A Simple Agile Explanation Not everyone has time to read one of my long-winded explanations on Agile, Scrum, and […]
Quite simply, Osmotic Communication is the accidental overhearing of background information that may later end up being important. The term was coined by Alistair Cockburn, one of the signers of the Agile Manifesto. “Osmotic communication means that information flows into the background hearing of members of the team, […]
If you are using Kanban within Scrum or another Agile framework, you may not need to worry much about this. The meetings used as part of those frameworks should work perfectly fine. This is more meant to be a suggested guide of meeting types if you are embracing […]
If you went through an earlier tutorial on custom issue types I created (Customize Issue Types in Jira), you would have noticed that I modified the Issue Types for one project and one project only. But what if we wanted to create a standard set of Issue Types […]
To understand Kanban, you must first learn what it is and is not. I covered some of this in What is Kanban?. To sum up that article, there are two different Kanbans – we will call them Lean Kanban and Agile Kanban. Agile Kanban is too often confused […]
The Scrum Master is one of three recognized roles in Scrum. They are the servant-leader for the Scrum team, which means they serve the team by working to provide what the team needs to complete their job. This could be working to make sure they have the right […]
There are many sources available that discuss Agile and Agile principles. One of the most well-known is the Manifesto For Agile Software Development, which is commonly known as the Agile Manifesto. This includes the 12 Principles behind the manifesto. I personally have some issues with the Agile Manifesto, […]
A joke I heard once was that in an 8 hour day, Agile has 7 hours of meetings and 1 hour of work. There can be some truth to it if you let it happen.
Agile is supposed to be strict. I am not saying miss a daily standup because you don’t feel like doing it, I am saying there are situations where letting some team members not attend would be acceptable.
