Quality is objective. It is measurable. It can be seen, felt and measured. Teams working on testing of a product know well how to measure the testing effort and quality imbibed in the product. A straight measure of quality in a product is the encounter of bug in the product post its release. Multiple bugs detected by multiple users in live environment is definitely a disaster for the product. A straight question raised in such cases goes on the role of quality testing team and their efforts.
Test cases, test bed, testing efforts is all what counts in the measurement of testing in efforts to produce a bug free product to go live for end user and business environment. It is very important to engage test team members right since the inception stage of a project so as to avoid any confusion at a later stage that will definitely lead to time loss which is a big factor in a project. Projects do get delayed but the intelligence required to manage a project is to ensure delays caused by unnecessary and unwanted activities.
Another very interesting question asked is as below:
When handling multiple projects simultaneously for multiple vendor portfolio, how would you address conflicts if happens between testers/test leads or any two cross-sectional QA leads due to project stress? Also, how should one manage the current critical project deadlines if you are being given an ad-hoc high priority work on top of the existing ones?
Having a scenario of managing ongoing multiple projects simultaneously for multiple vendor portfolio is not something new that is encountered by project managers. Seniority of a project managers comes along with wisdom that comes with experience. Right on day one a project manager does not know how would he handle such kind of situation when his environment and ecosystem demands for heterogeneous deliverables, for heterogeneous stakeholders with heterogeneous list of top priorities and tremendous pressure. Conflicts and clashes becomes frequent occurring events under such circumstances when all teams and team members are under time and delivery pressures. Imagine a real life matching scenario when common resources are being used by two QA leads for two different projects falling under the same project manager and different project managers.
A concrete work plan with deliverables for each project by each member with exact timelines is very important. Only hitch in this kind of condition is the unplanned absence of any critical team member.
An ad-hoc priority on top of existing ones – all with squeezed timelines of delivery is another issue. To handle this it is important that such in-bouncing priorities which are totally unplanned must come through a common route and that route is strong enough to take a call what to compromise in lieu of what. In parallel to this, what is being compromised needs to be informed to the respective stakeholders, which is the responsibility of this common route. Let this common route be Project Manager.
Quality is not a “one department” or “one person” baby in an organization. It is a mission that has to be followed by each and every person of the organization working at any level right from the office boy, pantry boy, helper, up to the top most level. Quality can not speak different languages or having different meanings in a team, project, or the organization. It is a culture. It is a definition of life within the organization.
Quality has to be built on regular basis. It is not like a building of the organization that is built and you start sitting and working inside it. It is a building of indefinite size, indefinite scope but with a clear cut, crisp, measurable and adoptable mandate. It cannot be enforced to anyone. It has to be exemplified and demonstrated by each and every brick in the wall – meaning by each and every person in the organization. Quality in a never ending journey but on a definite path and a definite target to achieve.
If above level is achieved in any organization, there can be no hurdle in its way to reach at the top.
Following was the question I was asked today by a Doctoral Candidate in Educational Technology & eLearning today.
When it comes to leading a huge QA team such as your position, how do you define ‘quality’? Why ‘quality’ matters to you?
(QA professionals are asked by the organization/customers during every project as how they would define quality. Do quality differs in each one’s perspective? Because, not everyone view in the same way. What would be your input on this?)
My answer to this question could lead to many posts. In a summary my answer would be as below that I would be elaborating further in next few posts to come:
1. Quality Is a Mandate for me without which no individual, no process, no business, no product, no project, no function and no organization can survive in today’s competitive world.
2. Quality is Objective and has to be defined in a clear cut measurable manner. It cannot be a subjective manner. It is a tool to draw out best possible positive results to meet expectations and timelines.
3. Quality is a TOOL for Human mind and not a tool to be used by a human mind. It has to be in the blood of a person to live with all the time.
4. Quality is NOT Speed to deliver a product where while delivering it compromises by any means. It has to be a balancing act between Delivery and Awareness of Completeness.
5. Quality cannot happen in Isolation. It is a team work – inter and intra both.
6. Quality is Synchronization and unanimous consolidation.
Would be taking it up further in my next posts.
The list of my top 10 blog posts on Project Management and Quality Assurance are as below:
The link for these posts is: http://itknowledgeexchange.techtarget.com/quality-assurance/
- What is a Testing environment for software testing?
- Twelve essential Steps of Software Testing Life Cycle (STLC)
- 10 Skills to make a perfect Project Manager
- Ten Differences Between Project Manager and Project Leader
- 5 essentials while building test environment for software testing
- Eight Goal Settings for Software Developers
- Eleven Skills For Product Manager To Win Over Any Situation
- Five Excellent Quotes On Quality
- Project Task Prioritization With Eisenhower Matrix
- What Is ETL Testing – An Overview
5 type of projects will be in high demand during 2014 as listed below:
1. Education: Projects based on education delivery in a smarter way will be for asking globally.
2. Retail: Systems to make retail business more comfortable, versatile and widely acceptable.
3. Security & Privacy: Demand will be high in making systems more secured while keeping privacy intact over the internet/ cloud.
4. Health: Global health management systems will be high in demand.
5. Governance: Management of public utilities, systems and facilities in an automated secured manner.
The success of a project is driven by the teams that work on it. Besides various other factors and logistics, it is always the team that matters most because static and non living things do not think and act according to changing environment and conditions but it is the human mind that has an ability to work efficiently even under stressed and constrained conditions. That is why the people factor remains on top always.
For Test Lead top 5 priorities on card for the year 2014 would be:
1. Requirements: Understanding of customer and business requirements beyond what has been documented by the analysts will be very important. It will be good if QC guy gets a chance to walk through the business process of the customer thoroughly.
2. Documentation: Documentation includes a lot and means a lot for QC. Right from test case building, test report, bug closure report and so on.
3. Experience: Testing is one expertise and business knowledge is another. Former comes from learning and education whereas latter comes from experience and wisdom. A tester needs to have both these expertise in a balanced form so as to align both the roads properly.
4. Team: Management of team, allocation of resources and retaining the best of resources is an art that needs to be learnt and managed.
5. Learning: Learning is a process that needs to be built in a structured manner. Learning must come from each project, each success, each failure and so on.
Learning keeps on adding ‘value’ ingredient in the professional life of a project manager. Project manager has to be a quick learner and grasping agent to get the crux of matter so as to adopt enhanced process of managing his projects. Every project brings in a new bouquet of learning. The shortfalls and failures bring in a determination of not repeating the same in next upcoming projects. The successes carry on with a message of maintaining the same in forthcoming projects.
Let us look at the top 5 priorities that would be on cards of a project manager during the year 2014:
1. Requirements: Focus will be there to grab business and customer requirements as crisply and elaborately as possible. Requirements and business processes do not change on daily basis once they get established and optimized. During such changes happening there would be a risk of changes in the requirements but then it has to be handled in a matured manner.
2. Documentation: Documentation has been a consistent pain for project managers at the time of project crunch and hence needs to be managed appropriately.
3. Reviews: Project progress review control mechanism need to be redefined with customer as an active participant in all review meetings where the requirements and progress is to be discussed. The process of project review has to be more transparent for the benefit of all by engaging all stakeholders.
4. Closures: Each closure has to be signed off in a structured manner so as to ensure compliance to customer needs.
5. Teams: It is not difficult to get best of the people but to retain them is. Focus on engaging your team members beyond work prepositions so as to have an emotional tie up with the organization and work.
For generations there is a fundamentally ongoing fight between the product team and the quality team of any project. This is a generic fight for which there has not been a solution found so far. The fight is as below.
Product manager and his team always think that their product is fantastically built as per customer requirement with 100% requirements business needs met while building it. And the product is bug free. They further have a mindset that the product when goes to quality for internal testing on a test bed similar to live environment, the testing team takes extra long time with an intention of overstretching the whole exercise of testing just to maintain their importance intact. According to product team 90% of the bugs are either unnecessarily listed to build the test report long with large number of bug findings or the similar kind of bugs are repeated for the same purpose.
For a successful project, the credit goes to the whole team. But for a project delayed or failed the one man in crisis is the project manager. Whatsoever the reasons may be for this delay/ failure but it is the project manager that has to bear the brunt. Let us look at the topmost reasons that cause project delay or project failure:
1. Change Management: The initial requirements from customer leads to development but as the work progresses, fresh requirements or changes in the existing requirements keep pumping in from customer end. There is no wonder about it to happen and one should take it as a natural phenomenon. After releasing their initial set of requirements, customer think tank keeps pondering over what else could be achieved which lead to these requirements. Critical part is to grab these requirements with a positive note, analyze well and segregate these requirements to two parts – to be added, or to be reverted back to customer with a justification for not adding it.
2. Commitment: For business critical apps development there is a deep rooted commitment required from each section, from each of the stakeholder. If that does not happen, there are chances of missing some important handling in time that could lead to a big disaster if raised at a later stage. It has been seen that if customer key users are not engaged well in time initially during the development phase for clearing off units built have higher risk of facing major setbacks in progress of project.
It is very interesting to note that there is a group of project managers who do not stay in an organization for long. They set a rule not to stay longer than 2 years or so. Or maybe the rule gets imposed on them automatically due to their own pitfalls to enable them to keep surviving in the ecosystem. Let us look at what makes it happen in case of such project managers. The main factors could be their
These guys are not fundamentally strong in their project management skills. They appear to be confident and strong get goers in their talks but not in their walk. They talk high about their past achievements which probably they have never achieved in reality. They are good in ensuring management about their capability in handling any kind of tight situations and tough projects but in actual they have their plans of exit at right moment well in advance.
They will not be able to run projects well and that will apparently start appearing after a short while. They would spend their intelligence not in learning business, processes and procedures; but on how smartly to shift cap to one or the other instead of owning it. Logically at the point of insertion in the beginning itself should raise eyebrows of the management for such candidates who have appeared for candidature with a track record of spending not significant time in their previous organizations.
Keep pace with the Technology: The way technologies are changing at a very fast pace, it will be foolish to stay with your legacy technology running for years whereas the world is adopting newer technologies for the similar kind of projects. There is no doubt that when the existing technology was selected, it would have been a state of the art and latest of the technologies kind of solution. But remember that over a period of time, technologies get faded away in wake of newer, robust and advanced technology entrants.
Remember that development for all business apps start with a prerequisite set of requirements basis which timelines and plans are built and team sizing, resources etc. are set. Once this business requirement is converted to an app, it is released on Test Server, Staging Server and Live Server respectively for QC, UAT and go-live in the same pattern. Gradually when this app is handed over to end users on go-live environment, the app usage starts triggering along with the desired business results chickening out.
But story does not end here. New requirements that either go to changes in existing functionalities or new functionality built keep pouring in there by reshaping the size and environment of your existing app. That is where your awareness towards newer technologies to manage and control any kind of crunch in the existing one, is very critical.
Methodology & Approach: Every project does not fall in a generic project methodology. It is important to understand the type of project before making it enlisted under a particular project methodology. For this, based on the projects undertaken and new upcoming ones, relevant project methodologies to be identified and defined. Right project methodology helps project manager and other teams to ensure following right processes and documentations for each project phase in that methodology. A new project marked in wrong methodology could lead to extreme level of confusion and thus leading to failures.
Issue Management: Issues are integral part of any project arising during any of the phases of a project. Taking issues in a lighter way could lead to losing the right direction of a project and hence getting it derailed from its progress track. A single issue management charter with process driven approach with right & understandable definition of issue, its categorization, its severity and its closure with identification of ‘who’ is responsible for closure of issue, is very important. Any issue, howsoever small, could lead to a big disaster. A regular review is a must.
Communications: Be it project management, team management or issues management; nothing will move in right direction, if inappropriate or incomplete or missing communications happen during a project. Project manager must ensure to graduate each of the team members and team leads on how to handle communications and its importance. Right kind of information, to right people, at right time with right kind of actions required must be a set protocol of communications. For example, if a piece of information is just for the sake of information, or an action is required, along with its criticality, should be the right approach to manage.
Project Management mainly comprises of converting customer requirements and business needs to an application so as to enable customer in running its business in a much smoother and error free environment. It needs to be imbibed of business processes, workflow (if required by customer) and minimization of manual interventions to a maximum extent. Any business process that speaks about business enhancement, improvisation and optimization by transforming it from manual to automation enabled through coding needs to be thrown into a dustbin.
Timelines of a project are mostly defined as per customer guidelines. At times it is important for a customer to get a solution within a stipulated time frame if the app is related to a pre-scheduled launch in a big way and the app is going to play a major role in that particular launch. Usually a project where customer has no say in desired results’ release timelines especially when it is a customer sponsored project, it is definitely a major glitch. Either the requirements are not serious or customer has no intentions to pay for the product later.
CTTR is Customer Time To Release which means the timelines defined by the customer regarding release of product. All project timelines, budgeting and allocations are a total derivative of CTTR.
Budget for any project is allocated right at its initiation phase. Budgeting includes lot of factors but the main factor remains customer defined timelines. Keeping this target defined by customer in mind, a backward calculation is done and accordingly time allocation to each phase is done, team sizing is defined and resource planning is done. After all it is customer that matters the most.
Well, it does not mean that there is a scope of comparison even if this backward calculation is being done. Two prime factors that play a major role in this whole game is quality and finances. Budgeting beyond optimum level and compromising with quality of the product will mar the beauty of product and impact on business badly. When timelines are shorter there is another way of pulling your socks and not letting you beaten down. It requires higher level of skilled task force, error free tools and rich experience to win over in such kind of wars.
If you really want to be a successful project manager you need to acquire following three powerful weapons so as to be a winner all the time whether the conditions are favorable or you are travelling in rough seas. The teams that are formed usually have all mixes of human beings having different styles of working and delivering results in different fashions. Overall momentum is something which need to be maintained all the time to race along the ticking clock. The three important and potent weapons that can help you are as below:
Skills: You need to have high quality project management skills to win your battle. If you are leading a team of unbeatable and brave soldiers but lacking the same in you, would not lead you to a winning situation.
Tools: Whether it is project management tools, bug tracking tools or incident recording tools – you need to assess your needs and acquire these tools accordingly. Overstuffing yourself beyond required commodities will lead to a burden on your head. But vice versa also holds equally good meaning if you are underestimating your needs and go for the battle along with your team with shortage of armory, your defeat is sealed right in the beginning.
Experience: Guys with rich experience under their belt and laurels shining on their shirts are always moral boosters in the teams. Hence it is important to have such guys, at least one in each team to keep overall tempo at high pitch all the time.
It happens at times when you have a mission critical project with tight timelines from customer that increases its stake manifold, for which you place best of your teams comprising of high skills and experience, and on top of it you provide state of the art tools to tackle all kind of situations; and still the timelines are not met and things go out of control. It is always important to go for a deep analysis for such kind of failures to such an extent that the shortfalls are identified with their core reasons; and are sidelined once for all, for all forthcoming similar kind of projects.
It is well said that disciplined approach and hard work pay well in comparison to merely hard work. Well defined processes and procedures play a major role in this. If these are in place, it makes your tasks easier in managing and guiding your teams. Since there is no differentiation among teams and the standard procedures apply to everyone, irrespective of who and what, the same procedures need to be followed.
Growing these skills is as important for immature teams, as is for matured teams to keep nurturing and excelling in these.
PMP is a good source in two aspects. One, it gives you a great insight on how to manage your projects in a more efficient and risk free manner. Second, if you appear for its exam and qualify, you get a universally accepted accreditation that is highly appreciated worldwide. PMP (Project Management Professional ®) offered globally by PMI is a boundary free certification. During your learning towards PMP you learn a lot about project management something that you have never learnt before or come across during any other kind of learning towards project management.
Four takeaways that you can be assured of during your learning of PMP can be listed as below:
1. It provides you a well-organized and highly structured method of managing your projects and related activities. The inbuilt flexibility enables you to design your project management methodologies as per your company’s requirements.
2. You get empowered and leveraged to take full control of your project(s) and mitigate risks anticipated in advance (or those come in the way in an unannounced manner). Your learning gets enhanced to enable you to plan, execute, monitor, control and steer your projects in a professionally organized manner without getting drifted away from best practices being followed across the globe, similar to your industry.
3. You get an enormous amount of knowledge on understanding gravity of documentation required for your kind of projects running in your organization. It helps you in planning and controlling scope, teams, financials, schedules/ timelines, quality, risks and closures in a way so as to assist you in achieving higher level of success in any kind of projects undertaken.
4. You get well equipped with the tools and techniques to monitor the timelines of your project in a proactive manner with an advanced way of getting you informed about any contingencies prone to occur during project lifecycle.
Capturing business requirement is a cumbersome process in many aspects. For some it might become difficult to capture concrete requirements if business is not process oriented and documentation centric. In such conditions there would be as many statements misaligned with each other as many mouths. Each member engaged even in a similar or same process might talk differently regarding the same process which could lead to a big confusion. In such conditions everybody would be eager to speak but nobody to vet the stated requirement.
In certain other conditions, systems in place could be too cumbersome that your timelines for closure of requirements capturing would definitely get shattered. Here, in this case, you would be running after the process owner, who would be rich in process knowledge and practical experience, but he would not be able to give you substantial time to help you in capturing requirements in multiple runs.
Requirement capturing goes useless if there are some ambiguities or misalignment that stops it for sign off. It is important to opinion from everyone who is part of a process in the organization and then a proper alignment needs to be done, if required, by involving top management into it.
Customer requirements never get finalized in one go. It takes multiple meetings and discussions to understand, draft and finalize so that it gets signed off and final nod to move ahead. The discussions that are held in this regard are primarily of four types. As listed below, these four types generally go in the same order but there are instances when in between one type get intermingled with another type. It also happens that during same discussion more than one type of discussion takes place.
One needs to be smart enough to differentiate between the type of discussion and thereby understanding the gravity of matter and level of documentation required to be performed. First type of discussion is General Discussion. Normally all initial discussion would be of this nature. This could also be treated as ice breaking as two different teams from different agencies are sitting across for a serious matter for the first time. This type of discussion would not be very crisp and conclusive.
Second kind of discussion is Scenario based discussion. The team expert in processes and procedures would showcase all possible scenarios so as to provide the other team an insight of the business requirements. Here – documentation needs to be very detailed and accurate so as to capture and understand business scenarios.
Third type of discussion would be Data Details. For a better understanding of scenarios discussed in other meetings, it is further explained with the help of actual business data or sample data simulated so as to build respective scenario.
Fourth kind of discussion would be Process Details where the business process is explained in detail. Important point is to study business process, data details and scenarios so as to find out and get resolved, if any ambiguity or misalignment occurs among the three.
I recently met with a test team with an excellent performance record. For all the applications where it had given a green have a track record of zero major bug encounter post its launch and 100% customer satisfaction with timely sign off. Definitely the credit goes to this test lead and his team. It was a point of curiosity at my end to know what was their process and methodology to give such a tremendous performance.
Their logic was very clear and crisp. The team lead had made a rule that during all customer requirements capturing by business analysis team – one QC member will be part of the team. Customer requirement finalization doc once signed by customer would be shared with testing team. The testing team, on getting customer requirements documents, would immediately start building test cases where on the other hand, requirements have reached to development team for preparing development plan, testing plan and release date.
While the development team is busy with meeting with their timelines, test team members had a clear cut charter of brainstorming and finalization of test cases built on the basis of customer requirements purely.
Project Plan is a onetime activity as and when a new project comes up. Project Manager or Project Lead prepares a project plan for the complete project while earmarking milestones to be achieved thereby measuring project movement towards its closure. Well said and done, if an organization or project team lives on this project plan till the completion of project without measuring the actual achievements scored at a shorter and prescribed frequency, it could lead to a disaster.
That is where project plan monitoring comes into picture where during regular project review meetings the initial plan is measured against the actual tasks completed at their stipulated time. It is a well-known fact that a delay in meeting one deadline for release of a milestone or completion of a task has recursive negative impact on project overall. That is why a regular review is very important and a dashboard where plan versus actual timelines against each task is shared with all relevant stakeholders.
Teams engaged in more visibility feel more satisfied and get an automatic momentum and thrust to meet their timelines.
Project Management, over a period of time, has become more optimized by means of evolving mechanisms. On the other hand Project Leaders and Managers are being asked to accept more challenges in terms of faster deliverables with higher amount of accuracy, managing frequent changes in customer requirement, while focusing on cost reduction. Cost reduction can happen by way of upgrading team members’ knowledge, using minimally required resources and managing attrition.
Attrition eats away a big cost. If talented and well groomed team members leave organization in between a running project, it takes a lot from various angles to manage the show in order to meet customer’s quality and timely delivery requirements. Innovative ideas like BYOD, centralized printing/ scanning resources, grooming team members for multiple tasks/ areas etc. are being implemented to optimize resource planning and management. For upgrading domain based knowledge of various team members regular training are must. Training without evaluation and monitoring can become a useless activity.
If with the increasing tenure of team members in the organization, a focused approach is maintained to prepare them to manage other domains where they have no expertise but which are critical for organization, it becomes quite helpful for the project manager in managing them by reallocating in case of a crisis. Times are gone when for critical areas dependency stays on a single person in the organization. That is the demand of time and also a requirement of certain standards where you are required to make organization more system dependent than person dependent.
As and when pressure related to revenue streams builds up on any business, it automatically drills down to project teams. The project manager comes under scrutiny in terms of managing the same along with supporting aggressive business growth by driving deliverables faster for running projects without failing to address customer’s changing environment and requirements. Newer technologies like cloud computing, these calls can be taken up to mitigate the risks arisen by creating and delivering value addition by making technological boundaries limitless, speeding up deliverables and creating a new domain pool within the organization skilled to manage it.
Personal, private and heterogeneous cloud platforms can help in tackling these situations by making the deliverables to be used by end user/ customer as-a-service thereby helping customer in spending less and enabling themselves with delivering faster and lowering timelines by means of reusability and optimization. Fear of cloud is vanishing provided adequate security measures are embedded in the system so that the customer feels confident including large, medium and small organizations. There are a number of information systems experts in the market to understand an organizations business requirements and providing them appropriate knowledge of positive and negative impacts of cloud computing.
Organizations who have taken a lead in adopting cloud computing for their internal environment or external customers can be taken up as example and benchmark. Case studies can help in such cases to build confidence for the organizations who intend to take new initiatives in this regard.
1. Connect with thought leaders in global and local arena to learn about latest business technology trends. It is also important to understand the innovations taking place in latest technologies like cloud computing, mobility and analytics.
2. Collaborate, participate and get involved in latest discussions, forums, and expert columns to get the insights in successes and failures of these technologies related to mobile, cloud and analytics.
3. Without such engagements, a business or project manager can’t initiate a blueprint for his organization or customer regarding transformation proposed in terms of adaption of newer technologies and the optimization and benefits offered in return.
4. There is always a gap between current and future needs for any organization of any size. A time to time introspection is must to understand whether enhancement in legacy applications will suffice to cater to newly arisen business needs or there is a need of altogether new systems to manage and sustain business growth.
5. By getting insights about futuristic applications and technologies, business growth strategies can be well managed by creating competitive advantages and providing higher thrust to business.
6. Always strive for solutions that carry built in best practices relevant to the business – whether it is in house driven project or an outsourced one.
It is very essential for Business and Project Managers to anticipate the pulsation and hence determine how newer technologies are emerging and marking their impact on businesses across the globe. Newer solutions could help them in tackling legacy driven systems’ issues and streamlining the business in a better way. There are case studies and global consultants available in this regard to teach on how business expansions can be well managed by imparting technology knowledge so as to enrich business processes.
Understanding of latest technologies, learning to explore them so as to understand where all and to what extent they fit into the business scenario and how much enhancement is provided, is an important initiation in this regard. Initiating adoption of newer technologies without any fundamental research can lead to a fluke resulting into a huge waste of money, time and resources. Fast changing business dynamics thereby creating critical situations where legacy systems come to a standstill can hit and ruin a business very badly. Timely interventions to get familiar, therefore, with latest technologies become quite crucial for the organizations.
Currently running legacy systems do not guarantee to sustain any business’ future needs. And that is why collaboration, decision, adaption and operation need to be introspected from time to time. If this is not done in a regular manner, a business will never get an opportunity to explore latest technologies, innovations and solutions.
1. Study the Industry: If it is decided that the organization for adaption of cloud technology, it becomes important to learn most commonly practiced data security controls in local and global environment.
2. Understanding of best practices in a newer technology is as important as knowing about the area where you are planning to buy a house. Be assured that you have enough knowledge about your business requirements and the best practices available in the arena for an effective data security strategy.
3. While learning about the global standards and practices, ensure that you have ample number of case studies, specially related to your industry to understand the key challenges that were faced by them while they were implementing data security strategy.
4. Selecting a vendor is a tough call in such cases. You need to select the best of the available vendors providing such services in terms of established one having minimal failure rate and higher rate of success in deployment/ serving. Also check the leaders in this field.
5. All said and done, having techies within the organization who understand the technology architecture and solutions for data security is again a must. External agencies can support and deploy to whatever extent, having someone at home who understands the crux is essential.
Every technology adoption in a business is seen to be on the positive side of its ROI. ROI includes tangible and non-tangible gains, both. There are various factors kept in mind by any business planning to adopt any, two of them, or all the three technologies to enhance their business. Few core factors can be taken into account are being discussed below.
Lower Capital and Operational Cost might not hold good in all adoptions as initial adoption of any new technology required both but it can be well balanced with the projected returns.
Innovation: These technologies require lot of innovation and ideas to establish. New paths need to be invented to acquire more customers, create customer delight and build larger volume of prospects.
Simplification of Processes: Core business processes take a steep change with adoption of these technologies.
Role of HR: HR has to play a major role in mobile and social technologies adoption. They become the strategic partners in a big way for these two technologies adoption in the organization.
Transformation: It demands a major change in functioning and processes of the business.
Evaluation and Assessment: A continuous evaluation and assessment process has to be in place while and post adoption of these technologies. There has to be a process to get feedback from customer and other stakeholders to ascertain the value gained.
Recruitment: Acquiring altogether different employees expert in these technologies to give it a thrust in adoption and fetching results out of it.
Security: Last but not the least, the most important factor – Security, needs to be handled and managed in an entirely different fashion in these scenarios.
Technology advancement is a continuous process. The three major technologies that have revolutionized the current decade are Social, Mobile and Cloud technologies which have impacted businesses in a very big way. There is no business these days which is untouched by the heat of these three technologies. Some businesses especially the large ones and those which are conscious about their outreach to last mile of consumers/ users have already taken the lead and taken initiatives to deploy it and delve into it in a larger manner.
Getting into any technology requires a structured planning and methodology. Without a proper planning or going into it without an organized manner can rather lead any business into a negative mode. There need to be appropriate policies and procedures in place along with a large amount of brainstorming to move ahead in adopting any or all of these technologies. All three technologies play a major role not only within the organization but in the outside world also among all stakeholders – be it prospective customers/ employees /.partners, or existing ones. For example regarding the security of information has to be taken care in a broader way to cater to multiple platforms, multiple devices and other needs.
These technologies are definitely making a big positive impact on the business provided these are handled with care. The investment in these technologies has also to be worked out in a sensible manner by taking care of various options available in the market otherwise a big investment might result into no end results.
Quality is a lot more that identifying and controlling defects. With increasing dependencies on business applications be it on server, mobile or web; is demanding more and more professionals who are capable of this paradigm shift and are intelligent enough to accept the challenge. One of the major areas to be focused in Quality is about understanding of existing processes and efforts towards their enhancements and optimizations.
Business software application is a basic requirement of any business these days. Businesses are emphasizing more on automation, consolidation and integration. Innovation and improvement is always welcomed in this field. With the exponential increase in software industry in the global arena, emphasis on quality needs, its optimization and adherence to processes is becoming more and more important.
The software industry is growing steadily with clear cut demarcation of boundaries. The applications are being built keeping in mind to cater to global market rather than the local area. Because of this fast growth in software industry, there is an increasing demand of quality professionals which will keep increasing in coming years.
There is a huge shift in mindset regarding scope of quality in software industry. Given the fact that dependency of business is increasing on applications, the adverse impact of any flaw bypassed during quality might impact business heavily. A small transaction leading to a wrong calculation due to a bug could cost a high amount to the business. Quality therefore has a higher amount of significance in today’s scenario.
Development process is supposed to ensure complete adherence to customer requirements and business alignment thereby making it useful for customer else there remains a never ending fight between the customer and delivery organizations regarding the gaps left un-addressed. Even if there is some gaps remain in the final deliverable and those ‘asked for’; it should be closed at the earliest with mutual consent. This can happen only when the development team gives some valid reasons for not filling those gaps due to what so ever constraints and customer agrees to it. Hence due to this higher stake of correctness of coding adhering to customer requirements, it becomes very important for quality to pitch in and ensure a zero defect product.
There has to be a good balance between coding and testing throughout the development cycle. For this, a tester’s knowledge about requirements and product in questions is as critical as it is for development team.
Software industry depends highly on quality of product. Bug encountered during and post production but before launch always cost in terms of time and money. Fixing a bug might take a small chunk of time but retesting again is a time consuming job which is required to ensure the impact of bug fixed should not degrade or put a negative impact elsewhere in functionality or business process. Quality again has to play a major role but the onus lies on development team also to ensure a bug free ‘bug fixing’.
Three important acts to perform during product development in a continuous manner can be listed as below:
1. Reviewing Process: Regular reviews, on one hand are quite important; and on the other hand, it is also important to keep reviewing the processes defined for development and testing of a product. The team, process and timelines need to be aligned tightly so as to ensure no leakages during development or after the release of product.
2. Customer Requirements: It is not a one-time exercise to capture customer requirements and then start development in closed doors. This will always lead to failures and disasters in the short and long term, both. It is very important to keep customer engaged during every iteration, internal releases, and milestones completions.
3. Best Practices: How so ever best your practices may be as per your claims, but there is always a scope of improvement, without any doubt.
Typically the vast scope of quality can be divided into three major streams – Quality Control (QC), Quality Assurance (QA) and Compliance. All three streams are critical for any organization engaged in software development activities – be it as a vendor or for internal use. In any case – an internal development team of an organization also more or less is like a vendor which has to ensure smooth delivery and functioning of the products they develop and deploy within their organization.
Scope of Quality Control (QC) is limited to product’s handling, testing, reliability, stability, bug finding, maintaining testing reports and ensuring compliance of documents required for the purpose of audits. QC is responsible for inspection of the product in all aspects from user and business perspective. Code testing and testing of product for the purpose of finding bugs, reporting, maintaining data and its history, getting bugs fixed, retesting, and ensuring finally that the product goes for release with no bugs or leakages. Test cases, test specifications and testing are very important. Retesting of product post fixing of bugs by development team is as critical and needs to be as exhaustive as first time testing of the product.
Scope of Quality Assurance (QA) is to ensure keep evolving best practices, ensure its compliance and adherence with continuous effort to uplift quality standards of the organization and teams by means of training, documentation, audits and change control mechanism. QA is required to be focused more towards compliance and adherence of processes in place. A re-assessment of processes in place is required to be done from time to time. External certification of global standard and regular audits by them always helps in this respect.
A wireframe is nothing but a blueprint for any sized software project in today’s corporate world. Think about a building on a land is first presented as a blueprint in order to explain the architecture and design of that building. The layout of the building is shown on this blueprint along with the components to be used for designing of this building. In a similar manner a wifreframe is an introspection of a software application in a layer by layer manner so that the application in question can be viewed/ reviewed from different angles.
A wireframe is a powerful tool to present a software application design and architecture in a crisp and clear way that enables you to understand it much strongly. An application can be referred to any business application, mobile application or website portal. A wireframe presents a 2 dimensional picture of your application in order to understand it more deeply and from different perspective.
A wireframe provides a visual map of your complete application so as to help you in see the application flow, navigation, correlation of various components of the application, linkages and associations. An application that is first presented through wireframe gives you a confidence about its flawless design, navigation and ease of use once you go through it and find out the gaps. A wireframe helps you to find out these gaps well in advance and hence assists you in completing your projects well in time with least amount of risks.
PMI – Project Management Institute is a global membership organization for professionals in project management. It announced that the prestigious Eric Jenett Project Management Excellence Award for 2013 regularly organized by PMI goes to ESI International Executive VP J. LeRoy Ward, PMP, PgMP, CSM. The award is presented to an individual professional every year by PMI for contributing outstandingly to the practices of project management by means of demonstrating initiatives and leadership style in a unique manner so as to enhance PM techniques, concepts, practices or theories that are widely acceptable and applicable.
Ward, while accepting this prestigious award, added to his speech that he is feeling highly honored to get this award. This way he has been added to the list of past honorable winners of this award who have been acknowledged for their passionate work towards project management excellence and innovation. Ward has more that 38 years of experience in project management, program management and portfolio management in the U.S. government and various private sectors. He is known for writing various highly acclaimed books on the subject and is a well known speaker at global conferences.
5 Ancient Principles Of Leadership is a lovely read that you will enjoy for three reasons – it is crisp, it is short and it gives you a lot to learn. As a project manager this book written by Jack Myrick has some basic fundamental principles to teach you that if you employ in your professional life, will never let you down in terms of meeting your targets or managing your teams. This 87 pages book has been published by Jaico Publishing House and it is a fable of a ship builder.
Rule 1: Make Them Appreciated: Your team members are as important as you are for your organization. As a child needs pampering and feels happy about it, similarly your team members need to be appreciated. Appreciation gives a feeling of achievement, satisfaction and motivates one towards his goals.
Rule 2: See Their Potential, Not Their Flaws: Instead of keep cribbing about what not has been done, it is better to understand what each of your team member is best in and then give him/ her tasks according to their potential. Putting a person with perfection in one field put on to achieve success in another field might end up in a failure.
Rule 3: Lead With Authority, Not Power: Use of power generates revolts but using authority demonstrates a great leadership skill.
Rule 4: Love Them First: Before you assign them a task or wait for them to complete a task, it is important to make them feel that they are being loved whoever and whatever they are. Once the message is clear, it may lead to wonderful results.
Rule 5: Make Them Feel They Are Part Of Something Special
No. 1: If you are clear about your destination, it becomes easier for you to decide about your journey.
No. 2: Drawing out productivity is an art that a project manager and a team leader need to learn as soon as possible as it is their sole responsibility.
No. 3: No business can survive without existence of its customers.
No. 4: In business it is not only a single person’s money that is involved, it involves money of various stakeholders.
No. 5: Any work that is done in a systematic manner will definitely fetch out some useful results.
No. 6: In absence of a plan there can not be any commitment but only promises and hopes.
Following 5 quotes are the best among a lot of 100 odd quotes I found.
Absolutely true. A code, a deployment, a training, a business analysis – everything has a optimum timeline.
Excellent quote. It is easier to demonstrate as a busy entity but the current scenario of professionalism doesn’t accept it if there is no visible result to the effort being done.
A warm welcome to Igor Ješe to accept my invite for an interview. He is the author of popular mockup tool MockupScreens. Recently Igor has published an easy and straight-forward generator of real-looking test and sample data named as MockupData. MockupScreens was built in 2003 by Igor as a simple tool to use it for himself and a small group of analysts. Within two years it was a well known tool to professionals outside his known groups.
Please tell about your early school days?
That really brings old memories, let me see. I barely remember my school days before I was 10 years old, it’s almost like I was just a bystander in my own life before that age. Then something happened and I started to fight for myself, becoming pretty stubborn in the process. Being a parent myself now, I think I can really imagine the hard time my parents had from one incident to the next during those years.
What were your plans during your later education days?
The weird thing is that I was by far most talented for physics, of all things. But when the time came to choose my professional education, I couldn’t for the life of me visualize myself as a physicist. So I went with my second choice, which was Computer Science at Zagreb University.
Circumstances quickly changed though, and I had to support myself for almost the whole duration (that dragged out to embarrassing 7 years, to be frank) of my studies. So when my Master’s Degree came in 1999, I was already employed with IBM for years and my course was firmly set.
What expertise did you achieve during your college days?
I guess I was lucky back then: I was involved in one of the biggest IBM projects in the region at a time. For a quick-learning and determined youth like me back then, it really seemed like a vast fountain of knowledge and experience and a playground with wonderful sci-fi technologies I’ve seen only in the movies before that. I came out with more than working knowledge of DB2 and WinNT servers, so I guess I got more than unfair advantage over my fellow students in the process.
What career did you opt to start with after completing your studies?
For few years, I was quite happy improving my skills as a database guy in development teams. But soon I started to feel “left out” somehow, it was like important things were happening somewhere else. So I started to steer my career towards Software Requirements, because I decided that was in fact were the operative decisions were really being made.
Since how long are your engaged in Software Requirements and Development Methodologies?
Software Requirements came as an intentional career move, somewhere before 2000. But the genuine interest for Development Methodologies started in quite different manner. In 2001 several colleagues and myself joined the small high-tech company in the making.
But within months we were all pulling 60-hour weeks without any real idea how we got ourselves into that mess. So we as a group decided there must be a way to work smarter instead of harder, and busied ourselves with UML first, which quickly led among other things to RUP and formal Project Management.
After several years of testing and customizing heavily all the knowledge we could find for our own practical day-to-day use, the results were so obvious that other companies started to hire the whole bunch of us as “methodology consultants”, to do the same for them.
What is the tool that you have developed? It is meant for whom? What purpose does it suffice?
MockupData (www.MockupData.com) is a data generator, the tagline I settled on is “Make your data look real”. Basically it generates bulk data that looks like a real thing: real-looking names, addresses, etc. Software testers use it to populate the applications they need to test.
There is no realistic testing having the fields of your system filled with random strings and numbers that human being cannot relate to anything from the real world. And populating databases with “almost real” data in realistic quantity is either prohibitively expensive in human effort or simply not feasible – e.g. because of data privacy regulations.
How did you conceive the idea to develop this tool?
Actually I have needed something like this myself many times. Several times I have even implemented something similar for a specific project and specific database. And in 2003 I have even published a precursor to MockupData, as a joint effort with a friend. But we were quite inexperienced so the partnership hasn’t worked out, which was nobody’s fault really, but the product just faded out before it got any real traction on the market.
Occasionally I have used this first product for my own purposes afterwards, and it simply felt a shame that I couldn’t offer it to other people. So I finally started from scratch and MockupData is a result. With which I’m very satisfied I must say, and the early feedback is simply fabulous. Testers and database developers need something like this, to create and re-create quickly and at will different variations of real-looking data, and in thousands or even millions of records when needed.
How much time did it take to develop this tool and with what size of team?
More than a year with three people putting approximately half of their time into it. Which was quite longer than I anticipated. I thought that since I exactly new what we needed to implement it would be a fairly quick project. The core “engine” took only a few weeks. The whole tool only several months. So far so good.
But then we came to usability. We had many concrete ideas how to make ordinary tasks more smooth for the user but no ready-made support for them in wxPython, the GUI package we were using. Finally I hired a usability designer to help us out, a great Spanish guy that on and off spent months discussing with us different ways to implement most of those ideas, and then to test and re-test and tweak everything.
What is the development methodology you adopted to develop this tool?
I knew you would ask that and still I don’t have a ready answer for you Frankly it was a mix of best practices: implementing small fixed chunks at a time, tricky parts first, stopping for refactoring when needed, while continuously having a “clickable build” and continuously unit-testing everything except the GUI.
I believe in creating a team of great people and letting them work, and to tweak methodology to suit them instead of the other way around. Most techniques in any methodology are in fact trade-offs, and if something doesn’t work for your particular team and your particular situation – out the window it goes.
What so ever is the fate of a project, it has a long lasting impacts at various levels and in various directions. If a project fails, it impacts your market value and reputation. It also impacts on your relationships with the customer for whom this project was being done. Then there is adverse impacts that automatically seep in inside the organization. The teams that were engaged in the project morally start owning this failure and unknowingly a feeling of guilt resides inside their heart. That itself becomes a demoralizing factor for forthcoming projects.
Then it is between various stakeholders and the management who stop seeing each other eye to eye. A failure of a project also becomes a blot on the performance of project manager. Hence overall a single project’s failure has multidimensional and multi-intensity impacts. For customer it becomes multiple loss. When a project fails, customer loses money, time, and fulfillment of a dream. It hurts customer and probably that becomes the reason of getting a negative reputation spread in the market through word of mouth of customer. All this has a recursive effect on the overall health of the organization. Multiple because the running project that failed during its final stages resulting into loss of money, time, resources, reputation etc.; and due to this loss your forthcoming business gets impacted hitting you with a double sided sword.
On the other hand success of a project results into compounded success. Your satisfied customer brings in more customers, your successful completion of project scales up your market reputation, your internal atmosphere becomes inspiring and teams get motivated to handle next level of hurdles.
When a project is assigned to a project manager, his first and foremost intention must be to chalk out a strategy to ensure timely completion of project without any compromise with the quality and financials. Most important for a project manager is to review Business Case once again so as to understand it thoroughly and an extra bonding with the project is built that becomes an additional driving force to act as a catalyst to the progress of project throughout its lifecycle. Some clear cut derivatives need to be worked out from the Business Case.
A project as such is both for a project manager – a problem and an opportunity as well. Problem because someone (customer in this case) wants a business solution to streamline their processes and hence that requirement needs to be catered to as per committed timelines and scope. Opportunity because once you decide to solve an issue for a customer (here in this case is to built an application in accordance to the business requirement specified) that resides at one level, you equip yourself to climb up to next ladder to handle higher level of issues and business requirements. That is how a project leader becomes project manager. That is how a person who is a team member once, becomes project owner and gradually reaches to a level where he or she handles multiple projects at the same time with complete attention, energy and dedication to each.
Business benefits to customer must be very clear right since beginning of this project which should start coming into light by the end of project.
Project Initiation: Every project has these basic phases during its lifecycle – Project Initiation, Project Planning, Project Execution and Project Closure. Each of these phases consist of a number of activities basis which success (or failure) of a project is ascertained. In project Initiation phase – when a project is borne, Project Definition is documented. Once project definition gets signed off, this project gets assigned to one of the project managers. This completes the Initiation phase.
Project Planning: Next comes the Project Planning phase. This phase begins with a very important task of requirement gathering, requirement analysis and definition of scope. Basis Scope Definition, Work Breakdown Structure (WBS) is made. WBS is a task wise breakdown of major milestones/ releases defined. Based on WBS, activities are defined and their hierarchy/ sequencing is set along with their timelines estimations. These activities are then scheduled for their respective releases by allocating appropriate resources and budgets with them. Identification of appropriate resources and right estimation of budgets is one of the key thing in this gamut.
Project Execution Phase: This phase is the real war game of the complete project. In this phase we execute, monitor and manage the overall WBS with ascertained milestones keeping in mind to mitigate any risks to ensure adherence to timelines, quality, and project closure as per plan.
Project Closing: The final stage of project management lifecycle is Project Closure where the project gets signed off
High Expectations Are The Key To Everything by Michael Bergdahl is a fantastic self booster and motivational guide. Michael worked at Walmart Headquarters in Bentonville, Arkansas, as Director of “People” and was reporting directly to the Founder of Walmart, Sam Walton. Sam Walton has been a big inspiration in Michael’s life and has influenced him in many ways. Michael is known to possess an authority over the best practices of Walmart and Sam Walton. Currently Michael is a Professional International Speaker and has visited to many countries across the globe. He is engaged with many big global corporate. Michael says to for writing High Expectations Are The Key To Everything, his main source of ideas, insights and inspiration has been Sheryl Bergdahl, his wife.
As per Michael it is nobody else that stops us to set higher standards and achieve higher in life, but ourselves. Challenges are there in everybody’s life. Some build courage to cross all hurdles and achieve success whereas others get discouraged by the obstacles in their life and get drifted away from success even if both start with same resources and get same opportunities. There are total 6 keys to success described in this book by Michael by setting higher expectations from yourself to get all round success. You need to set your vision and purpose with a commitment to yourself to move to your goals with passion.
Next key is – you can control your own destiny and achieve success in life but with some gem like mantras – having focused and disciplined approach towards your goals, hard rock determination, and you will have to sacrifice something in your life to achieve something much bigger; with an ability to adopt change with the changing environment.
Overall this is a must read for anyone aspiring for following a tougher path to achieve big results in life.
It is not easy to drive a project being a project manager when you have multiple projects in hand. You really need to have a concrete strategy, plan and process in place to make it a win-win situation for all stakeholders. Every stakeholder’s eyes remain on you to manage and monitor your project and you need to have a proactive approach to assess any stipulated (or unalarmed risks that usually happens) and raise an alarm to mitigate the risks in time without compromising with costs, timelines, process, product and quality.
To understand basic things first, your project’s life starts with project definition, project scope and then project requirements. All the three elements need to be taken care of in a very crisp and elaborative manner so as to get a clear cut sign off and to avoid any ambiguities that might occur at a later stage. Project requirements need to be scrutinized and understood well so as to build work breakdown structure (WBS), basis which you will be preparing your team’s activities and tasks with appropriate timelines of releases, estimations, resource allocation & management, and costing involved.
If you have been able to perform your job well up to this stage, be assured that you have scripted half of the success of your project already. Based on what you have prepared as listed above, it becomes easier for you and your team managers to monitor and control with least chances of failures in adhering to your estimates and plans.
Book Review: Improving Your Project Management Skills by Larry Richman: Enriching Project Management Skills
Improving Your Project Management Skills by Larry Richman is a really enriching book for all aspirant and established project managers hungry for getting mastered in enhancement of their skill for managing projects. The second edition was published in 2012 and is themed on one of the most popular seminars with the same name in the United States conducted by American Management Association. The second addition has been completely aligned with PMI’s PMBoK (Project Management Body of Knowledge ®) in terms of revised Project Management Standards, Practices and Methodologies.
This excellently presented book completely covers a project’s lifecycle right from its inception to project sign off. You will find a comprehensive coverage of step by step process knowledge of real life projects. The life of any project begins documentation of project definition, project scope and project requirements; and their subsequent sign off to kick start a project. Once the project initiation is handled in a structured manner, there remain less chances of hiccups in its execution and deployment in the next stages.
On the basis of project requirements are captured in detail, what a project manager needs to do next is to build work breakdown structure (WBS). The same can be translated to diagrammatic form to manage the sequential activities of project execution/ development phase. Basis work breakdown structure, tasks’ estimations are worked out for each activity with appropriate timelines, team estimations, resource management and financials.
Improving Your Project Management Skills by Larry Richman, in a nutshell helps you in chalking out concrete path to accurate estimations and execution without getting budged off with your timelines, costs, resources, quality and teams.
Generally three key factors are considered to work out on future of any running or starting project and those are – Cost, Time and Quality. It is assumed that if these three factors are monitored closely throughout the project lifecycle, a project manager can easily predict the future of a project. In real life practice and especially for large sized projects these three dimensions do not suffice the process of proper analysis for the purpose. There is a fourth dimension that needs to be added to it and that is ‘scope’. This is an entity that can contribute to a large extent in shambling your targets of cost, time and quality.
Scope is something that needs to be finalized and controlled throughout the project. It does not mean that you are not entitled to change scope during a project. Of course if there is a change in business scenario of the customer and that required a change in logic or flow of the system, scope chance can’t be entertained. There is a fifth dimension that is a complex one to handle almost to the same extent as that of ‘scope’ that impacts heavily on progress and success of a project as per desired pace and that can be termed as ‘team’. Team size/ composition is one sub dimension of the dimension titled as ‘team’ and another sub dimension to this is team members turnover.
We all are aware that in current days tight conditions we can’t have backup for each member but definitely project manager need to have a concrete alternatives in mind so as to have a quick remedial action if any of the dimension in going to impact on project’s projected timelines.
Shorter projects do need lesser attention as the iterations are quick, with shorter timelines of deliverables and milestones. In a short duration if a milestone gets missed, it raises many eyebrows and things get controlled in a fast manner. It is reverse in case of longer duration projects. In longer duration projects, milestones and deliverables are not too close and hence chances of focus getting drifted away are higher. If, for example, the duration of project is more than a couple of years and major milestones are scattered over an average of 3-6 months, it is difficult to get senior management’s engagement in the project in a tightly woven manner. It might happen that senior management does not discuss about this project for a couple of months if there are no major milestones visible during that period.
PMO or project board in this case, like senior management, might oversight such projects, keeping in mind that they have a number of projects in their kitty, including some major and critical short term projects. This acts as a double sided sword creating twofold risk. One, the sleeping volcano has a chance to get blown any moment of time. Second, whatever discrepancies are found at a later stage (because of delayed reviews and management/ PMO ignorance/ lenience), it will not be less than a postmortem rather than a proactive approach to mitigate risks.
This in turn will be create havoc for the running project in terms of delays in timelines, overshooting budgets, frustration among teams, compromise with quality, customer dissatisfaction, and scope creep.
Enterprise Project Governance: A Guide to the Successful Management of Projects Across the Organization by Paul C Dinsmore and Luiz Rocha
This excellent book Enterprise Project Governance: A Guide to the Successful Management of Projects Across the Organization by Paul C Dinsmore and Luiz Rocha was released in 2012 that covers all major guidelines for handling large sized enterprise project. It also covers bottlenecks encountered during such project and how to mitigate those risks. Overall it contains 13 chapters taking you to a high maturity level step by step in management of governance of enterprise projects with least possibility of succumbing to failures. The journey starts with an elaborative but crisp introduction to enterprise project governance. It further delves down into the crux of governance of enterprise projects and how do you strategize it to make it a grand success. Next it takes to the risks involved in enterprise projects and how to mitigate the risk of uncertainty arising out of those risks. Portfolio management itself is a big thing in enterprise project and it is important to learn mapping of right portfolio with corresponding project.
Practicality of life begins in a project when you start making your strategies formed in the earlier stage into realities and thus start bundle of problems with that. There would be some pre conceived and anticipated problems but usually there are a separate set of problems that occur unalarmed and with no pre-notions. For that there needs to be a structured organization for managing projects along with appropriate management of stakeholders. It is also necessary to understand the role of the sponsor in enterprise projects. You get an insight on controlling and managing performance in order to avoid a situation where you start compromising with timelines, financials and/or the quality of deliverables/ milestones. There is a separate chapter exclusively covering very large sized project termed as mega projects. The same chapter also covers joint ventures and alliances engaged in enterprise project governance.
The last chapter covers challenges and roadblocks having a possible occurrence in all aspects and how to manage these challenges and roadblocks. Overall Enterprise Project Governance: A Guide to the Successful Management of Projects Across the Organization by Paul C Dinsmore and Luiz Rocha is a must read book for all project managers and stakeholders involved in Enterprise Project Governance. 271 pages of journey will end up with Sarbanes-Oxley Compliant Projects, notes and sources, glossary and abbreviations & acronyms thereby making your overall journey well enriched with various learning insights.
Basically Enterprise Project Governance is all about enterprise projects and their plan of execution with zero risk of failure. Governance is an integral part of tasks, activities, projects where different teams join hands to fulfill different modalities of those tasks, activities and projects. Governance is required to ensure completion of those tasks/ activities of projects within stipulated period of time, budget and quality committed and agreed upon among various stakeholders.
Large projects with higher volume of intricacies require higher level of governance with higher amount of seriousness. To execute large projects, there definitely need to be a structured and clearly defined approach which needs to be signed off by all concerned stakeholders. Timelines not only bind internal teams but the customer also is bound to adhere to timelines specified in project plan in order to benefit him at large.
At many places during different phases during project lifecycle, a project manager will have to take a detailed stock of situation so as to ascertain reorganization of plan in order to fill the gap between plan and actuals. A realignment might demand of extra efforts during such shuffles but that is important to do so as to ensure no delays in time and no compromise with the quality of deliverables.
The project approach that is defined and signed off at the start of a project has to be followed by each person involved in the project during the development and execution of a project. It is assumed that initiation phase meets its timelines most of the time and most of the hiccups arise during a project are either during development phase or its execution phase. Progress of a project is measured by means of objectively defined milestones, targets and releases defined with their timelines.
Any timeline anticipated in getting delayed to its execution needs to be alarmed as soon as comes into notice. Appropriate actions need to be taken so as to get the train back on track rather than wasting much time in postmortem of delays happened. Though analysis and in-depth probing is definitely a solid tool for learning of factors that caused delays and helping in future projects in controlling those factors, it can be done post release of major milestones or at a stage when the project is passing through happy state.
Ultimate goal of any project is to get what was planned during initial phases – in right shape, in right time, and of committed quality.