A sampling of public posts that I wrote in October 2022:
Electronic tooling, especially tools with good searching and filtering capabilities, reduce the need to control the size of a backlog. The focus can shift to ensuring that the work in a backlog still is valid with respect to the vision.
Agility is built around flexible scope, so scope creep is of a far lesser concern, as long as the work aligns with the goals, objectives, and vision.
Lean-agile methods and long-term planning are at odds with each other. Agility recognizes that change is inevitable, so preparing for change is a better approach than complex change control and change management processes. Lean defers decisions to the last responsible moment to avoid decisions being invalidated and the effort that went into making them wasted as new information is revealed.
Releasing, delivering, and demonstrating are distinct methods of getting feedback. Agility is about getting rapid feedback and incorporating that feedback and not about how that feedback is obtained.
Projects do not need an end date, but they do need to have defined end criteria. This could be a date, a goal or objective, a level of effort, or some other objective criteria.
In Scrum, the fixed-length and timeboxed Sprint provides a planning cadence, a product feedback loop, and a process feedback loop. Changing the iteration length without proper consideration for the impact to all three can negatively impact the team's ability to plan and execute work while increasing the risk of building the wrong thing.
Moving a card "backwards" through a workflow isn't a problem to be avoided, especially if it makes the true state of work more visible to key stakeholders.
User acceptance testing (UAT) doesn't fit into team's development workflow. In nearly all cases, successfully completing UAT requires dependencies outside of the team, which makes it incredibly difficult to plan, since the team has little to no influence over these dependencies.
Branching strategies do not replace effective communication and collaboration between team members.
In an existing project with little architectural and design documentation, The Arc42 documentation template and the C4 model for diagrams provide a solid structure to begin organizing relevant information.
The Cloud Security Alliance's Cloud Controls Matrix provides a lighter and cheaper steppingstone for organizations seeking audit and certification against standards such as ISO 27001 or a SOC2 certification.
