Showing posts with label scrum. Show all posts
Showing posts with label scrum. Show all posts

Wednesday, July 29, 2015

Finding the Right Project Management Methodology for You

By: Kazon Robinson

Projects are formulated and produced by organizations to gain profit and expand the organization. Every project formulated, whether it is big or small, needs some form of planning because without planning, a project could result in failure.

Fortunately, there is a way to go about that business of creating an outline for a project - Project Management Methodology (PM).  Today, there are various PM methodologies and author Moira Alexander addresses a few very well in her recent article, “How to Pick a Project Management Methodology”. Specifically, three methodologies that stand out from the rest are Agile, Waterfall, and Scrum.


Agile: Alexander writes, “The Agile Methodology was developed for projects requiring significant flexibility and speed… Agile may be best-suited for projects requiring less control and real-time communication within self-motivated team settings.” So, a possible recommendation would be an open space office where communication is faster paced and thoughts are able to exchange faster.

Waterfall: “Used across many industries, most commonly in software development. Waterfall allows for increased control throughout each phase but can be highly inflexible if scope changes may be anticipated later,” according to Alexander. The Waterfall methodology is used for more complex projects being as there is a need for more control throughout to handle the complexity.

Scrum: Scrum is an agile development framework that is more so used for software development but is now generally used in complex projects.

In addition, there are many other PM Methodologies such as Critical Chain Project Management (CCPM), Six Sigma, Crystal, or Feature Driven Development (FDD). This amount of various methodologies helps organizations settle on a certain way of performing a project whether it is complex or simple.

Every methodology works in a business, some work better than in others depending on the situation and if the situation does not always fit the project methodologies framework it can lead to undesirable results. Nevertheless, no project is the “best of the best” and Alexander explains what to look for in a methodology. “When evaluating methodologies, these are only a few of the many factors that should be carefully considered: risks, complexity, constraints, project size, and cost…” Those are some of the factors to consider when looking at different project management methodologies.

In the end, what needs to be focused on is how projects improve or better the whole organization’s objectives. Once you determine the success or failure of those goals, look for the best methodologies that suits your organization’s needs.


About the Author: Kazon Robinson is currently a Marketing Intern at IIR USA and a high school student at All Hallows. Kazon helps oversee and revise the data entry of spreadsheets with information relating to investors, twitter handles, and conferences. He also has experience interacting with other writers from participating in the AH Writers and Authors Club. He has previously worked at Bronxworks Betances Community Center as an Office Assistant where he provided professional service and directions for callers. He can be reached at krobinson@iirusa.com

Wednesday, August 14, 2013

Top PM Trends of 2013: Agile will be Viewed as a Failure for the Wrong Reasons

“Trying is the first step to failure” is probably not a motto you want to live your life by, but all too often it’s true in the Agile world. But why?

According to Mark Bashrum, VP of Strategic Intelligence & Corporate Marketing at ESI International, in 2013 Agile implementation will be viewed in some organizations as a failure, but for the wrong reasons.

When it comes to project management, studies prove time and again that Agile can help reduce cost, speed time to market and improve quality. Still, in 2013 many organizations will continue to fall short in realizing the Agile promise. Among the reasons, the professionals assigned to Agile projects simply aren’t trained in its use. And, organizations are not culturally ready to embrace its principles.

“You can’t just train a few scrum masters and call it a day,” said Bashrum.

The team including developers, testers and product owners need to know how the method works and how to break down the cultural barriers to adoption.

Check out the full video below:



Want to hear all about project management from the experts in person? Join me at ProjectWorld & World Congress for Business Analysts in September! For details on the event, click here: http://bit.ly/19e2rDb


Amanda Ciccatelli, Social Media Strategist at IIR USA in New York City, has a background in digital and print journalism, covering a variety of topics in business strategy, marketing, and technology. She previously worked at Technology Marketing Corporation as a Web Editor where she covered breaking news and feature stories in the tech industry.  She can be reached at aciccatelli@iirusa.com. Follow her at @AmandaCicc. 
Enhanced by Zemanta

Wednesday, May 15, 2013

Top Business Analysis Trends of 2013: Forget Consensus, it's About Collaboration and Convergence


Requirements in the form of a user story are all about the business analyst focusing on delivering convergence vs. collaboration and consensus. The new trend of collaboration and consensus is a way to get everybody on the same page, but it takes a long time to be able to get those requirements developed.

