true – Page 5 – Godinterest

May 9, 2016July 1, 2022

The New Day: How Should I Think About My Failures?

Everyone wants to be a success. I have never met anyone who purposely set out to be a failure. Undoubtedly, this is why so much has been written on the topic “How to be a Success” and why these books are so popular.

However, The New Day daily newspaper closed just nine weeks after launching, Trinity Mirror confirms.

The New Day was a British compact daily newspaper published by Trinity Mirror, launched on 29 February 2016. It was aimed at a middle-aged female audience and was politically neutral. The editor, Alison Phillips, intended readers to get through the newspaper in under 30 minutes.

The new paper was initially available for 25p for two weeks, then rising to 50p. Two million copies of the New Day was given away on the first day, as the turquoise-branded upstart attempted to spark a revival in readership and gain ground against the mid-market Mail and Express offline.

Arrogance about their own ability to rescue a situation can prevent leaders from changing course

The New Day had no leading articles, no website, and columnists and believed it could successfully drag readers back to print? The sad truth is that it did not attract enough attention and failed to create a daily newspaper that could co-exist in the digital age, especially as tabloids and broadsheets continue to suffer a significant circulation decline.

Shareholders at Trinity Mirror’s annual meeting called the failure “demoralising”. Analysts said it was “embarrassing”.

Assume for a moment that the leaders of The New Day had no idea about the changes swamping the print media as a result of the digital revolution, and carelessly decided to invest millions into the venture without undertaking a risk assessment and also decided to ignore every indication that the paper was failing. That would have been embarrassing and demoralising.

However, the leaders decided to fail quickly and shut down the project they started.

Abandonment is a rare, difficult and a valuable management skill. The natural instinct of most people is to persist, particularly when the project is a collective commitment, as most corporate ventures are, but then it becomes even harder to hit the red “stop” button.

The New Day’s editor, Alison Phillips, said in a statement posted on Facebook that the team “tried everything we could” but were unable to reach the figures needed to make it work financially.

We dread failure. We don’t like talking about it. Some of us will internalise and rethink our failures in our heads time and time again. Others will swipe them away, moving onto the next thing immediately. In the public, we prefer sweeping our failures under the rug, silently, while nobody is watching.

While this might save our feelings momentarily, this is not the way learn and innovate.

According to Albert Savoia – ex Googler and innovation expert, most project innovations will fail.

“Most New Things Will Fail – Even If They Are Flawlessly Executed.” – Albert Savoia – Ex Googler

Does this mean you should stay away from trying new things (and failing in the process)? Certainly not. It just means you need to accept failure will inevitably be a part of the process.

In most cases, however, a combination of arrogance about personal ability to rescue the situation and blindness to the lengthening odds of success stops leaders from changing course.

The natural lifespan of most projects is finite, and the rarities are companies that survive.

The Art of “strategic Quitting” Will Become More Important as Careers Fragment and Companies Exert More Discipline

So if an idea is doomed, organisations usually treat the person who pulled the plug early on as a hero right? Not exactly, it’s complicated.

Roy Greenslade, Professor of Journalism at City University London, wrote a report in The Guardian explaining how The New Day had failed. He pinpointed the error of marketing a newspaper to people who inherently despise newspapers, and the short period of time between the announcement and launch, leaving no time to advertise the product. It was also published early in the evening thus missing out on late-night breaking news such as Leicester City F.C.’s shock win of the Premier League.

“Nothing so powerfully concentrates a man’s mind on innovation as the knowledge that the present product or service will be abandoned in the foreseeable future.” – Peter Drucker

The first thing the Bible wants to say is that all of us have failed. None is without failure. If you think you haven’t failed, two things are true of you. One is you are blind to your failures and the other is you probably haven’t taken enough risks to try enough hard things so that you would be aware of your failures.

Peter Drucker’s influence on business management is legendary. Peter realised that “systematic abandonment” a regular, unsentimental spring-clean is critical to the fostering of new business ideas.

Conclusion, every organization needs to have a regular “rummage sale” to determine which products, services, and programs are worth keeping and which ones must be abandoned.

March 29, 2016July 1, 2022

33 of the Most Inspirational Leadership Quotes for You to Live By

We’ve all seen quotes designed to motivate or inspire us. Well, according to a new study, people who post these ‘inspirational’ quotes also have lower levels of intelligence. However, Godinterest disagrees, and see’s some quotes as universal nuggets of wisdom. You know the ones – those quotes that give you “Aha!” moments of inspiration or meaningful insights into your personal and professional lives. These are the ones you want to print out and place on your fridge so you’ll see them every day.

This collection of inspirational quotes features some of the all-time classics you may know, as well as some lesser-known ones you’ll love too. If you have any quotes you would have added, feel free to share in the comments section!

“The reason most people never reach their goals is that they don’t define them, or ever seriously consider them as believable or achievable.” – Denis Watley
“Our goals can only be reached through a vehicle of a plan, in which we must fervently believe, and upon which we must vigorously act. There is no other route to success.” – Stephen A. Brennan
“Without goals, and plans to reach them, you are like a ship that has set sail with no destination.” – Fitzhugh Dodson
“Goals are dreams with deadlines.” – Diana Scharf Hunt
“You must have long-term goals to keep you from being frustrated by short-term failures.” – Charles C. Noble
“Crystallize your goals. Make a plan for achieving them and set yourself a deadline. Then, with supreme confidence, determination, and disregard for obstacles and other people’s criticisms, carry out your plan.” – Paul Meyer
“The tragedy of life doesn’t lie in not reaching your goal. The tragedy lies in having no goals to reach.” – Benjamin Mays
“Progress has little to do with speed, but much to do with direction.” – Unknown
“The world makes way for the man who knows where he is going.” – Ralph Waldo Emerson
“Goals help focus you on areas in both your personal and professional life that are important and meaningful, rather than being guided by what other people want you to be, do, or accomplish.” – Catherine Pulsifer
“What you get by achieving your goals is not as important as what you become by achieving your goals.” – Zig Ziglar
“It doesn’t matter where you are coming from. All that matters is where you are going.” – Brian Tracy
“The true measure of a man is not how he behaves in moments of comfort and convenience but how he stands at times of controversy and challenges.” – Martin Luther King Jr.
“It’s not the load that breaks you down, it’s the way you carry it.” – Horne, Lena
“Difficulties are meant to rouse, not discourage. The human spirit is to grow strong by conflict.” – William E. Channing
“Nothing is particularly hard if you divide it into small jobs.” – Henry Ford
“It’s not whether you get knocked down. It’s whether you get up again.” – Vince Lombardi
“You must do the thing you think you cannot do.” E- Eleanor Roosevelt
“Motivation is what gets you started. Habit is what keeps you going.” – Jim Ryun
“Strong lives are motivated by dynamic purposes.” – Kenneth Hildebrand
“People who are unable to motivate themselves must be content with mediocrity, no matter how impressive their other talents.” – Andrew Carnegie
“Be miserable. Or motivate yourself. Whatever has to be done, it’s always your choice.” – Wayne Dyer
“The surest way not to fail is to be determined to succeed.” – Richard B. Sheridan
“A determined person will do more with a pen and paper than a lazy person will accomplish with a personal computer.” – Catherine Pulsifer
“There is no chance, no destiny, no fate, that can hinder or control the firm resolve of a determined soul.” – Ella Wheeler Wilcox
“It was courage, faith, endurance and a dogged determination to surmount all obstacles that built this bridge.” – John J. Watson
“Failure will never overtake me if my determination to succeed is strong enough.” – Og Mandino
“You’ve got to get up every morning with determination if you’re going to go to bed with satisfaction.” – George Lorimer
“We will either find a way or make one!” – Hannibal
“That some achieve great success, is proof to all that others can achieve it as well.” – Unknown
“Do not let what you cannot do interfere with what you can do.” – John Wooden
“Success seems to be largely a matter of hanging on after others have let go.” – William Feather
“Success is the sum of small efforts, repeated day in and day out.” – Robert Collier

