Question: We are starting a project that is part hardware and part software driven. The organization has asked me if we want to use a traditional approach or a more flexible version like agile. It seems to me that the production line would benefit more from one and the IT team might do better with another. What do I recommend to management about what our team wants to adopt to move forward?
Have you been wondering about what Agile Estimating and Planning looks like? How it is different from traditional methods and why you would even consider using agile estimation methods? If you're looking for a closer look at how we estimate, what story points are, how to use velocity for planning, dealing with fixed date and fixed scope projects, maintaining product backlog using scrum boards for daily standups then this webinar is for you!
Per the Agile Business Consortium, business agility allows businesses to adapt quickly to market changes; respond rapidly and flexibly to customer demands; adapt and lead change in a productive and cost-effective way without compromising quality; and continuously be at a competitive advantage. The primary reason for moving to Agile is to achieve faster business value and keep you ahead of the competition. Agile is built for change - fundamentally, it is about creating Business Agility. It enables the enterprise to deliver projects more efficiently, with relentless focus on business value and providing the highest return on investment. Whether it is a software project, a new service offering or a new product, Agile’s twelve principles and three pillars (transparency, inspection, adaptation) are designed to reduce money spent on undesirable or unusable features which were built based on outdated requirements.
Coordinating Knowledge Work in Multiteam Programs: Findings From a Large-Scale Agile Development Program
Software development projects have undergone remarkable changes with the arrival of agile development approaches. Although intended for small, self-managing teams, these approaches are today used for large development programs. A major challenge of such programs is coordinating many teams. This case study describes the coordination of knowledge work in a large-scale agile development program with 12 teams. The findings highlight coordination modes based on feedback, the use of a number of mechanisms, and how coordination practices change over time. The findings can improve the outcomes of large knowledge-based development programs by tailoring coordination practices to needs over time.
Save Time With Tools And Templates
This template can be used to estimate costs for a project based on Scrum iterations/sprints. This tool assumes basic knowledge of agile/Scrum. The template is divided into three spreadsheets: Overview (detailed explanation of the template and usage), Estimator (calculations required for obtaining project cost estimates) and Data (look up data used in the estimator worksheet).
Scrum has been at the forefront of a revolution in how software is developed and deployed. Who is using it? How? And why? In this exclusive 48-page report from ProjectsAtWork, Scrum Alliance and ProjectManagement.com, 500 professionals share their answers.
This 19-slide deck is a companion piece to the Agile Distributed Teams research report from ProjectsAtWork. It is designed to help you leverage the report's key findings and recommendations to achieve the benefits of working with distributed agile teams in your organization.
Learn From Others
If we stubbornly insist on running projects “by the book,” we are going to miss opportunities. In that spirit, here are six ways to develop your hybrid approach to project management.
Scrum masters are critical to the success of agile projects, but as agile skills and experience in an organization grow, does the role need to evolve to remain effective?
After you've assembled a cross-functional innovation team and aligned around a goal, it's time to start using metrics and data to track the most important things, supported by a scorecard that everyone can see. This will help establish a rapid rhythm and generate positive velocity on your innovation journey.
Question: Last week, I was told that there will now be a business analyst (BA) working with my project team. To be honest, we have all the roles filled. Why are we being assigned yet another person to deal with? Isn’t it enough that they also want us to work with a second team to produce the tangible portions of this project, while we do the software and other soft deliverables? Can I refuse to accept this person into the group?
Expanding on an earlier article, the author details roles within the Scrum framework along with the organizational environment that needs to exist to transition to an agile approach. The benefits of agile and path to adopting agile practices are discussed, including use of a gradual incremental hybrid approach.
The daily standup is an important part of agile-based project delivery. But let’s be honest, any daily meeting can become stagnant and stale. Don't settle—you can re-energize your standups by changing the routine and honoring their true purpose.
The benefits of outsourcing also come with various challenges—often because the vendor will execute the work with a project mindset that has limited visibility and never really looks at it from the product mindset. Agile can help instill the right outlook.
Colonel John Boyd discovered that the primary determinant to winning aerial dogfights was observing, orienting, planning and acting faster. How does this apply to project management?
Like many fields, nonprofit and government organizations want to find ways to respond to projects faster and more efficiently. This article provides five ideas for them to use agile methods and approaches.
Ask a Question