Showing posts with label Agile software development. Show all posts
Showing posts with label Agile software development. Show all posts

Thursday, December 3, 2015

Free Webinar: The Mental Game of Project Management

Join Lou Russell, CEO/Queen of  RMA, for an upcoming webinar, “The Mental Game of Project Management.”

Russell is a consultant, speaker and author who grows companies by growing their people. She is the author of 7 books including IT Leadership AlchemyLeadership Training ,10 Steps to Successful Project Management and Managing Projects. Through speaking, training and writing, she inspires leadership, project management and team growth. Her upbeat style will give you the passion and tools to improve. Laughing, participating, and challenged, you will learn. 

Register for the webinar here: http://bit.ly/1TnwGx8

Webinar Summary:

Tiger Woods will be remembered as an exceptional golfer.  His legacy may also be that he made a big mistake and never returned back to his greatness – time will tell.  Why do you think he still remains so far from his earlier abilities?  His clubs?  His coach? His health issues? Everyone Russell asks says “it’s all in his head.”  As a very rookie golfer, Russell is fascinated and appalled by the way her mind gets in the way of my game.  She is aware that her mind also gets in the way of her success in life and business, including projects.  She actually speaks more negatively to herself through her self-talk than anyone else has ever spoken to her.  So do you.
In business and organizations all over the world, we jointly agree to certain truths (that are actually lies) including:
·         You must always be in control of a project to succeed
·         It is possible to predict the future accurately if you’re talented
·         Projects are impossible to do on time and on budget with appropriate quality because of all the jerks involved
·         The politics of the organization have no place in a project
·         People should do what they say they are going to do
·         She can personally torture people enough to get a project done

We bet you can pick a couple of these that you believe, in fact, that you make choices based on.  Now that you read them, you may be starting to notice that these ‘truths’ are preventing you from being agile, resilient and collaborative. These are the truths that we pretend to not see. To drive outcomes requires new truth.  In this Reflections with the Masters Series, Russell wants us to all have a conversation:

·         How are our current truths, self-talk and values moving us away from the outcomes we strive to achieve?
·         What are the strategies for noticing my own disconnects before they trigger fear and stress as auto responses?
·         What are the strategies for reframing and distracting our brain to drive success?
·         How does all of this change the way projects are done and increase their success?

Russell is excited about the opportunity to create community virtually to drive hope, energy and joy in all aspects of your life.  Together, we’ll create new truth.  She’s hoping Tiger will create new truth, too.


Save your seat for the webinar: http://bit.ly/1TnwGx8

Tuesday, July 22, 2014

Agile State of Mind


Are you wondering how to choose which project management method to deliver a successful project? Organizations today have to be more competitive in the marketplace so choosing the best practices and methods for your organization and projects is important. Agile is a set of values and principles, not a pre-defined process with obvious areas of limitation. Waterfall is a model based on development method that is linear and sequential.

Here are four criteria to choose the best fit of methodologies at the right time for the right customer.

1. Time to market projects – Agile adoption has replaced waterfall in organizations in the delivery of small, yet frequent pieces of functionality where requirements are expected to evolve, change is embraced, competition in the marketplace is a key concern, and critical to delivery of the latest technology. I.e.: medical device manufacturing, military/aerospace.

2. Status quo – Waterfall is a better choice for organizations that are not flexible, have clearly defined requirements, frequent interactions with end users and other stakeholders is a constraint or when there is risk of key developers quitting the project midway.

3. Success criteria – The success of a project that is defined by delivering business value will benefit from agile methodology. The success of a project defined by measured by KPI of the IT organization would be better suited with a Waterfall methodology.

4. Organizational Project Portfolio – Organizations that have a diverse portfolio must be both risk adverse, innovative and take some risks to be competitive.  Choosing a hybrid approach to use a blend of both methodologies would be beneficial. Planning, requirements and team communication are areas in which organization are designing custom best practices/ methodologies that fit their culture.



