Deliberate resource allocation - Deepstash
Deliberate resource allocation

Deliberate resource allocation

There should be proper allocation of time and money in order to build a feature that protects the team so that they can focus on their assigned tasks. Too much distraction won't make the designers and developers make progress.

Only the management can protect the cycle of three (1 designer, 2 programmers) of which is rotated based on need. 



An agile team will not go very far if management does not protect their time. The team should have flexibility, especially the management because as the team learns, late nights and late deliveries are guaranteed. 


Uphill strategies

Software development is not like moving a pile of stones from point A to point B.

Challenges come often and to be able to solve them is like going through an uphill phase where you try to figure out where you're going and then when you get to the top, you'll be able to see the other side and what it takes to finish.

Curiosity is an important regimen for a team because the only way to gain certainty is to engage with the reality of the problem.


A Mutable Requirement

Give the teams the power to redefine scope because they are able to differentiate what is essential and which aren't.


Deepstash helps you become inspired, wiser and productive, through bite-sized ideas from the best articles, books and videos out there.



Agile mindset

Agility is the ability to be quick and graceful. Agile mindsets focus more on core values such as: Respect, Accountability, Collaboration, Being adaptive to change, learning cycles and improvement.

An Agile mindset helps to easily overcome obstacles and not get stuck when unexpected events happen.



The agile framework

The agile framework is about optimizing performance. One way to inspire that improvement and help teams grow in the process is by celebrating wins and setbacks.



1. Planning Poker: All participants use numbered playing cards and estimate the items. Voting is done anonymous and discussion is raised when there are large differences. Voting is repeated till the whole team reached consensus about the accurate estimation. Planning poker works well when you have to estimate a relative small number of items (max 10) in a small team (5-8 people). Tip: try to keep the voting between affordable numbers. Maximize the highest card to 13 points. More on planning poker via this link. 

2. T-shirt Sizing: This is a perfect technique for estimating a large backlog of relative large items. Especially when you have several concurrent scrum teams working on the same product. Items are estimated into t-shirt sizes: XS, S, M, L, XL. The decision about the size is based on an open and mutual collaborative discussion. This method is an informal and quick way to get an rough feeling about the total size of your backlog. More about T-shirt size estimation is here.

3. Dot Voting: When you are faced with a relative small set of items and in need of a super simple and effective technique to estimate you can use Dot Voting. This method has originated form decision making and you can use it for estimating. Each person gets a small number of small stickers and can choose to vote for the individual items. The more dots is an indicator of a bigger size. Works well in both small and large group. You have to limit the number of estimated items. More on dot voting here.

These are different methods you can use to make agile estimation more efficient and an inspiring team effort. Please share your experiences with this below in the comments section. 



❤️ Brainstash Inc.