ProjectWorld and World Congress for Business Analysts blog seeks to bring together all levels of project management and business analysis expertise, from diverse industries and perspectives, across business groups and information technology. Our goal is build successful collaboration and share content, best practices, techniques, and networking.
Time: 2:00 PM - 3:00 PM EDT
Have you ever gotten lost when traversing through the IIBA® BABOK® 2.0? How quickly can you find pathways through the Guide? How easily can you trace your way from one key element to another? Whether you are new to the discipline of business analysis, someone studying for the CBAP® or even a seasoned business analysis professional, navigating through the BABOK® can be a daunting task.
In this webinar we’ll explore a variety of pathways through the BABOK. Your navigator for the session is requirements guru Mary Gorman, a four year veteran of the IIBA Body of Knowledge Committee.
IIBA® International Institute of Business Analysis®
BABOK® Business Analysis Body of Knowledge®
What you will learn:
Teams must adapt, but they can’t lose track of the ultimate goals of the project. Teams should constantly evaluate progress, whether adapting or anticipating, by asking these four questions:
James A. DiMarzio
Chief Information Officer
Mazda North American Operations
Since joining Mazda, DiMarzio has helped to set the strategy to implement a partnership with the business areas of MNAO to ensure alignment of information technology projects with the company's business strategy and goals. This strategy also promotes the search for opportunities to improve the efficiency of business operations through the use of cost-effective new technologies. Prior to working at Mazda, DiMarzio spent 12 years at Subaru of America in various information technology staff and management positions. Before working at Subaru of America, he spent five years with Land Rover as the general manager of information technology and two years with Agency Insurance Company as senior vice president and chief information officer.
DiMarzio has a bachelor's degree in Mathematics from Franklin and Marshall College, and an MBA from Rutgers University. He is married with three children and currently resides in Rancho Santa Margarita.
Biography courtesy of Mazda.
I conducted a workshop on the future of project management at IIR's ProjectWorld conference in Baltimore last week. Here is the brainstorming based on Microsoft's future of information work scenarios:
Proud Tower
Continental Drift
Frontier Friction
Freelance Planet
As Kathleen Barret said in her seminar on Business Analysis, “We are the lucky few who are allowed to get out of our businesses. The conference is much smaller this year.” In the opening remarks yesterday morning, IIR also commented that most people attending ProjectWorld are wearing both their Project Management hats and their Business Analyst hats. Today is the time to be a jack of all trades. The seminars were definitely more sparsely attended then previous years (only a 110 registrants as opposed to 300-400 in previous years), but the content was still strong and practical.
More snippets from the afternoon’s sessions:
Business Analysis: Helping Business Do Business Better, Kathleen Barret
How Agile Reduces Requirements Risks, Ellen Gottesdiener
If you’d like more about the seminar, you can find some Agile goodies here.
Evolving Role of the CIO: Asif Ahmad, VP Diagnostic Services & CIO, Duke University Health Systems
Peter thinks that we're in the most exciting field there is right now. Do you agree?
Ms. Washington came to DOT after spending 9 years at the Library of Congress as the Director of Integrated Support Services (ISS). She began her career at the Library of Congress in 1994 as Chief of the Photo duplication Service, which provides microfilming services for the preservation of all of the Library's collections. As Director of ISS, she managed support operations, which included contracts and logistics, printing and mail operations, health and safety services, and facilities operations. She was the Library of Congress Designated Agency Safety and Health Official (DASHO) and the Library's Emergency Manager. As the DASHO, Ms. Washington managed critical incidents, including the 9/11 and anthrax emergencies.
In August 1997, she was asked to develop the Library's Internal University (IU) to provide training and education programs for the more than 4,000 employees of the Library of Congress. The IU's mission is to improve the Library's productivity, performance, and service to the Congress and the American public by developing management and work force knowledge and skills that promote individual and organizational excellence in support of the Library's strategic objectives. Since developing the IU, Ms. Washington implemented a Library-wide training program entitled "Facilitative Leadership", a methodology that empowers staff to work together to achieve common goals. She is also a trained facilitator and master trainer.
Prior to joining the Library of Congress, Ms. Washington spent 12 years with Xerox Corporation holding various sales and marketing positions, the last of which was in management with Xerox Business Services where she demonstrated skill at achieving customer satisfaction while meeting business goals. While at Xerox, Ms. Washington also received the President's Club Award and the Par Club Award. The team she led won one of the highest Xerox awards, "Team Excellence".
In 2003, Ms. Washington was appointed by Secretary Ann Veneman of the United States Department of Agriculture to the Board of the Department's Graduate School. Ms. Washington was honored by the Washington, DC, Chapter of the Women's Transportation Seminar (WTS), as the 2005 recipient of their Diversity Award, in Recognition of Outstanding Leadership in Transportation. The WTS, founded in 1977, is an international organization dedicated to the professional advancement of women in transportation. Ms. Washington is the Vice Chair of the Local Federal Coordinating Committee for the Combined Federal Campaign’s National Capital Region. Ms. Washington also represents the Secretary of Transportation on the Federal Council on Arts and Humanities.
In October 2007, Linda Washington was selected by the President as a recipient of the prestigious Presidential Rank Award for her leadership, professionalism and commitment to excellence in public service.
And most recently in March 2008, Ms. Washington was honored during Women’s History Month with the President’s Volunteer Service Award.
Ms. Washington holds a bachelor's and master's degree from Morgan State University and the University of North Texas, respectively. She is a native of Annapolis, Maryland and has been married for 37 years to former Dallas Cowboy defensive back, Mark Washington. The Washington’s have one daughter, Lisa, who is married to David Noguera. They also have two granddaughters: Kaiya Alexis, and Reece Gabriella.
Thank you to the Department of Transportation for their gracious biography.
1. Management direction is inconsistent or missing. If project leadership has gone AWOL, chances are that things are starting to go in a bad direction. Or, even worse, if the directives you get from management (or feel compelled to give if you are management) change frequently, there's a problem. If a project either lacks direction or can't maintain a reasonably consistent course, it's unlikely to get to any desirable destination.
2. Project management and business management seem disconnected. Even if a project does get consistent direction, if that direction seems to be at odds with business management's desires, there's a problem brewing. In political battles between IT and business management, business management usually wins, even if it takes a while. I don't hear too many stories about the great political triumphs of IT managers over their users or clients.
3. The team lacks a commitment to clearly articulated and commonly understood goals. Every project has a goal or two. They may be clearly stated or only vaguely discussed, but it's rare for any business to shell out lots of money for something that genuinely has no purpose. That said, it's common to presume that the purpose of a project is so obvious as to not be worth articulating. That's unfortunate. It typically leads to misunderstandings and inconsistent presumptions about priorities. Eventually, poor and inconsistent tactical decisions undermine project progress.
4. Team members don't listen to one another. Even when teams get along personally, team members don't always listen well to one another. This tends to lead to chaos as people fail to coordinate activities and make the compromises necessary to enable projects to move ahead.
5. The team is in a state of discord. Teams sometimes break into competing camps. These can form around honest-to-goodness differences over project direction. They can also form over petty loyalties and personality clashes. Sometimes teams just descend into chaos, with multiple factions or an every-person-for-himself ethos. The state of discord is destructive to progress. It needs to be rooted out. Sometimes, as a manager, you can engineer a reconciliation. Other times, you need to pick winners and losers.