“Remember, in agile from a BA’s perspective user stories are supposed to be there to deliver value that provide a way for everybody to converge on the same path so that you can deliver every four to six weeks. That’s the package and the focus of what agile is all about,” said Nancy Yee, vice president of Global Product Strategy, ESI International,.

In 2013, Nee thinks we will begin to see that the BA’s are going to need to focus their elicitation skills more on convergence than on consensus. To get there, BAs can focus on collaboration and choosing the elicitation methods that will bring everybody into that convergence path.

Check out Nee’s full video below:



Nee is presenting a webinar next week entitled, "Developing Effective Agile Requirements." To register, click here! 
Enhanced by Zemanta

Tuesday, May 7, 2013

Top Business Analysis Trends of 2013: Strong User Stories Will Drive Effective Requirements Analysis

Now more than ever, businesses of all shapes and sizes require effective business analysis to be successful in this highly competitive business world. Business analysis involves taking information gathered from a variety of sources and analyzing to forecast future trends, finding ways to make improvements in business strategies, improving operations, and making strategic decisions to improve the overall bottom line.

Moving through 2013, according to Nancy Yee, vice president of Global Product Strategy, ESI International, there are key business analysis trends that will be prominent and that businesses should embrace this year. The second significant business analysis trend of 2013 is strong user stories will be the force driving effective requirements analysis and product backlog prioritization

If the BA is already working with the product owner the BA needs go back to the roots of what they know, being able to elicit and analyze requirements in the form of a user story.

In 2013, BAs must return to the grassroots of what you know in requirements management development and get in sync with your inner elicitation and analysis requirements, focusing on the perspective of developing user stories.



“Using what you already know from an analysis standpoint, you will create successful user stories that will help your product owner prioritize their product backlog and deliver value at every iteration,” she commented.

Be sure to register for Yee’s upcoming webinar, Developing Effective Agile Requirements. Click here for more information:  http://bit.ly/10haSfj

Enhanced by Zemanta

Tuesday, April 30, 2013

Top Business Analysis Trends of 2013: BA and Product Owner Roles are Solidified


Today, businesses require effective business analysis in order to be successful in a competitive business world. Business analysis involves taking information gathered from a variety of sources and analyzing to forecast future trends, find ways to make improvements in business strategies, improve businesses operations, and make smart business decisions to improve the bottom line. Understanding key marketing areas is essential to helping a business generate revenue and cut down on excess waste. 

According to Nancy Yee, vice president of Global Product Strategy, ESI International, there are some key business analysis trends that will be prominent in 2013. The first significant business analysis trend of 2013 is the roles of the BA and product owner will be solidified and respected.

In an Agile environment, the BA and the product owner have very different roles. The BA works with the product owner to identify what exactly they need, help them understand how this is going to help them achieve the values that they are looking for. The product owner, on the other hand, is responsible for understanding exactly what the business needs.

“They are there to talk about how, where and when they need to improve their businesses, which translates into the product backlog,” said Yee.

In 2013, there is going to be a stronger relationship with the product owner and the BA together in order to create a stronger foundation of understanding of what they need to be able to deliver value when it comes to priority of the product background.

Check out the full video here: 



Be sure to register for Yee’s upcoming webinar, Developing Effective Agile Requirements. Click here for more information:  http://bit.ly/ZXGbaa

Enhanced by Zemanta

Friday, April 19, 2013

The Top 10 Business Analysis Trends of 2013


Today, businesses require effective business analysis in order to be successful in a competitive business world. Business analysis involves taking information gathered from a variety of sources and analyzing to forecast future trends, find ways to make improvements in business strategies, improve businesses operations, and make smart business decisions to improve the bottom line. Understanding key marketing areas is essential to helping a business generate revenue and cut down on excess waste.  According to Nancy Yee, vice president of Global Product Strategy, ESI International, there are some key business analysis trends that will be prominent in 2013.

1. The roles of the BA and product owner will be solidified and respected.

In an Agile environment, the BA and the product owner have very different roles. The BA works with the product owner to identify what exactly they need, help them understand how this is going to help them achieve the values that they are looking for. The product owner, on the other hand, is responsible for understanding exactly what the business needs.

“They are there to talk about how, where and when they need to improve their businesses, which translates into the product backlog,” said Yee.

In 2013, there is going to be a stronger relationship with the product owner and the BA together in order to create a stronger foundation of understanding of what they need to be able to deliver value when it comes to priority of the product background.

