So often in advanced project management circles we talk about rigorous, complex tools, processes and methods which allow us to tackle the most difficult projects. We acquire and train ourselves with the latest version of tools such as Project server or Primavera. We become the champions of developing a myriad of rich artifacts from charters, scope statements, and work breakdown structures to schedules, budgets, communication plans, and risk registers. We are prepared to employ sophisticated project management methods like qualitative and quantitative risk assessment and earned value. So then what happens if suddenly some or all of those things don’t apply? › Continue reading…
Archive for 'Planning'
Tags: Simple Planning
In my last article on risk, I discussed qualitative and quantitative analysis which allows a team to assess probability, impact, and monetary value of the risks identified. This allows a project team to develop priorities for those risks that require further planning and threat mitigation or opportunity realization strategies. In this article we’ll discuss how to develop risk response strategies › Continue reading…
In my last article on risk, I introduced how to get started with project risk management through risk planning and identification. In this article we’ll discuss how to evaluate and prioritize those risks for action through qualitative and quantitative risk assessment. › Continue reading…
In our last post, Susan discussed the top project management stories of 2010, and in that article concluded that risk planning was one of the major take away lessons of the year. When we look to past news-worthy project stories such as the BP oil spill disaster, the Carnival cruise ship Splendor nightmare, or the delays of the Broadway production of Spiderman, risk management emerges time and again as a leading factor for better outcomes. So why don’t more projects and organizations embrace it? › Continue reading…
Here is my list of the big project management stories of 2010 and what lessons they offer for project managers. At a glance, I think risk planning and perseverance are the take-aways. › Continue reading…
Undoubtedly, the masters would agree hands down that the recommended approach for any project team practicing agile methods would be co-location. The benefit of this arrangement is all the casual conversation that team members naturally tend to engage in, or are forced to overhear from their co-workers, which in turn promotes collaboration on the project – or so the theory goes. Unfortunately with the fabric of today’s multi regional, global, or outsourced organizations, co-located teams are not always an option. › Continue reading…
In my last article I discussed characteristics and roles of the agile scrum methodology as compared to waterfall. In this continuation article, I committed to examine the artifacts, meetings and processes involved and also discuss what they compare to in a waterfall context. By design agile and the scrum methodology deliberately minimize processes, artifacts and meetings › Continue reading…
In my final article on requirements development, I want to discuss the processes involves in eliciting requirements from business stakeholders. There are several commonly held techniques that are used for gathering requirements from business customers. Some of these methods are specific to software systems or systems with some type of user interface, and some are applicable to › Continue reading…
I am on vacation in Taos, New Mexico this week with my husband and 15-year-old nephew, Evan, who spends every summer with us. We are staying in a very nice condominium and having lots of adventures: a llama trek, river rafting trip, horseback ride, visits to the Taos Pueblo and various art galleries, restaurants, historic markers and other areas of interest. Like any good project manager, I spent a considerable amount of time planning for this trip. I did a lot of research on places to stay and restaurants to visit. I researched different vendors to determine who to book our activities with, and I reserved in advance. I also have a “standard packing list” of additional items that I bring whenever we stay in a condo: a good cutting knife, two good cooking pans, coffee, tea, extra kitchen towels, etc. My planning efforts paid off enough that › Continue reading…
In previous articles we’ve discussed requirements from several viewpoints. We’ve examined the characteristics and attributes of good requirements and differentiated them from business rules. We’ve discussed the merits of developing requirements in a cascading fashion from business goals through related objectives to enable prioritization. We’ve also looked at techniques and templates to aid in remembering categories of requirements to explore. Requirements are so important a topic I could probably discuss them for weeks, and who knows maybe I just will. Requirement documents can take on many fashions and styles and this week’s focus will be common formats for their expression and capture. › Continue reading…