Action Items to Help You Get Started:

> Choose your methodology wisely; make sure your project team can adapt to the change and lead using the right best practice methodology or a hybrid approach.

> Focus on team member selection – Resources on an agile team can thrive by co-locating in common areas or resources can struggle due to intense and constant interactions which may create stressful team dynamics.

> Leadership Support – all projects need great sponsors, buy in from the business for implementing IT standards and methods and support for product service delivery using a big bang approach to smaller iterative delivery cycles.

Ultimately, a hybrid approach of traditional waterfall and agile elements make be your key to success. A hybrid approach can help an organization leverage talent and deliver business value early and often for software development projects.

ProjectWorld & World Congress for Business Analysts 2014, is taking place in Seattle, Washington September 22-24th at the W Hotel. The 2014 program is designed with courses for all training levels, a robust agenda, and most importantly tangible lessons which you can begin implementing the day you return to your office, making you even more valuable to your organization. PW&WCBA offers attendees 36 PDU/CDUs - that's more than half of the required credits necessary to maintain your certification in just one place.

To learn more or register for the event, click here: http://bit.ly/1jtZtxB
- See more at: http://www.iirusa.com/projectworld/speakers.xml






Tuesday, July 30, 2013

PW&WCBA Speaker Spotlight: Malgorzata Kusyk

In our brand new Project World and World Congress for Business Analysts 2013 Speaker Spotlight series, Malgorzata Kusyk, PMP, Senior Project/Program Manager at Thomson Reuters, recently sat down with us to discuss what it takes to be a great project manager and business analyst in an environment that is growing increasingly competitive every day. Here is what Kusyk had to say:

IIR: How do you, as a PM or BA, stand out in a crowd in this competitive business world?

Kusyk: Today slow economic growth, shifting global market priorities and a push for innovation all make for a very complex and risky business environment and put additional emphasis on the need for excellence in project, program and portfolio management.  Research conducted with senior project management leaders on PMI’s Global Executive Council found that the most important skill for managing today’s complex projects and programs is the ability to align the team to the vision of the project and design the project’s organizational structure to align people and project objectives.

I have been managing very complex projects and some of them were very successful and the other ones struggled, not because there were more difficult but because there was no social engagement and collaboration between stakeholders. The shift from micromanagement and looking at the project from a task perspective to team empowerment, self-organization, self -motivation, trust, authority and ownership are the key to success of today’s complex and risky projects. So, I put a lot of effort to build a collaborative environment, that means ownership of shared goals, links with a purpose and commitment to one another’s success (T.E.A.M = Together Everyone Achieves More).

IIR: What are characteristics of a GREAT project manager?

Kusyk: Projects are people not equipment or PERT diagrams, so for me the most important competency of a great PM is people focus. A great Project Manager builds relationships, is  interested in others’ success,  is emotionally intelligent, gives positive and constructive feedback, coach and teach other to perform their best, is exceptional communicator and listener and provide formal and informal recognition.

Moreover, focuses on process and  outcome, and by that  I do mean “task focus,” control or micromanagement, but rather keeping himself and team on track and motivated (trust). And last but not least is a learner by nature – demonstrates attitude “what can I learn?” rather than “who’s to blame?” recognize and respect cultural differences etc.

IIR: What are some tips you would suggest to someone who is just learning Agile?
Kusyk: Agile is…
  1. Mind shift. Agile is about a fundamental shift in thinking - Agile is not a process is a mindset! There is a good presentation on this topic by Bob Hartman– Doing Agile isn’t the same as being Agile. The essential point is that we are “Doing Agile” when we follow practices and we are “Being Agile” when we act with an Agile mindset – set of values and beliefs defined in Agile Manifesto. 
  2. Not a “silver bullet”. According to the survey results and recommendations presented in Agile Maturity Report – Benchmarks and Guidelines to improve your effectiveness,” a broken waterfall based project execution approach is not sufficient reason to commit to Agile. Agile is not a “silver bullet” or a solution to a mission critical initiative without any background in the approach. Agile will expose problems such as team dysfunctions. It doesn’t always fix them, but visible problems tend to be easier to solve.
  3. Bridging the gap between IT (or other departments) and the business.
  4. Business/Feature driven versus traditional task/activity driven.
  5. About self organization! Self organizing team makes decisions, commits to the work that they have to do, has few specialized roles, is cross functional, and organizes its own work.

