Agile approaches promote development teams comprised of generalizing specialists and seem to ignore the BA role. This begs the question: Do BAs have a role on agile projects? And if so, how do their functions change? This article examines their new role, what changes and what stays the same.
Connect In Person
Advance your BA skills. Earn PDUs and more—all for free. Don’t miss the most popular Business Analysis event of the year! Over 13,000 attend. Registration is FREE. We’re sharing career journeys and talking about the hottest BA and agile BA topics. Register now to attend the only event designed with your future in mind to help you get ahead.
Is Your Agile Transformation Set up to Fail? Find out at the PMI® Organizational Agility Conference 2016, FREE and Exclusive for PMI Members. We know there are barriers that slow your organization’s ability to be agile: failed agile transformations, complex organizational processes, team dynamics and the uncertain role of the PMO in an agile environment (just to name a few). Attend the PMI Organizational Agility Conference 2016 to get help breaking down these barriers. It’s free for PMI Members.
Overwhelmed by how technology is transforming project management? Looking to increase your productivity and learn new tech tools but don't know where to begin? No matter what your focus—medical, manufacturing, product design or otherwise—this virtual day of learning will deliver years of enduring value, with exclusive insights on how project managers are using new technologies.
The debate over Waterfall and Agile is the wrong debate. Is project management ready for the Tsunami?
This is the final session in our six-part How to Be a Project Hero series. In this session we will discuss how to bring all the pieces together in a LEAN plan and share some techniques on tracking against that plan.
The journey to Adaptive and Servant Leadership is a long one, it doesn't happen over night and it takes conscious effort to get there. I want to share some of the best tips we've learned from the real world on how to navigate this journey and help others do the same.
Larry Cooper recently approached a group of senior leaders from a broad spectrum of industries, sectors and countries to participate in a Wisdom Council to answer a series of questions on Organizational Agility. In the webinar Larry will share the insights he gathered from them.
In case you actually read this description, the beginning of the blog is about preparing for the PMP exam. It then evolved into maintaining my credential. After taking a break for a few years, I'm back and will be blogging about project management, in general, and probably a bit of agile on a regular basis.
The Agility Series focuses on agile and agility across the organization not just in software and product development. Areas of agility that will be covered in blog posts will include: - Organizational Agility - Leadership Agility - Strategic Agility - Value Agility - Delivery Agility - Business Agility - Cultural Agility - Client Agility - Learning Agility
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
When companies move to an agile Software Development Lifecycle (SDLC), they often remove the processes and analysis of their waterfall SDLC because, as the Agile Manifesto puts it, “They value individual and interactions over processes and tools.” Some of the rigor should be removed – waterfall processes can get bogged down with gates and sign-offs. However, caution must be exercised to not go too far against processes and analysis and rely just upon backlogs and user stories. Requirements and the analysis that leads to those requirements are just as essential in an agile project as they are in a waterfall project. The difference lies in how much requirements analysis is completed and the timing of it.
If you adopt the agile approach, it will affect every aspect of your work. Learning it will be challenging for you, your team and your organization. The learning process will take months or even years; during this time, you still need to produce results. After 20 years of agile’s existence, do we know of a reliable, effective way of learning it?
It took this practitioner a while to find her footing as both a project manager and ScrumMaster. Here, she shares lessons learned in a large, corporate environment in which agile is considered "new."
Following installments on the other four stated Scrum values (courage, focus, openness and commitment), this concluding entry focuses on respect. It offers techniques to scrutinize agile project management frameworks based on values, principles and practices.
To rise above the competition requires tenacity, veracity and intangibles that organizations need to respect, comprehend and practice. Business success is cultivated through sound project management practices, which include business rhythm, organizational intangibles, organizational development, project production, project delivery and a project management team. These key ingredients, when working together, guarantee project success.
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment in this series, we take one of the most commonly used visual models in agile and explain how to create one and how to use one to help build, groom or elaborate your agile backlog. This installment looks at business data diagrams.
Is agile the tsunami of change? Not necessarily, but the wave of change is coming to our profession. This practitioner warns that it won’t hit us like a waterfall—it will hit us like a tsunami. Will you be ready?
The agile approach needs to be understood thoroughly before it is introduced to a company. This explanation will give leadership the information they need for deciding if agile project execution is right for their organization by discussing key points including core framework, high-level benefits, and risks in the project-based environment.
When should you use waterfall and when should you use agile? The usual answer to this question is vague: Apply each approach according to circumstances. This article discusses the main positive and negative aspects of the waterfall and agile approaches, deconstructing some of the myths behind them and suggesting where one could be used over the other according to different factors.
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment in this series, we take one of the most commonly used visual models in agile and explain how to create one—and how to use one to help build, groom or elaborate your agile backlog. This edition looks at the business objectives model.
For many, the concepts of agile are distinctly related to software development. But there has been a trend over the past 15 years of agile approaches taking root outside of software development and systems integration projects. Agile has not only appeared outside of its usual places, it has thrived in many of these new areas.
Today, roles have changed. As a project manager, you must keep your projects (and developers) on the right track. It doesn’t matter how many languages or platforms you know. This seasoned practitioner explores two different approaches and applies them to a complex IT scenario, looking at the best of both worlds.
Many organizations are obsessed with getting things done quickly no matter what. Therefore, they create reward plans that motivate this behavior. ScrumMasters gradually deprioritize promoting Scrum values and metamorphose into agile project managers. How can we prevent this?
Most organizations struggle to engage their workforce to its potential. This is not through a lack of planning, technical skills or resources, but instead effective tools for dealing with typical project problems. Fortunately, agile practices hold many practical solutions for solving the classic five dysfunctions of a team.
This fourth installment of articles scrutinizing agile frameworks based on values, principles and practices focuses on commitment (following the entries on courage, focus and openness). A stated value of the Scrum framework, commitment is everything in agile.
What does “scaling agile” mean to you? There are two ways to think about scaling: one is moving from one project to a program, the other is sharing agile across the business. Here we talk about moving from a one-team project to agile programs.
Ask a Question