March 24, 2016July 1, 2022

How to Cope with a Mis-Sold Job

Everyone knows a story about a smart and talented professional who has lost his or her passion for a role, who no longer looks forward to going to the office yet remains stuck without a visible way out. Getting on the career ladder is a great thing, you start off at the bottom and work your way up, but sometimes you can get stuck and do not even realize it.

“One in Five Employees Claim They Were Mis-sold Opportunities When They Joined Their Organisation – Kelly Global Workforce Index (Kgwi).”

Commenting on the findings, Debbie Pettingill, Director, Kelly Services UK and Ireland said

“Employee retention will become an increasing challenge for employers as we move out of the recession. As we move into a more candidate driven market, this trend is likely to accelerate. Our findings indicate that this problem is being exacerbated by the misrepresentation of job role or company culture at the interview stage, leading to the dissatisfaction of new hires.”

Most of us know what we are trying to escape a “mis-sold” job resulting in a narrowly defined career, inauthentic or unstimulating work, numbing corporate politics, and perhaps blackmail including direct threats of being used as a scapegoat. A job where you are both overlooked and underappreciated. One may ring true for some of you.

“Fewer than Half of Uk Employees Are Happy with the Way Their Careers Are Progressing According to New British Research.”

Why Would A Company or Person Block Your Move?

Well, this could be because of his or her personal insecurity i.e. as the team works well, why rock the boat? Comfort zone: sometimes the team gets too comfortable? Golden child syndrome: you’re working your butt off and your sponsor or other senior is reaping the recognition from your amazing deliverables?

Working a job you don’t like can leave you feeling stuck, forgotten by God, and asking yourself questions like:

Why hasn’t God opened another door for me yet?

Why is God not moving?

Why would God leave me here in this job I hate?

But the truth is God has not left you. He’s not holding back on you. When you feel God is silent, that’s exactly when He’s moving! Your situation does not change God. He still loves you and is with you no matter what.

Instead of looking at our situation from a perspective of fear and worry, we need to look at it through faith and hope.

What Can You Do About it?

Don’t fret, you can handover your work or completely leave the organisation and still stay sane. You might worry that announcing your intentions will cause your company grief, but ultimately you have to do what’s best for you no matter what!

Think and pray long and hard about how you’re going to drop this bombshell as you will need to give notice. A sound method is required to overcome the assault and possible backlash – including of course more prayer and fasting.

So how are you going to approach it? What’s your reasoning going to be? How are you going to get them to understand exactly why you’re doing this? What do you need to do in order to prepare for the big day?

Easy, you’re going to read this guide.

Strategy 1 – Remote Working Arrangement

This could be a great approach if 80% of your work can be undertaken remotely. However, while there is a very logical argument to be made in favor of working from home, many people equate remote work to a lack of productivity and laziness. These people do not realize that the switch from an office to working from home can actually lead to significant increases in productivity.

Strategy 2 – What’s in It for Me?

What’s in it for me? That question sounds a little selfish, doesn’t it? Maybe you aren’t being compensated fairly, or you’re not happy with the effort vs return. When you know your client and team needs you and you’re willing to stay for a price, don’t mess around. Give them the real number or offer that will make it worth your while to stick it out for awhile.

Strategy 3 – The Budget Cut

The re-structuring. The downsizing. The dreaded budget cut. Whatever name you want to give it, this can be terrifying for a lot of professionals. However, if you’re already thinking about leaving, so maybe it doesn’t have to be such a scary thing. In fact, maybe it can be extremely positive for both parties.

Strategy 4 – The Ease Out

Still feeling weary about leaving the organization. Propose easing yourself out of the post. Pick a time frame, maybe four weeks or so, and come up with a plan for slowly taking yourself out of the position. This also allows you some time to slowly ramp down your time commitment.

Strategy 5 – Burning Bridges in the Industry

“Sometimes it’s about networking and being nice to people and not burning any bridges – but remembering to draw line where you must.”

There’s no harm in an early exit from a job you never plan to mention again or an interim role where you have clearly agreed on a start and finish date. But if your manager is well connected to your industry you should try to leave on a good note. Why? Because it’s a small world and the next hiring manager may put in a call to his or her former colleague (a.k.a., your new manager) to get the unofficial scoop. It happens, so if you’re going to leave anyway then try to fulfill your end of the deal.

Strategy 6 – Get Moving Fast

Imagine, for example, that you were hired to help the company manage multiple programmes and projects across the globe, but a recent change in leadership means all efforts moving forward will be focused locally.

If you’re spending your days just trying to find ways to be productive or are undertaking a role you never signed up for, you have every right to pursue new opportunities. Of course, the first course of action should normally be to discuss this with your manager to see if there are other roles you can take on. But if you know that this isn’t going to happen in the new world, get moving fast.

Strategy 7 – Your Dream Job Awaits

“When you’re being interviewed, always treat the interview as a 50-50 thing,” says Andy Dallas, a director at Robert Half International, recruitment consultants. “Ask what you can expect to be doing in your first week, month and three months. Ask what a successful year looks like.”

Dream jobs don’t come every day. So, if you have a chance at yours, take it quickly and congratulate yourself for being strong enough to leave when you were unhappy.

Strategy 8 – Remeber to Be Patient