IIR: How do you as a PM or BA build leadership skills?

Kusyk: First, we need to define the leadership skills? IBM study reveals that creativity is the most important leadership quality followed by integrity and global thinking  (1500 corporate leaders, from 60 nations and 33 industries were pulled on what drives them in managing their companies in today’s world). Creative leaders are more prepared to break with the status quo of industry, enterprise, and revenue models. 

So how do I unlash creativity, build integrity and think globally? 

  1. I support and reword creativity &  innovation. I’m open to new ideas and give the team freedom to try new ways of working or new tools or processes.
  2. Build trust and high level of honesty – I trust people until I’m proven wrong. 
  3. Find or create some rituals or common symbols – special designed t-shirts, morning coffee together.
  4. Create positive work environment.  Add some fun to work – integration/team building activities, interviews with team members on their passions, hobbies or achievements (both from work and outside).
  5. Formal and informal celebration. Birthdays, milestone/project accomplishments.
  6. To understand the cultural differences and make relationships I try to visit a country where my team members are based – very often at my own expenses. If cannot effort a visit  try to find out more on cultures through reading, speaking to people or visiting a restaurant representing the ethnicity of a team member.
  7. Coach and mentor rather than control.
  8. Focus on personal development and knowledge sharing – encourage team members to  taking part or speaking at conferences and then sharing the knowledge and experience with others.

IIR: How does a successful PM communicate?

Kusyk: Clear communication is the most important ingredient of managing projects. A  successful project has a communication strategy in place. I find a Communication Plan as a very powerful tool and use it extensively. For me it’s crucial that there’s not too much, not too little, but just enough communication in my project, that’ why it is so important to find out what are the needs and preferences of the project stakeholders with regard to communication. A good Communication Plan includes but not limited to: kicking off a meeting, defined roles and responsibilities, project status meetings and frequency, identifying project communications, defining the level of detail to the level of management, developing communications standards and project de-briefing.

Stay tuned for more upcoming expert interviews right here on the PW&WCBA Blog.  

Kusyk is a speaker at the annual PW&WCBA 2013 in Orlando, FL in September. To register for the event, click here: http://bit.ly/13sfECq

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

Tuesday, June 4, 2013

Top Business Analysis Trends of 2013: The Government will Recognize the Value of BA as it Moves Toward an Agile Environment

These days, businesses require effective business analysis in order to be successful among the competition. To do so, business analysis involves taking information 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.

According to Nancy Yee, vice president of Global Product Strategy, ESI International, there are specific business analysis trends that will be prominent in 2013. We have gone over five of them in our previous posts. The sixth key BA trend this year is about how the government will slowly, but surely, recognize the value of BA as it moves towards a more 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.

Check out Nancy's insight on the trend in the video below:


Enhanced by Zemanta

Tuesday, May 28, 2013

Top Business Analysis Trends of 2013: BAs Will Be Seen as the Keystone to Adopting Agile

Modern businesses require effective business analysis in order to be successful in a competitive 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 Nee, vice president of Global Product Strategy, ESI International, there are some key business analysis trends that will be prominent in 2013.

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.

Check out Nee’s entire video below:


Want to learn more about how BAs will affect Agile business this year? Attend Project World & the World Congress for Business Analysts in September: http://bit.ly/14Vo3Bh

P.S. Listen to Nee’s archived recording of her recent webinar entitled, “Developing Agile Requirements.” To hear her interesting insights on PMs and BAs in agile, click here!

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, 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