2. Strong User Stories will be the force driving effective requirements analysis and product backlog prioritization

If the BA is already working with the product owner the BA needs go back to the roots of what they know, being able to elicit and analyze requirements in the form of a user story.

In 2013, BAs must return to the grassroots of what you know in requirements management development and get in sync with your inner elicitation and analysis requirements, focusing on the perspective of developing user stories.

“Using what you already know from an analysis standpoint, you will create successful user stories that will help your product owner prioritize their product backlog and deliver value at every iteration,” she commented.

3.  Forget consensus, in 2013 it’s all about collaboration and convergence

Requirements in the form of a user story are all about the business analyst focusing on delivering convergence vs. collaboration and consensus. The new trend of collaboration and consensus is a way to get everybody on the same page, but it takes a long time to be able to get those requirements developed.

“Remember, in agile from a BA’s perspective user stories are supposed to be there to deliver value that provide a way for everybody to converge on the same path so that you can deliver every four to six weeks. That’s the package and the focus of what agile is all about,” Yee said.

In 2013, Yee thinks we will begin to see that the BA’s are going to need to focus their elicitation skills more on convergence than on consensus. To get there, BAs can focus on collaboration and choosing the elicitation methods that will bring everybody into that convergence path.

4. BAs will become the new PMs through Agile

BAs will become the new PMs. From the Agile perspective, project management disappears and we focus on project leadership, project delivery, project execution. The role of the BA in agile is about delivering value from the user story perspective. “The role of a project manager become obsolete? Maybe, maybe not. Only time will tell,” she said.

In 2013, the focus of the BA will be more on upscaling themselves in the traditional role of what we know as PM. They will learn the skills of scheduling, planning, managing risk, controlling costs – so that they came become the new PMs of an Agile project.

5.  BAs will be seen as the keystone to adopting Agile

At its core, Agile is all about requirements from the perspective of user stories, according to Yee. In 2013 if organizations are going to embrace Agile, they need to focus on the keystone to success of Agile, which is business analysis.

If they don’t have a current business analyst role, they will at least embrace the function of business analysis because at the end of the day Agile success is all about requirements and that is what BAs do because they are able to define user stories and be able to deliver value which is what Agile is about.

6. The federal government will slowly recognize the value of business analysis as it moves more toward an Agile environment

Requirements management and development is a concern in the government. Although state and local governments have embraced the role of BA, the federal government hasn’t fully embraced that function.
However, in 2013, when the government is focused on Agile and delivering things in a modular fashion they will begin to see the value that requirements management will lend itself toward embracing the role of BA. In 2013 from a government’s successful usage perspective, we will see a critical eye on a key role of investment in looking at the BA role to define user stories and deliver value.

7. Strategic Enterprise Analysis will slowly become the foundation of business architecture

These days, with budgets so tight, there is a focus on strategic enterprise analysis – the foundation to organizations that are embracing business architecture.

“It’s all about: How do we grow our business? Make our business more money? How do we keep our business stable? All of these things are about the BA and the ability to do strategic enterprise analysis,” Yee explained.

We will begin to see that as organizations are able to work in the space they are trying to deliver their products with greater uptake to be the next Apple or Microsoft, for example. They will be looking at strategic enterprise analysis and business architecture together for its all about defining the “what” of business and how we can deliver customer value.

8. BA Centers of Excellence will focus on providing their worth and driving innovation

In 2011 and 2012 we saw the resurgence of BA COEs. We saw that many organizations were establishing those centers of excellence. Now in 2013, we will see the trend of those COEs staffing up their ability to deliver the value and innovation that they promise to have in place.

This year we will see senior BAs and business architects joining the ranks of showing the innovation and value because it is all about understand exactly what your business does, how you should invest in it and be able to prioritize the value from a requirements and product perspective.

9. Modeling skills take precedence in business analysis training

In 2013 is all about pictures, graphics or models. What you will begin to see is that the BAs are going to be using and leveraging all of the different models and modeling techniques they know to be able to deliver the messages they need. For instance, user stories require the use cases to be able to develop the value the customer is looking for. Process models are a way to understand how the organization as a whole is going to be able to deliver what they are looking for and add operational effectiveness and across the board.  
In 2013, will we see the written word disappear?

“I hope not, but pictures speak a thousand words so 2013 BAs should get focused on practicing your modeling skills and techniques because the model is going to pay the rent,” said Nee.

10. Communicating “up” will become critical to articulating requirements’ impact on a deliverable.