We will not always be in a job we desire. Maybe you are fresh out of school and are working a job that has nothing to do with the degree you just earned. Maybe you are in a situation where you are working at a job where you are overqualified, overworked, and fed up. Maybe, for the most part, you love your job but get discouraged by the mundane tasks that take up time from doing the aspects of your job you love most.

“Humble yourselves before the Lord, and he will exalt you.” – James 4:10 NIV

Here’s the thing: God will still use this season to grow, develop, and prepare you. Any season that humbles us is preparing us for what God has next.

Any thoughts to share?

March 16, 2016July 1, 2022

15 Shocking Project Management Statistics

The project management landscape is changing with an increased emphasis on productivity, reporting, and information technology. A number of studies have been completed that look into the success and failure rates of projects.

Below are 15 shocking statistics that reveal how project management has changed and is performing across various industries over the last 5 years.

There is projected to be 15.7 million new project management roles to be added globally across seven project-intensive industries by 2020 reaching an economic impact of over $18 trillion, across seven project-intensive industries including Manufacturing, Finance & Insurance, Information Services, Utilities, Business Services, Oil & Gas and Construction (Project Management Institute)
75% of IT executives believe their projects are “doomed from the start. (Geneca)
The healthcare industry is projected to increase project management roles by 30%, a higher growth rate than any current project intensive industry between 2010 and 2020. (Project Management Institute)
A third of all projects were successfully completed on time and on budget over the past year. (Standish Group)
80% of “high-performing” projects are led by a certified project manager. (PricewaterhouseCoopers, Insights and Trends: Current Programme and Project Management Practices 2012)
One in six IT projects have an average cost overrun of 200%. (Harvard Business Review 2004)
44% of project managers use no software, even though PWC found that the use of commercially available PM software increases performance and satisfaction. (Pricewaterhouse Coopers)
More than 90% of organizations perform some type of project postmortem or closeout retrospective. (The Standish Group: CHAOS Research Report 2013)
On average, it takes 7 years in the profession to go from entry-level to managing large, complex projects. (ESI International: Annual Salary Survey 2013)
The average large IT project runs 45% over budget, 7% over time, and delivers 56% less value than expected. (Project Management Institute: Pulse of the Profession 2015)
Only 64% of projects meet their goals. (Project Management Institute: Pulse of the Profession 2015)
60% of companies don’t measure ROI on projects. (KPMG New Zealand: Project Management Survey 2010)
The United States economy loses $50-$150 billion per year due to failed IT projects. (Gallup Business Review)
In just a 12 month period 49% of organizations had suffered a recent project failure. In the same period only 2% of organizations reported that all of their projects achieved the desired benefits. 86% of organizations reported a shortfall of at least 25% of targeted benefits across their portfolio of projects and many organizations failed to measure benefits so they are unaware of their true status in terms of benefits realization. (KPMG – Global IT Project Management Survey 2005)
According to an IBM study, only 40% of projects meet schedule, budget and quality goals. (Harvard Business Review 2004)

If you have any other project management statistics please share them with us.

February 20, 2016July 1, 2022

66% of IT Projects Fail

Is Britain a nation of slient Christians?

Only one in three software projects will turn out to be successful. According to Standish Group’s 2015 Chaos report, 66% of technology projects (based on the analysis of 50,000 projects worldwide) end in partial or total failure. More surprisingly, these statistics have been the same for the last five years, the report shows. Furthermore, 17% of large IT projects go so badly that they can threaten the very existence of a company.

On Average, Large It Projects Run 45% over Budget and 7% over Time, While Delivering 56% Less Value than Predicted

Despite such failures, huge sums continue to be invested in IT projects and written off. For example the cost of project failure across the European Union was Ã¢”š¬142 billion in 2004.

It Projects Always Come with an Element of Risk, but There Are Huge Gains to Be Had If We Can Just Avoid Some of the Factors That Contribute Frequently to Project Failure

What makes a IT project successful, though?

According to the Standish Group, a successful project is on time, on budget and has satisfactory results (value, user and sponsor satisfaction, and meets target requirements). Other measures of success are widely known and accepted as true such as getting requirements right, providing effective leadership, and having full support and engagement from sponsors and users. Without these, it’s unlikely that any project would succeed.

But there’s more to success than what is widely known and, apparently, rarely followed. To reduce the risk of failure for your tech project, here are six key actions to take on the road to success.

1. Executive Vision and Involvement

Without a Executive Senior Sponsor Its Easy for Projects to Fail with the Organizational Resistance That Accompanies Large Change

Executive involvement is a primary variable in predicting the success of an IT project. Having a leadership team aligned across an organization articulating the purpose, value, and rationale for a project goes a long way towards getting stakeholders and end-users pulling the proverbial rope in the same direction.

2. Have a clear view of scope and timetable

Oftentimes, a tech project flops because its developers fail to plan and rush forward with an idea. However, some project managers plan so meticulously that they end up falling behind and lose momentum. The best approach is somewhere in between.

Interviewing team members, documenting requirements, prioritizing what is “mission critical” versus “nice to have,” getting agreement across stakeholders can feel like a never-ending cycle. As a result, requirement gathering has fallen out of fashion with many organizations in the past few years.

However, the ideal starting point for a successful technology project is to have a set of fundamental requirements with sufficient detail to develop against.

Requirement Gathering Is Labour-intensive and Challenging but Remains the Roadmap and Measuring Stick for Software Projects

This approach allows you to maintain sight of the business benefits as well as engaging stakeholders and responding to their feedback. In combination with a clear business case, a well-defined set of requirements also simplifies design and testing, two areas where projects tend to go sideways.

Ensure that requirements for the project are clearly defined and agreed upon among stakeholders and that you have a way to track, measure, and manage changes in requirements as appropriate during the project.

3. Define how you will deliver

When it comes to delivering a major project, one size does not always fit all. All products are customizable to some degree, so what might have worked in one company may not work in another company.

That being said, why reinvent the wheel if it’s already proven successful? Sometimes it can be more beneficial to use an existing off the shelf solution. Whichever direction you take, choose the delivery mode that works best for your company.

4. Risk Identification and Management

Every project has risk and there are many factors out of your control. People leave the organization, for better or worse, leadership changes, budgets get cut, however, many risks to projects can be mitigated or even eliminated with some forethought and on-going management. For example, do you have the resources you need to deliver the project (resource risk). Are project goals clearly understood and requirements clearly defined (scope risk). Do you have a realistic project plan and timeline (time risk).

Mitigating Risk Is a Combination of Science and Art, and Always a Balancing Process

5. Test your product again and again

