Colocation is useful for meetings that require close listening, such as design discussions. It is also handy when new employees are training and need some amount of hand-holding or encouragement. Whiteboard is highly effective for colocated team but can be managed with online tools as well.
Continue readingThẻ: es-done
Scrum Philosophy: Release Early, Release Often
Release early, release often is a software development philosophy that emphasizes the importance of early and frequent releases in creating a tight feedback loop between developers and testers or users, contrary to a feature-based release strategy.
Continue readingScrum: How to Refine Product Backlog?
Not all items in the product backlog will be of the same size and level of detail (i.e. features/ eprics/ user stories and tasks) at the same time. PBIs that we plan to work on soon should be at the top of the backlog, smaller in size, and very detailed so that they can be worked on in the near-term sprint. PBIs that we won’t be working on for some time should be at the bottom of the backlog, larger, and less detailed.
Continue readingScrum: Do you need a vision statement?
A vision statement identifies where the organization wants or intends to be in future or where it should be to best meet the needs of the stakeholders. Every project needs a vision to steer itself in a proper direction. A vision serves as a guide for choosing the current as well as future course of actions.
Continue readingScrum: Solution vs Process Adaptive
What is Predictive Process? A defined and predictive process model is appropriate if both the requirements for the project and
Continue readingAgile Backlog Prioritization Technique: MoSCoW
MoSCoW Method provides a way to categorize users’ requirements based on their priority. It helps develop a clear understanding of the customers’ requirements and their priority. MoSCoW stands for must, should, could and would. Visual Paradigm comes with a rich set of diagram templates. You may start with a blank diagram or a pre-made MoSCoW Method template.
Continue reading12 Agile Principles — #12 of 12
“At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”
Continue reading12 Agile Principles — #11 of 12
“The best architectures, requirements, and designs emerge from self-organizing teams.”
Continue reading12 Agile Principles — #10 of 12
“Simplicity — the art of maximizing the amount of work not done — is essential.”
Continue reading12 Agile Principles — #9 of 12
“Continuous attention to technical excellence and good design enhances agility.”
Continue reading