Focus on the Short Term But Think Big Picture - Development
This is your new mantra. The creed of project management. Your concept and conviction.
Every decision you make will have effects on the project’s flow; both long-term and short-term. You might hear developers referring to the course it takes, the course or the track of a project. They might spend time coordinating the project, channel-correcting, or fine tuning the heading.
All of this is project descriptors that refers to the flow of your project. The balance between performance and development.
The Balance
I think the simplest way to describe a symmetrical project is this: making progress toward the end-product while maintaining maximum yield.
It means that every decision you make is (as the project lead) proportional progress with direction.
Thinking Big Picture
Thinking big picture means being mindful of the state of your project over several months’ time. The challenge of thinking big picture is ignoring details. Tempting, enticing details that we all want to grasp and design and build mock-ups of and Holy Batman of web development, they’re grand. The fine points move us. The agile win.
Thinking big picture means breaking down the essential makings of your project from the billowing of details, and describing them in inexact terms. You conclusively oversee the work flow. You’re calling the shots and cultivating that order over a long period of time.
Focusing on Short Term
Now I’m not saying that the code never gets written. It’s just wasteful for us to write code without purpose. 110 lines of script in an afternoon won’t mean anything unless they have a purpose.
Thankfully, you’re a big-picture thinker, right? You’ve broken down the project into its fundamental parts, and you’ve got a few skillfully designed layouts to show how they annex. You’re ready to go!
Fixating on the short-term means getting detailed in small portions. In simple terms, you’ll take the ideas w/the greatest importance, and in a low-key, unflappable manner, start to juice out the specifics. Specifics that won’t be passed over, but instead will inhabit several days of development work.
So That’s All?
If you think this is transparent, then you’re a god among developers. If you have exposure to it, then you’ll know that no two projects that are ever exactly the same, but this notion prevails.