A technology project is something that should overall support your business. It should not be something that dictates and forces you to change your operations. If this is happening, you should shift gears and focus on tweaking the technology, rather than lowering expectations and adopting less ideal requirements.

Adequate testing is a must for any tech project. While some features may be fine with automated testing, the best approach is to have a dedicated testing team. Testing activities should mirror those with the development team throughout the project’s lifetime. With thorough testing, a project should deliver with less design flaws or missing requirements.

6. Prioritize simplicity and performance

Developers often leave the external look and feel of a product to the wayside thinking these things are not necessities for the consumer to enjoy. However, user experience is absolutely critical to the success of the project.

Developers must consider things like storage, network requirements, processing speeds and overall performance in order to satisfy the customer. If users are going to have to wait for an extended period to allow information to load, there must be a good reason for the wait, otherwise they won’t return for future products.

Simplification and Improved Efficiency Is What Adds Value

Ultimately, using the product should be a smooth and intuitive experience. Additionally, tools and alternative routes must be placed logically without being intrusive. The process can be complicated, but the finished product should emit simplicity. After all, that’s what makes companies like Apple so successful. Simplification and improved efficiency is what adds value.

November 23, 2015July 1, 2022

42 Masterful Quotes to Inspire Healthier Relationships

Conflict is part of our working life and is often used as a way to work out our differences and reach a conclusion. It’s usually the approach you take that tends to exacerbate the issues and cause undue stress. How you deal with conflict reveals your character.

The wise man doesn’t give the right answers, he poses the right questions — Claude Lvi-Strauss
A crisis is a turning point — Anne Lindthorst
Conflict is inevitable, but combat is optional — Max Lucade
Don’t be afraid of opposition. Remember, a kite rises against, not with, the wind — Hamilton Mabie
There is no way to peace. Peace is the way — AJ Muste
The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment — Dorothy Nevill
The most basic of all human needs is the need to understand and be understood. The best way to understand people is to listen to them — Ralph Nichols
The more we sweat in peace the less we bleed in war — Vijaya Lakshmi Pandit
To live a creative life, we must lose our fear of being wrong — Joseph Chilton Pearce
A man convinced against his will”¦is not convinced — Laurence J. Peter
My problem is I say what I’m thinking before I think what I’m saying — Laurence J. Peter
Discussion is an exchange of knowledge; argument an exchange of emotion – Robert Quillen
You can’t influence somebody when you’re judging them — Tony Robbins
Quarrels would not last long if the fault were only on one side — Duke FranÃƒ§ois de La Rochefoucauld
It is astonishing how elements which seem insoluble become soluble when someone listens. How confusions which seem irremediable turn into relatively clear flowing streams when one is heard — Carl Rogers
If it’s mentionable, it’s manageable— Mr. Rogers
Don’t let yesterday use up too much of today — Will Rogers
The best way to persuade people is with your ears, by listening to them — Dean Rusk
The greatest challenge to any thinker is stating the problem in a way that will allow a solution — Bertrand Russell
It is with the heart that one sees rightly; what is essential is invisible to the eye — Antoine de Saint-Exupry
Human beings love to be right. When a person is willing to give up being right, a whole world of possibilities opens up — Pete Salmansohn
The test of a successful person is not an ability to eliminate all problems before they arise, but to meet and work out difficulties when they do arise — David J. Schwartz
Why not go out on a limb? Isn’t that where the fruit is? — Frank Scully
Before you speak, ask yourself: Is it kind, is it necessary, is it true, does it improve the silence? — Shirdi Sai Baba
When things are not working for us, instead of fighting and struggling, we need to say, “What’s happening here? How am I not being true to who I am? What is pulling me away from my purpose?” — June Singer
The only people with whom you should try to get even are those who have helped you — John E. Southard
It takes two to quarrel, but only one to end it — Spanish Proverb
The first problem for all of us, men and women, is not to learn, but to unlearn— Source unknown
Confidence, like art, never comes from having all the answers; it comes from being open to all the questions — Earl Gray Stevens
Life is ten percent what happens to me and ninety percent how I react to it — Charles Swindoll
If you are patient in one moment of anger, you will escape a hundred days of sorrow — Carol Tavris
Peace is not the absence of conflict but the presence of creative alternatives for responding to conflict—alternatives to passive or aggressive responses, alternatives to violence — Dorothy Thompson
Let us not look back in anger, nor forward in fear, but around in awareness — James Thurber
A good manager doesn’t try to eliminate conflict; he tries to keep it from wasting the energies of his people. If you’re the boss and your people fight you openly when they think that you are wrong, that’s healthy — Robert Townsend
Knowledge becomes wisdom only after it has been put to good use — Mark Twain
People who fight fire with fire usually end up with ashes — Abigail VanBuren
The most common way people give up their power is by thinking they don’t have any — Alice Walker
It isn’t a mistake to have strong views. The mistake is to have nothing else — Anthony Weston
I’ve found that I can only change how I act if I stay aware of my beliefs and assumptions. Thoughts always reveal themselves in behavior — Margaret Wheatley
I would not waste my life in friction when it could be turned into momentum — Frances Willard
When you’re at the edge of a cliff, sometimes progress is a step backward — Source unknown

November 21, 2015July 1, 2022

The Good, the Bad and the Ugly of Requirements Management

The Good, the Bad and the Ugly of Agile Methodologies

Most project managers know the importance of requirements management. Without a solid foundation and grounding in the subject, requirements management quickly turns towards the complex and difficult side.

Why Manage Requirements?

In the final analysis, all projects are completely driven by requirements. Requirements are usually not cast in stone. Stakeholders gather insights and more knowledge of their true needs with time. This means that they can change their minds about requirements, no matter how late in the game. Requirements should therefore be managed proactively in anticipation of change.

However, if requirement definitions are not set up properly in the first place, expect that the quality of delivery will suffer, along with more schedule delays than imagined, and a big drain on the budget.

Broad project requirements help to establish a baseline for objectives. Subsequent change requests would thus require approval by the right authority; a change control board is usually set up to investigate and approve changes to requirements. The objective of baselining is not to prevent or discourage changes, but to ensure that approved changes are relevant and deserve the priorities assigned to them.

The simplest way for project managers to reduce the probability of missing critical requirements is to hold requirements review sessions to ensure that stakeholders understand the requirements and that any ambiguities, inconsistencies and omissions are identified and addressed to facilitate requirements approval or sign-off.

However, when inaccurate requirements are in play, team members end up reworking those activities multiple times. The only sensible course of action is to deliver requirements up front in an accurate manner. That way team members will be able to immediately identify any missing components early in the project lifecycle.

