Project management in construction follows traditional planning methods to communicate project schedules. The objective of this article is to show how agile tools like burnup and burndown charts help communicate project timeline and progress.
Everyone wants metrics, but which ones really matter? Which metrics can help you "actually" get better and give you visibility into the health of your teams?
Do you often find that when something fails in production, the response of a development team member is, “It works on my machine or at our end, you must be having the wrong version“? Vice Versa on the other side of the table – do you find that the operations team always feels that the developers are not sensitive to the operational requirements and constraints? If so, does that mean we are just developing software not a working system ? Are we just working in Silos ? DevOps aims at breaking the Silos and bringing in a culture of everyone “getting along”. Presenter Priya Patra disucsses how and why DevOps is the force behind the evolution where the development team and operations works together with business sponsors and quality assurance (QA) to deliver software that can be released to production at any point of time.
This webinar features the GSA (US General Services administration) and its journey in going Full Agile!
Save Time With Tools + Templates
The Risk Management Grid is a technique to identify potential risk events that could impact one of more of the project’s Seven Win Conditions. Importantly, it also serves to decide how those events will be prevented or mitigated.
The Three-Sentence Project Skinny is a concise summary of the purpose of the project. It addresses the what and the why.
You can't do everything, nor should you. This template helps you figure out what is in and what is out of your project.
These are the do-or-die, must-meet requirements in order for the project to be considered a success. As such, they are continuously focused on by the project manager and core team.
Win Conditions address how success will be measured. How do you stack up when it comes to stakeholder satisfaction, your schedule, scope, quality, budget, ROI and team satisfaction? This template helps you rank priorities, and provides areas for metrics and descriptions.
Learn From Others
Agile methods recommend co-location and face-to-face communications, but studies of office workers show high levels of dissatisfaction with open-plan environments. So, how do we make agile work and minimize the issues surrounding open-plan environments?
Did you know that agile has an explicit and core principle guiding decision making? You can’t be agile without following it. It’s called “deferring decisions to the last possible moment."
Is agile working for your team? Do standups feel like micromanagement? Are people missing commitments because they are spread across projects? If people are going through the motions of agile and aren't happy about it, use these five key questions to help.
Kanban has become popular in the software development world--but is used very selectively. Developers are missing real opportunities to better serve customers in both software operations projects and in new development projects. Here we cover the core principles of Kanban that can be applied to any project where improved quality and throughput are desired.
You’re a hardworking, successful business analyst (BA), and have just been told your organization is “going agile.” Perhaps you’ve heard a few details about the types of roles involved in an agile development environment, but nothing that really depicts how a BA fits into this new atmosphere. So what does this shift in your organization mean for you?
The number of agile certifications available in the market keeps growing, and one must consider the unique needs of the inquiring company or individual to know what would be best for them. What factors should you consider? Do you even know the options available?
Managing quality during a software development project can be difficult and time consuming when you have been misinformed about true quality indicators and practices. Actively managing quality on an agile project can be both simpler and harder than traditional approaches. Here are some basic practices to save time and unnecessary rework--and improve stakeholder satisfaction before and after delivery.
Project managers need to communicate effectively with all types of project stakeholders. For agile projects, this sometimes involves adapting traditional PM constructs into the closest agile alternatives. Agile pendentives are adaptive patterns that facilitate these traditional-to-agile discussions.
Agile approaches often have greater engagement levels between stakeholders. While those conversations generally focus on the deliverables and how they meet the customer’s needs, can they also drive sustainability best practices?
Agile does not enforce rigid processes, but organizations typically choose a guiding framework and a set of practices that serve as the starting point of an agile transformation. Executives typically want to know where teams are in terms of adopting these new ways of working. This article provides three techniques--individual, team and group--that can be used to assess the agile adoption level, monitor progress and drive improvements.
Ask a Question
|How can CPM be utilized within Agile Methodologies?||Larry Goldsmith||May 14, '15 2:44 PM||2||2|
|Agile and BI (or datawarehouse)||Hannes Kropf||Apr 22, '15 8:32 PM||2||2|
|Finding Past Recorded Webinars||Anonymous||Mar 29, '15 1:28 AM||4||4|
|What are your experiences working with large-scale agile projects in government?||Bill Brantley||Mar 13, '15 6:32 PM||3||3|
|Is Agile a right way to handle Re-engineering projects?||Krishnan Giri||Mar 12, '15 11:54 PM||5||5|
|Page: 1 2 3 next>||Mark All Read|