How do you estimate agile projects outside of software?

Agile is an approach to implement a project, which includes several types of frameworks, project must be divided to the smallest pieces which can be delivered in the specific time box! Define the project scope is coming from discovery and customer requirements which must be prioritized before that and continue during the development and delivery phases please check agile onion model… your questions is wrong! Agile means continuously discovery, development and delivery.

The first very important step is to identify the “problem “ you want to solve. All projects are created for solving specific issues. Pointless projects do not provide values can not live long.

The objective of estimating agile projects outside of software is to accurately determine the effort, time, and resources required to complete the project tasks, allowing for effective planning, tracking, and decision-making throughout the project lifecycle.

First question is whats the fitment of Agile to concerned projects outside software developments. Is it's a type of product which needs to be continuously evolved over time? Whats the size of market it's going to impact? Whether Agiles principles are a good fit for purpose where it is to be implemented. If yes then we can focus on further aspects of implementation.

Selecting an appropriate estimation method is pivotal for agile projects. For instance, in our recent software development endeavor, we opted for the planning poker technique. It encouraged team collaboration, transparency, and an adjustable approach as we broke down complex tasks into manageable chunks. By utilizing this method, we were able to provide more accurate estimations, enabling better project planning and resource allocation throughout the development lifecycle.

If you chose to adopt Story Points for estimation, the Fibonacci sequence benefits Agile estimation by offering a relative sizing scale (1, 2, 3, 5, 8, 13...) that reflects complexity. It encourages discussion, breaks down complex tasks, and avoids false precision. Teams adapt easily to changes, ensuring consistency in estimating and predictability in project planning through historical velocity analysis. This practice also accounts for a certain level of fluctuation and unplanned work by providing a range rather than a 1:1 representation of hours estimated for the work to be completed.

Estimation should not be a single-person activity in agile it should be a team activity. One person proposes and others can question and discuss and everyone should be convinced that the estimates are correct if not then discussion can continue until some valid justification is received on the estimates. sometimes the estimates are done by someone else but worked by someone else in this case if it was a team decision then it might have been discussed and some valid justification might be there for the estimates which even a new person could adapt to. Agile is always adapting to new challenges and realigning based on the needs of the business or team

In of my project, we opted for the planning poker estimation method, and to enhance our workflow, we implemented a work breakdown structure using Scrum. This strategy included segmenting tasks into distinct sprints, each with well-defined goals. For instance, one sprint was dedicated to user interface design, while another centered around backend development. This methodical breakdown allowed us to create accurate estimates for the time, resources, and budget necessary for each sprint, significantly improving our project planning and execution.

Taking this perspective into account, estimating project timelines becomes a matter of embracing incremental progress. Just as Rome wasn't built in a day, complex endeavors require breaking them into manageable steps. Instead of attempting to predict a distant finish line, Agile principles suggest focusing on short-term, achievable goals. This approach allows for flexibility and adaptation along the way, as it's easier to gauge progress and adjust course during smaller intervals. Whether it's a software development project, a personal goal, or any other endeavor, estimating becomes more reliable when you acknowledge that lasting accomplishments are the result of consistent, incremental efforts

One thing I have always noted in projects, in order to break down the work you have to understand the work. In Agile that means grooming, everyone involved should understand the work that needs to be done and how to tell, or demostrate that the work is done. Grooming is bringing the team together to discuss the work, if it is written as a story or task to be used in a sprint or cycle all involved parties need to understand the why and the how of the work to be done, as well as how to know it is done. In many projects I have seen problems arise from not knowing how to tell that no more work is needed on the task.

Comprendre les principes agiles : Comprendre les valeurs et les principes agiles définis dans le Manifeste Agile en intégrant les concepts tels que : la collaboration avec les parties prenantes, la flexibilité face au changement et la livraison continuent de valeur. Adapter les méthodes : Les méthodes agiles doivent être adaptées pour répondre aux besoins spécifiques du secteur. Établir des objectifs clairs : Définir des objectifs clairs et mesurables pour le projet. Cela inclut non seulement les résultats finaux attendus, mais aussi les critères de succès pour chaque itération ou cycle de travail.

Agile frameworks like Scrum or Kanban can be applied to organize the work: • Scrum: Breaks the work into sprints, which are short time cycles focused on completing specific tasks with continuous reviews. • Kanban: Provides a visual representation of the task flow, making it easier to track the real-time status and progress of each item. By breaking down the work in this way, you gain a clearer understanding of the project’s needs, improve the accuracy of your estimates, and streamline resource allocation, ensuring more effective execution and on-time delivery of results.

In one of my projects, we utilized a thorough estimation strategy, incorporating scenarios for best, worst, and most likely outcomes to tackle uncertainties. We also implemented risk management techniques to preempt potential obstacles. Validating and transparently sharing these estimates with both stakeholders and team members helped us harmonize expectations and goals, while also equipping us to proactively address any unexpected issues, thereby elevating our project's overall efficiency and triumph.

On the validation side of things, if necessary, you can have experts or senior team members help by identifying overly pessimistic/optimistic ones or even bring a fresh perspective. But remember, agile is iterative so the estimations tend to get more accurate as the team develops and the work progresses. I suggest tailored communication since different stakeholders may require different levels of detail. For example, you can provide executive summaries for higher management, while sharing detailed reports for project teams.

Agile prioritizes flexibility, adaptability, and collaboration, principles that can apply to various projects—from marketing campaigns to organizational change initiatives. I'd say one thing worth considering is how to handle risk and uncertainty in those initiatives: Buffer for Uncertainty: Always add a buffer for unknowns. In Agile, you have the flexibility to adapt, but it's still wise to account for some level of uncertainty. Inspect and Adapt: Regularly review performance metrics and re-estimate based on the latest data and learnings. Use retrospectives to analyze what went well and what needs improvement. Being able to adapt and respond to change is at the heart of Agile, whether you're developing software or planning an event.

According to me, every work needs common things to get executed. Estimation is the approximation of effort needed to complete the work as stated in the scope with acceptance criteria and definition of done to arrive at business value. so with this view, you all are experts to execute the work so you can easily estimate, may be based on the complexity, readymade tools available, volume of work, dependency with others, availability of all resources required (HR/non-HR) etc. You may use any method of estimation based on appropriation and fitting to the work strategy.

I would like to emphasize the importance of continuous learning. Focusing on a (non software) project following agile principles, this implies the feedback of the experiences, and lessons learned before and during the project lifetime. As the team excels in this, the mistakes transform into development opportunities, and the individuals as well as the team skills are being elevated over time. This leads to risk reduction, improves the probability of the project success, and even more importantly, supports the personal development of the team members, that might go well beyond the lifetime of the project. (Fruits harvested sometimes years after the project’s end.)

Agile supports relative estimation technique which gives much more flexibility to developers in terms of creativity and productivity. The work to be done is compared with a similar piece of work done in the past and similar size can be provided. If a similar type of work is not done earlier, every team member can suggest their choice of size for this work and the best among these can be considered as the size of work.

Scrum and Agile methods, with their adaptability and incremental focus, permeate various sectors and life itself. They echo the age-old wisdom that monumental achievements, such as Rome's construction, require consistent, gradual progress. In software development, teams employ Scrum's sprint cycles for incremental gains. Individuals can apply this to personal growth, breaking life goals into manageable steps. Agile's influence extends beyond tech, fostering adaptability in education and improving healthcare through continuous feedback. In summary, Scrum and Agile embody the timeless truth that lasting progress often results from steady, incremental efforts, guiding both industries and individuals on their journey through life