It’s vitally important to employ tools designed to assess requirement quality at the beginning of the project. These tools will help to identify any requirements that are vague or missing early enough to improve the changes of success for the project. Even simple tools like guidelines and checklists can solve major problems later on. You may also consider automated tools, depending on your level of technical expertise.

The Good, the Bad and the Ugly of Requirements Management

Good Requirements

Requirements that meet the “good” standard are ones that anyone can easily evaluate to quickly and clearly determine that all the needs have been accurately met by the project.

The common criteria used by project teams to properly evaluate requirements is as follows:

Verifiable: Ensure that all deliverables are able to be evaluated to ensure they have met all necessary requirements. Verification techniques such as modelling, analysis, review by experts, simulations, and demonstrations or testing.

Testable: Requirements are able to be assessed using the most basic of all criteria. This includes quantitative measurement like “pass or fail.”

Traceable: Requirements should be tagged to specific sources. Examples are compliance requirements, best practices, industry standards, and use cases.

Clarity: All statements should be presented in unambiguous ways so the cannot be interpreted differently by different team members.

Bad Requirements

Bad requirements are marked by their incompleteness and lack of clarity. They are hard to understand and implement. They generally possess these characteristics:

Inconsistency: Without clarity, you’ll find requirements that are in conflict with other requirements! This is very frustrating because there’s no way that either one will ever be satisfied.

Non-valid: These are requirements that team members simply cannot understand. They will never be able to accurately assess or approve non-valid requirements.

Non-ranked: These requirements have not been correctly prioritised. Without proper ranking, it’s difficult for team members to be able to assess them properly.

The risk to the project not meeting the clients expectations is not something that will ever be entirely removed. However, having a specific criteria upon which to benchmark a project is a great way to reduce this risk.

Risks fall into two main categories. Systemic risk is inherent to the nature of the work and cannot be avoided. The non-systemic risk is a bit different and relates from the activities in the project itself. One of the greatest of all non-systemic risks is that of bad requirements management.

Teams that wish to reduce the risk of the project not meeting the clients expectations substantially are best served by establishing specific requirements in the initial stages. Common goals like being “on time and on budget” while maintaining a high level of quality will require dedication from teams members who have eliminated as much non-systemic risk as possible.

When you’re next involved in a project where requirements come up in a discussion, always pay careful attention to the good, the bad, and the ugly that could result without proper due care and attention.

November 15, 2015July 1, 2022

Taking the Right Path to Good Agile Implementations

1) A Wise Man Said Only Fools Rush In

Companies that goes nuts for agile because they know they have to deliver faster and for less cost to keep up with competitors may be making a big mistake and face a collapse of their efforts.

If they focused first on a deep understanding of their business’ needs, they could more accurately decide if agile is a good fit. A better approach for you to take is analyse your current processes to determine if agile methodologies actually support your goals and needs.

2) Educated Stakeholders Make Excellent Allies

Agile works from a focal point of improving quality delivery and frequency. It does not start with reducing time to market or cutting costs. Those benefits are a result of implementing agile methods over time, after the requisite investment of time and resources has been made.

3) Don’t Do the Project Without at Least One Committed Product “Owner”

A “product owner” is a the committed business leader who will make or break the project. This person will be expected to put at least half of their time into the project. They’ll also be responsible for getting all the decisions made through the right channels in a reasonable period of time. You must have a leader like this to succeed.

4) Gain Consensus on the Definition Of “Finished”

Everybody on-board needs to agree on what constitutes being finished with any stage of implementation. For some, it will mean that by the end of each and every iteration, the production-ready software will be available. This is not always possible, so get out ahead of a potential problem and gain consensus.

5) Build an Exceptional Cross-Functional Team

Cross-functionality is what separates the ineffective agile teams from the high-performance ones. Team members have to be proficient in performing any and all necessary tasks so that they’ll be able to always deliver what the customers need.

Team building requires that you identify the right parties and that you shape them into a functional team by making sure that they share your own true goal of always delivering massive value to product owners.

6) Make the Proper Investment in the Tools That Support Agile

The beginning stages of any agile project will involve you investing in the of the robust frameworks, infrastructure, and process automation tools that fully support agility. This includes a wide range of solutions like continuous build servers, automation testing, video conferencing, interactive chat, and software frameworks. Don’t scrimp on other important details like the solution architecture, either.

7) Retrospectives Need to Be a Main Priority

Inspection and adapting are the keys to agile. Organisations using this methodology use a vehicle called “retrospectives” to ensure these tasks are being performed correctly. A proper retrospective should embrace the qualities of self-improvement and transparency. Any actions that are a result of the retrospective must be given the highest priority. This is especially true of estimations, which are crucial to achieving the kind of team velocity that keeps projects on track.

8) Start the Project with a Solution Architecture

Even though documentation is not always the most glamorous part of any project, you’ll be well served to make sure you understand that documentation is still important to a successful project. Using a solution architecture pays off because it serves a blueprint for the final project that will be delivered by the team. Team members need this document so they understand what will happen if they make changes. Members who are added to the project at later days will use the documentation as a reference point so they can be brought up to speed.

9) Embrace the Fact That Change Is Coming and Plan for It

You can’t make a change without a cost in agile. Change is something you always have to embrace philosophically, but be aware of the costs and the impacts to the project. When you are doing the estimation process, factor in potential changes when applicable.

10) You and Your External Partners Should Have an Agile Relationship

Agile is not always the best fit for traditional vendors. They prefer contracts that use fixed prices and fixed outcomes. When you switch to agile you’ll need to make a point out of understanding the ramifications the changes will have with your vendors. You and they may have to make some changes to keep the relationship running smooth.

Try to build a transparent relationship with all of your external vendors. Risk Reward contracts that employ clearly defined KPIs work amazingly well for agile organisations.

November 13, 2015July 1, 2022

The Good, the Bad and the Ugly of Agile Methodologies

The “agile” buzzword has really taken hold among a myriad organisations worldwide. That result is not particularly surprising. Who wouldn’t love to employ light and fast tactics that allow them to respond to rapidly changing challenges? Despite all the optimism about agile methods, the bigger question is how well companies are actually doing when it comes to employing these methodologies in the real world. Without understanding what the core objectives of embracing agile methods are, it’s not going to be easy to gain results.

Agile methodology is employed in order to reduce the time, risk, and cost that is associated with a project. However, these massive benefits are not going to materialise out of thin air. They are the result of the dedicated work of a team who is well versed in implementing the methodology.

To become “agile” will require organisations to take a quantum leap in their culture. They will have to embrace the entire philosophy behind these methods or no real change will take place. Truly agile companies are the ones that have gone through a transformative process in order to implement brand new processes that say goodbye to the past. This takes a lot of work and effort and not all organisations are willing or able to do this.

