Telerik blogs

Tag: Agile

  • Productivity

    2 Quick Agile Myths- Busted?

    Agile Projects don’t use Project Managers It is true Scrum doesn’t discuss Project Managers – it focuses on the Product Owner, Scrum Master, and the Development Team. Scrum is only one implementation of the agile principles (albeit probably the most well-known). Even though Scrum doesn’t call out the role of Project Management in its literature, it never states that you can’t have one. Project Managers typically have different responsibilities, such as budgeting, reporting, and portfolio management. These are all extremely important, especially in larger organizations, and experience project managers excel at these tasks. Project Managers are also a vital link ...
    November 07, 2013
  • Productivity

    The Truth About Agile | Top 30 Agile Myths- BUSTED

    Agile is not suitable for fixed bid projects Before looking at this myth, it’s important to define “Fixed bid projects”. Does this mean fixed scope, schedule, and cost? History has proven that software projects of any significance in size or complexity cannot be accurately estimated well. What is more, according to CHAOS reports 24% of all projects fail and 44% are significantly challenged2. Regardless of the project management methodology, attempting to fix all three does not have a high probability of success. Something has to give – whether it’s adding resources, cutting scope, or moving the delivery date. As described ...
    October 23, 2013
  • Productivity

    First 5 Agile Myths- BUSTED

    Agile has no Process, doesn’t have Documentation, doesn’t believe in Contracts, doesn’t follow a Plan These four common agile myths most likely come straight from a misunderstanding of the Manifesto’s value propositions. In order to fully understand the value propositions, you have to take all three parts into account, not just the middle section.
    October 16, 2013
  • Productivity

    Top 4 Challenges for Agile Planning

    Despite trying to achieve simplicity, Agile teams may still run across difficult issues. In this section some of the more common challenges are explored. HANDLING INCOMPLETE WORK AT THE END OF AN ITERATION It is not uncommon for a team to have incomplete work at the end of an iteration. Unfinished work is an important issue to identify as it signals a potential problem with one or more aspects of the team. When an iteration is planned, the team sets an expectation with the customer. When those expectations are not met, the customer could lose faith in the team’s ability ...
    October 09, 2013
  • Productivity

    [A Few Tips] How to Decompose User Stories and Assign Tasks

    Decomposition into Tasks Your backlog is normally comprised of requirements in the form of User Stories which depict the resulting value required by the users of the system. During iteration planning, teams take the highest value requirements and assign them to the current or next iteration, filling the iteration to capacity. Agile teams typically do not decompose requirements into work tasks until they are assigned to an iteration. Agile teams spend the first few hours of each iteration going through iteration planning, and a part of that process is the decomposition of requirements into work that can be completed by ...
    October 03, 2013
Prev
1 2 3 4 5 6 7 8 9 10 ...
Next