In 2013 we will see BAs learning that they have to communicate better, meaning that communicating up and across is going to be a major focus of what BAs are going to be targeting in 2013. BAs are the most aware of the requirements of the value those requirements bring because they do a lot of impact analysis on those requirements.

She added, “When they are working on a project they know if they miss a requirement or if it changes, and how that will affect the business. The problem is the ability to share that difficult message and have that crucial conversation.”

In 2013 BAs will be focused on their ability to have those communicating up conversations with their sponsors and stakeholders, laying it out for them of what could happen when it comes to these requirements.
“By being able to put that in your bag of BA skills, you are solidifying yourself as a key component to everything related from a business value standpoint,” Yee concluded.

Business analysis is a big part of the upcoming conference , ProjectWorld & World Congress for Business Analysts (PW&WCBA), which blends practical learning, skill building, big picture thinking and leadership training together for a holistic approach to developing managers into leaders.

Whether you are looking to sharpen your toolkit, grow as a leader or benchmark against peers by exchanging stories of success and failure, this event delivers it all – providing you with more credits than any other event of its kind. With a huge  network of experts and peers to connect with, you'll be prepared to confront the Increasing complexity even more confidently with dexterity and agility.

To register for PW&WCBA, click here!


Enhanced by Zemanta

Tuesday, November 13, 2012

Insights from PW&WCBA: Solving The Puzzle With Scrum

As we move forward from the 2012 PW&WCBA event, we'll be looking back at some key lessons learned and trends that popped up during our sessions and sharing some of the takeaways presented in our exclusive Executive Summary. If you attended the event, you may download the executive summary document on Crowdvine.

Puzzling
Via Flickr user Jhritz
One of our most popular sessions at PW&WCBA 2012 was "Agile Essentials: People Planning, and Product Practices" with Ellen Gottesdiener, Founder, Principal Consultant, EBG Consulting, Inc.

At one point during this session Gottesdiener briefed our audience on some of the essential components of Scrum Methodology such as:
1. Product Backlog – The backlog consists of pieces of the overall product. The product backlog is always changing according to customer requirements. The product champion prioritizes the backlog for the team.

2. Sprint Backlog - The spring backlog is the objectives of the current sprint. This backlog is created by the team as a whole and is fixed once the sprint begins.

3. Sprint – The sprint is a short time period in which the team focuses on the sprint backlog which contains small pieces of the overall product backlog. The sprint produces a working iteration of the final product. Any items not finished during the sprint go back into the product backlog to be finished at another time.

But if you (or the stakeholders that you need to convince) are new to Scrum Methodology you may find yourself struggling with the terminology and jargon. In our 2012 executive summary, author Victor A. Lopez wrote the following, and I think it's an important, simple selling point for Scrum:
"The Scrum methodology allows teams to break down the product into small, manageable pieces instead of being intimidated by the larger puzzle."
Looking at the jigsaw photo above, you couldn't say what the end result will look like, and you might find it quite challenging to try and assemble the puzzle. Many would give up without giving it a shot, and others would get frustrated without guidance after the first attempt.

Using a methodology such as scrum helps all the moving pieces of your project puzzle fall into place. In Scrum, the product champion can see the big picture and prioritize tasks for the team, just as you may choose to, say, assemble the edges of the puzzle first.

We'll be publishing insights from attendees of this year's PW&WCBA event over the next several weeks. Would you like to share your thoughts or this session or any others? Email them to Michelle LeBlanc at mleblanc@iirusa.com.

Friday, July 13, 2012

Friday Flicks: Why is communication so darn hard?

Earlier this week, guest blogger Peter Sloane commented here about communication challenges, and particularly the challenges that can arise as schedules and attitudes become more casual for summer.

Here in the PW&WCBA headquarters we recently missed a project team scrum meeting as so many members of the team were out on various July-4th-related holidays. Luckily it's a slower season, but what if an important deadline was missed or something slipped through the cracks as the scrum meeting went by the wayside? Part of our problem is, the team is just too big, if we kept the main meeting as a "scrum of scrums" and had smaller project teams meet separately scheduling issues wouldn't be quite so difficult.

Appropriately, PW&WCBA favorite Joseph Flahiff tweeted this illustrative video this morning: How do you deal with large project teams? Michelle LeBlanc is a Social Media Strategist at IIR USA and the voice behind the @Project_World twitter. She may be reached at mleblanc@iirusa.com