Ugly Agile Implementations

Project teams that are solely focused on results and who don’t do their homework end up with very ugly agile implementations. These teams are so excited about agile as a concept that they convert everyone in their organisation into adopting the methods. The problem is, they do not spend the requisite time getting everyone on board with exactly what needs to be done.

Because of this oversight, the projects are plagued with poor communications and engagement. The project team and others in the organisation are each working on their own tasks with no thought to how the pieces fit together in the “big picture.” This is a major problem because agile methods really only shine when the whole organisation works as one well-oiled unit. In this scenario, major issues at the core of the project are neglected and the entire project goes off the rails. This leaves a bad taste in the mouths of managers, who are no longer excited about agile methods.

Really ugly agile implementations have the wrong focus. Because of this myopia, the true benefits of agile employment are never realised. Before long, things, unfortunately, go back to “normal.”

Bad Agile Implementations

Some businesses completely miss the boat when it comes to agile deployment. They’re interested in receiving the benefits of reduced costs, faster time to market, and cutting “red tape.” Despite this knowledge, they’re not truly committed to the all of the values that are espoused by the Agile Manifesto. Without this commitment, they cannot possibly hope to fully embrace a functional implementation.

Organisations like to invest in education and communications, but they ignore important concepts like utilising the tools that help them truly embrace agility. They even form teams that understand cross-functionality, but without empowerment they are unable to make vital decisions.

Lastly, organisations that do poor agile implementations perform project reviews regularly enough, but the input from the meetings is never acted on by anyone. The key issues that are preventing proper implementation are never properly addressed and the project fails on its promise. Organisation members swear off the agile methods forever at this point.

Good Agile Implementations

When business personnel and IT staff work together, good implementations of agile are the result. These units work together so that a project delivery methodology is presented to the organisation that meets its needs. They also spend the time to create the cultural changes needed to ensure the methods are successful.

In organisations like this, team members, business end users, along with senior management and key stakeholders received a continuous education that empowers them all. Cross-functional teams that excel are the results. These organisations also invest in the techniques and tools that fully support agile. That includes test driven development, continuous builds, new standards, and more. With these in place, a platform that ensures long-term success will be installed.

Particularly telling, these businesses conduct regular project reviews which they conceptualise as opportunities to improve instead of something that simply has to be done. When change is needed, they embrace it and plan for it. When it arrives, they are ready and the organisation continues to excel. A sign of a good agile implementation is when the organisation is commits to making long-term changes that will benefit the methodology in the long run.

It doesn’t pay to underestimate just how difficult implementing good agile really is. Since major internal changes to how project delivery is done need to be embraced, the road ends up being a challenging one. Traditional managers will be challenged because empowered teams now have more input than ever before.

Once a good agile implementation is in place, the benefits are obvious and plentiful. An energised, cross-functional community of empowering people who are all focused on common goals get more done than ever before. Good implementation put platforms into use that improve project delivery because they allow for test-driven development, continuous integration, standards implementation, and best practice design applications.

November 3, 2015July 1, 2022

Top 10 Project Management Myths Debunked

Since the dawn of time, mankind has used myths to make sense of the uncertainty that surrounds us. In the early 1990s a lot of people believed that project management was the best kept secret in business. However, because project management was not seen as a prevailing profession at that time, it suffered from a lack of awareness which was in a sense, a double edged sword. Those who were knowledgeable in the practice of project management became extreamly valuable to organisations and pioneers for the profession.

These early adopters were able to convince organisations that project management practitioners were needed. Myths around project management began to form in the business community and as the role of the project manager was unclear, questions were raised as to what project management was and what it could offer organisations.

The definition of the word myth is a “widely held, but false belief or idea.” Here, we’re going to examine 10 of the most pervasive PM myths that have emerged.

Myth #1 – Contingency pool is redundant

This is one of the most ‘mythical’ myths that has plagued the industry for a long time. Coupled with the tendency to presume that ‘real work’ is tantamount to implementation or building something concrete and you have the perfect recipe for project disaster. The thought pattern behind this approach typically originates from budget constraints and/or having unrealistic expectations. As we all know, or should know, the unexpected happens quite regularly. An effective contingency plan is important as it aims to protect that which has value (e.g., data), prevent or minimise disruption (e.g., product lifecycle), and provide post-event feedback for analysis (e.g., how did we fare? did we allocate funds correctly?).

Myth #2 – Project Management software is too expensive

If your idea of project management software involves purchasing servers, and purchasing a software application from a major vendor for a small practice with 10 practitioners then, yes, it is too expensive. If, however, you have gone cloud and elected to use a powerful web-based project management solution (such as Smartsheet), then you are likely to save thousands of pounds while reaping the benefits of a pay-as-you-go price structure. The present, and future, lie in cloud solutions that provide equal, or superior, functionality at a fraction of the cost.

Myth #3 – Project Management methodologies will slow us down

Project managers have a reputation of using process-intensive methodologies that favour ideology over pragmatism. In some instances this may, indeed, be the case when there is a mismatch between a specific project management approach and the organisation’s acutall needs (e.g., a process-driven method, such as PRINCE2, may not be appropriate for a slightly chaotic environment that favours an adaptive approach, such as Scrum). So, in sum, put down the paint roller (“Project Management isn’t for us!”) and take out your fine-bristled brush (“The Critical-Chain method may not be our cup of tea, but Agile on the other hand”¦”).

Myth #4 – Facts and figures are more important than feelings and perceptions

While facts are very important, projects are often derailed and sabotaged because of false perceptions. The PM must pay attention to both fact and fiction to navigate through turbulent organisational change.

Myth #5 – Project managers need to be detail oriented and not strategic in nature

While it is of the utmost importance for the project manager to understand how to read the details of the project, they must also understand how the project supports organisational objectives. Having a strategic perspective adds great value to the skill-set of the project manager.

Myth #6 Rely on the experts in everything that you do

It is true, we do need to rely on the experts but our trust can not be a blind faith. The job of the project managers in this area is twofold. First we must extract information and second we must verify that the information is accurate. A good example of this is asking a planner to provide an estimate on the effort required to perform a task. In some instances team members forget to include tasks which ultimately results in a faulty estimate.

Myth #7 All the battles have to be fought and won so that we can succeed

Project managers sometimes make the assumption that they need to stand firm to get the job done, however, coming to compromise on a particular issue is often a better course of action in order to win the war.

Myth #8 Project Managers can wear multiple hats

Wearing different hats can be extremely confusing. This is especially true if the project manager is asked to be a business analyst or technical expert on top of serving in their PM role. They end up doing both roles with mediocrity. When we “wear two hats” we essentially tell ourselves that both hats fit on one head at the same time. However, what happens if the demands of two roles conflict and what assurances do we have that we’re managing the inherent conflict of multiple roles and the risks the roles introduce? Sadly, multiple roles become more common as we move up the management hierarchy in an organisation, and that’s exactly where potential conflicts of interest can do the most harm.

Myth #9 Once the risk register is created, it’s full speed ahead

Risk management provides a forward-looking radar. We can use it to scan the uncertain future to reveal things that could affect us, giving us sufficient time to prepare in advance. We can develop contingency plans even for so-called uncontrollable risks, and be ready to deal with likely threats or significant opportunities. Too often, it’s not until a catastrophic event occurs and significantly impacts project progress that ongoing risk reviews are conducted.

Myth #10 Project managers can not be effective in their role unless they have specific technical expertise in the given field that the project falls within

You don’t need to be an engineer to manage a construction project or a IT technician to manage a software development project. All you need is a fundamental understanding with strong PM skills to manage the team. Experience in the field helps but does not guarantee success.

Project management is challenging enough without the myths. The profession has come a long way since the 1990s and some of these myths are fading. However, we still see remnants of them in one form or another. Great projects cut through false assumptions and confusion, allowing their teams to make smart decisions based on reality.

These are just 10 project management myths, what are yours?

October 24, 2015July 1, 2022

9 Suggestions for Overcoming Barriers to Good Design When Using Modern Methods of Construction (Mmc)

The term ‘Modern Methods of Construction’ (MMC) embraces a range of technologies involving various forms of prefabrication and off-site assembly.

MMC is increasingly regarded as a realistic means of improving quality, reducing time spent on-site, improving on-site safety and addressing skills shortages in the construction of UK housing.

The variety of systems now available potentially allows the designer enough choice to sidestep problems deriving from constraints posed by the use of any one method. MMC systems, from closed-panel timber framed systems to bathroom pods are a palette from which designers can make choices. They are not necessarily stand-alone solutions that anticipate all the needs of an individual site and can be mixed and matched as appropriate.

These limitations are not obstacles to achieving the good design in MMC-based schemes, but may hinder the incorporation of more complex and innovative types of MMC from which greater overall benefits may be obtained which are considered under the following headings:

1. COST UNCERTAINTY

There is no doubt that, given products of comparable performance the key issue in purchases of MMC construction systems is the price. At present not enough is known about the potential costs of using volumetric and closed panel systems to enable confident specification at an early date. This inhibits designers from exploring the full potential of MMC systems. This is particularly true of the less repetitive, small, one-off scheme, where a smaller margin of benefits is gained from using MMC. The principal barrier to the uptake of MMC, therefore, seems to be the perception of cost uncertainty with respect to using more complex systems. Without doing substantial project-specific research, consultants and their clients simply do not know with enough degree of certainty how much the volumetric or closed panel systems are likely to cost, and what would be the savings to overall project costs produced by potential speed gains to offset against increased capital expenditure.

This is due to the complexity of assessing the ratio of cost of repetitive elements where pricing is relatively straightforward to the cost of adjusting elements or building in another method for the abnormal condition. Decisions to use innovative systems are likely to be made once designs are well progressed to enable teams to be more certain of costs. This can increase the potential for change or result in design compromise as the designer attempts to incorporate the specific limitations of a particular system in their design.

In an attempt to improve this situation, the MMC consultant and or clients could pull together a directory of MMC expanded to include cost comparison data. The huge range of variables involved inevitably makes this difficult, but a database of current construction cost information would be an invaluable resource.

2. PLANNING PROCESS AND EARLY COMMITMENT TO A SYSTEM

The time it can take to obtain planning permission has obvious implications both for project cost but also, in some circumstances, for architectural design innovation.

Most of the more complex types of MMC have an impact on dimensioning, the choice of external finish and detailing may have some effect on the buildings mass. Therefore, the construction system should be chosen prior to a planning application to avoid abortive work, redesign or amendment, or even resubmission for planning permission.

However, developers whose money is at risk, frequently hold off deciding on the construction technique until the last practicable moment, in order to get any advantage from fluctuations in material or component pricing.

Given the potential for lengthy duration of planning applications, this means that there is little incentive to prepare initial designs for planning with a prior decision to incorporate MMC firmly embedded. In cases where the developer has a financial or business link with the supplier, this is less likely to be the case. As the majority of commercial or residential developments involve some kind of arrangement with a developer, agreement on construction systems is often left to the stage after planning.

3. TIME INVESTMENT

Another very significant factor is the time investment required at the early stages of projects. This is needed to develop the design when the project is still at risk. There is a direct relationship between the scale and complexity of MMC component and the amount of time required to develop a design at an early stage.

The introduction of advanced or complex MMC techniques into the design process is potentially costly to the design team. A significant amount of research is needed to explore alternative systems, to obtain verification of suppliers’ credentials, investigate mortgage and insurance issues, visit previous sites, talk to system suppliers, obtain technical performance guidelines, understand junctions and interfaces, coordinate other consultants, obtain building control input and so on.

For a consultant, the only way of investing in this research is either through timely payment of increased fees by a visionary understanding client or through the anticipation of increased future productivity through repetition when a project is phased, or large enough, or likely to be followed by another similar project.

The potential of learning a system and then being able to repeat lessons learned efficiently is a powerful incentive for both client and consultant. By contrast, HTA’ s project at Basingstoke is an example of a phased project with a three to four-year duration allowed the design team to repeat various elements of the design, and the manufacturer to develop improved solutions to technical and supply problems.

4. INSUFFICIENT COMMUNICATION

Improved dialogue at the outset of the project is vital if design quality is to be maximised. Constraints and opportunities implicit within a particular system are more easily incorporated into design if partners communicate pre-planning. Increased early communication can be fostered through improved long-term partnering relationships.

Clients should also partner with a range of suppliers and architects so that choice and flexibility is not restricted.

5. INEXPERIENCE

Generally, the inexperienced client or design team will have to do more research, with the result that there is likely to be significant design development without a specific system being incorporated.

This is a disincentive to using a more complex system involving a higher proportion of MMC, where early decision making and knowledge of a system’ s capabilities have a decisive influence on the nature of the architecture. However, encouraging the take up of MMC through the use of a dedicated funding mechanism may assist clients in finding time for research into suitable MMC techniques.

6. SUPPLIER’S ROLE

Site capacity studies and early stage pre-planning design studies could be undertaken directly by system suppliers on behalf of clients, cutting out the usual procedure of commissioning design work by independent consultants.

7. ASSUMPTIONS

There are a number of assumptions that are generally held about certain types of MMC that may have been valid at one time but are no longer true today. There is a need for reliable and up to date information comparing system criteria, performance data, timescales, lead in times, capacity, construction time, sequencing issues, limitations, and benefits.

Therefore it would be helpful if a forum for discussion and experience exchange was set up.

8. DEMONSTRATING THE BENEFITS OF MMC

There is still a large amount of skepticism about the need to go very far down the line with MMC. This is reflected in the acceptance of the desirability of maintaining or indeed enhancing the pool of traditional craft skills throughout the UK.

A balanced view is that there is a demonstrable need for the wider use of MMC which is recognized by both industry and government. The best way for clients and the public generally to become more confident and knowledgeable about the quality of design achievable through MMC is to see it demonstrated.

9. FINANCIAL INCENTIVES

There is no doubt that spreading the burden of investment through the life of a project helps to ensure a higher standard of specification and hence quality. In the Netherlands, a ‘ Green Financing’ system has been developed by the Dutch government that provides favorable loan finance when certain sustainable standards are reached. In the UK, the Gallions HA has pioneered a study of this, based on a scheme in Thamesmead, ‘ the Ecopark project’.

Eco Park is an eco-friendly business park built on the False Bay coast. This business park is at the cutting-edge of sustainable design and offers a unique working environment in a secure, well-managed facility.

October 7, 2015July 1, 2022

Playing God: Swedish Train operator uses Big Data to ‘avoid train delays that haven’t happened yet’

In a sign of things to come, a Swedish train operator is using new technology that employs big data to predict the entire commuter train system two hours into the future.

Welcome to the world of “Big Data.” We have more information at our fingertips than any generation in history. We live in the world of “Big Data.” That is the new way people are trying to describe this sea of digital facts, figures, products, books, music, video, and much more. Twitter, apps, Facebook–they’re each giving science new ways to look at what people do and why.

“Hopes, fears, and ethical concerns relating to technology are as old as technology itself.”

We actually welcome some aspect of Big Data. These mysterious data successes (or accidental successes) are easy to see as a kind of Big Brother future, where technology can track your every move and report back to ”¦ someone. However, StockholmstÃƒ¥g, the train operator is using new technology that employs big data to predict train delays before they happen.

“The Commuter Prognosis – A Social Scientist’s Dream Come True.”

The mathematic algorithm, called “The commuter prognosis” was developed in Stockholm, Sweden.

When a train is not on time the algorithm forecasts disruptions in the entire network by using historic big data to prevent the ripple effects that actually causes most delays.
Wilhelm Landerholm the mathematician who has developed the algorithm said:

“We have built a prediction model, using big data, that lets us visualize the entire commuter train system two hours into the future. We can now forecast disruptions in our service and our traffic control center can prevent the ripple effects that actually cause most delays.”

The algorithm has been tested but is not currently being used by traffic controllers.

How does it work?

The key to the model is a large amount of historical data. The model works similar to a seismograph, an instrument that measures and records details of earthquakes, such as force and duration, but instead identifies late train arrivals. When this happens, the system uses historical data from previous occurrences to forecast the likely impact on the entire train network.

Real-time public transportation information is already used around the globe, however, traffic control centers still typically assess delays manually to try and prevent further problems in a network. The commuter prognosis system, on the other hand, will forecast these delay effects instantaneously and provide a prediction of how a single or multiple disturbance might affect the whole train network. The commuter prognosis system could change how traffic control centers operate all over the world.

“The Effects of One Delayed Train Can Quickly Multiply Within a Train Network”

Imagine that “The commuter prognosis” forecasts that a train will be 10 minutes late to station C in two hours. To deal with this the traffic control center issues a new train from station A that will arrive on time at station C. As soon as the new train has been put in motion the algorithm re-calculates and gives the traffic control center a new forecast for the entire train network within minutes.”

The most important benefit of “The commuter prognosis” is that it provides for a more punctual public transportation.

“The commuter prognosis” will be available in a smartphone app based on the original model. The app will integrate with other transportation big data to make commuting easier and will indicate which coaches are more or less crowded.

Big Data, Ethics, and Religion

These stories remind us that even though companies and governments are doing amazing things with data, it’s at best imperfect. The algorithms and programs they use to filter and respond to data are at least as fallible as the human beings who designed them. We can also see its complexity and failures as evidence of the amazing omnipotence of our God – who doesn’t make errors and who knows right where to find us, even inside a great fish or the depths of hell.

The arrival of big data has already brought with it numerous questions that have yet to be properly addressed. These questions are methodological, epistemological, and ethical, and they concern (inter alia) the ways in which data is collected, stored, interpreted, represented, and traded. A further complication is a speed with which data science is advancing, which means that (for example) the application of legal and ethical restrictions to the practice of that science will always risk being several steps behind the point that it has currently reached. There are indications that we are currently sleepwalking towards a situation in which the commercial exploitation of big data routinely increases social division, and renders privacy a thing of the past.

Ket factors

A mathematical model interprets big data to forecasts for each train in the train network.
The commuter prognosis can warn about delays two hours before the departure or arrival actually takes place.
The commuter prognosis calculates how the delay affects other trains in the system.
The purpose of “the commuter prognosis” is to make life easier for traffic control centers and to give passengers a better service.
In the future, the algorithm will be potentially adaptable for more types of public transportations and cities.

January 21, 2013January 15, 2024

Marcus Garvey

Marcus Garvey was a Jamaican political leader and civil rights activist who advocated for the rights of people of African descent. He is best known for his vision of an independent, self-governing black nation and his promotion of the “Back to Africa” movement, which encouraged people of African descent to return to their ancestral homeland.

Garvey believed that people of African descent, who had been dispersed around the world as a result of the slave trade, needed to come together in order to achieve political and economic power. He felt that they would never be treated as equals in white-dominated societies and that their only hope for true freedom and self-determination was to create their own independent state.

He founded the Universal Negro Improvement Association (UNIA) in 1914 and worked to build a sense of pride and unity among people of African descent. Through the UNIA, he encouraged the development of businesses, schools, and other institutions that would serve the black community. He also organized a “Back to Africa” movement, which sought to establish a new nation in Africa where black people could live free from discrimination and oppression.

In addition to his work to promote the rights of people of African descent, Garvey also advocated for the rights of workers and the poor, and spoke out against colonialism and imperialism. He was a charismatic leader who inspired many people and his ideas continue to have an impact on the lives of people of African descent around the world.

It’s worth noting that Garvey’s ideas and movement also met with a lot of criticism and opposition, specially from the Jamaican political and economic elite and some black leaders.