I'm wondering if this type of tool exists. Basically, I am senior dev of a 3 man dev team at a non-tech company. I maintain 60 or so web apps for our 300-400 users (all internal apps) as well as act as jack of all trades when it comes to SQL, IIS, self hosted and cloud hosted windows server boxes, VMware, etc. Basically, I have a lot of spinning plates.

We are in active development but we get interrupted a lot. Like, a lot a lot. Because of this, we don't really work based on deadlines but more on timelines. Upper management knows that things get priority over other things and we have to move things around and pivot a lot, so as long as we can explain why a project took 6 more months than we projected, it's fine.

So having said all that, I'm looking for a timeline system similar to gantt but I want the ability to have more than one "timespan" per task/row.

So for example let's say I'm building a to-do app and one of the tasks is to figure out the theme/color scheme of the app. I think this will take 3 days, and I don't really need to be more specific than that, they aren't trying to micro manage. However, I got interrupted and pulled off the project in the middle of that task, so I worked on it for 1 day, I had other things for 3 days, and I came back to finish the last two days.

In this case, in a gantt chart, your task can only be one "timespan" per "row" and in order for me to chart what actually happened, I need to add multiple subtasks to that task and the task ends up taking 3 rows of space.

This is rough to read and annoying to have to rearrange and insert new subtasks and rearrange subsequent tasks along the timeline.

Is there a tool out there that handles this more "ad-hoc" scheduling that I'm looking for?

Ideally what I would like is for me to be able to put together a full estimate of time for the project (say 3 months) with the ability to cascade schedule changes down when a task in the middle goes on longer than expected or gets interrupted.

I would like to have categories or color mapping so we can see which timespans are interruptions and which are tasks done and tasks to do.

Am I asking too much? Does gantt have this ability and I've not found the right vendor?

Right now my temporary solution is excel but it's a beating to have to go shift things every time I have an interruption, I feel like I spend more time explaining what happened than I do actually programming, haha

Edit: I've seen things like Monday.com and Microsoft project, but these are really heavy and too specific for my needs, I don't want a lot of context or setting up a kanban board or anything like that, I just want effectively an interactive timeline with simple "I'm doing this for x days" and not much else in terms of percent complete, details of the task, sprint integration, etc.

Think trello in complexity, just time-based and sideways 😅

I don't want to be a project manager, I don't have time for that - I just need the ability to quickly track interruptions and be able to use it as backup if upper management comes poking around

I'm currently juggling full time work and graduate school. Project management is not something that I necessarily find easy, but I need to figure it out in order to succeed this semester. Any productivity tips would be welcome. Thanks

About 15 years ago, I was impressed by a TV commercial. In a Bank of America ad about their investments in crappy neighborhoods (they didn’t phrase it that way), the spokesperson said the bank knew they’d succeeded, “when the flowerboxes begin showing up on front porches.”

Teams have the same sort of indirect indications, too, for good or ill. I’m writing an article about such non-obvious metrics that managers can use to judge whether a team is healthy.

One example is self-organizing get-togethers. It’s one thing for a manager to create team-building exercises. But when the team members arrange for such gatherings themselves — and it includes the whole team, not merely a clique — you know you have an actual team, not a bunch of employees working on the same tasks. (A negative “flower box indicator” of a project cancellation is when the company no longer refills the snack bar; but in this article I want to keep things positive.)

For managers and other leaders: What have you recognized as “flowerbox indicator”? I want to give examples that managers can use to recognize and celebrate success.

(We can have a great conversation here, but I do need to quote people by name, company, title if I use the input in the article.)

Technically two people are a team, right? :P

If it was only me I would use Org Mode, but that's not the case.

Our projects are all artistic in nature, mostly screenplay collaborations, film criticism, YouTube, podcasts, etc ^[1]. It's easy to get overly excited about this kind of stuff, but we need to follow up too. And we don't have an external demand that would incentivize us to put in the effort.

Even though we're only two people, we both have trouble sustaining long term goals, organizing schedules and information. My partner is a brilliant writer, but for him concentrating is even more of an issue than it is for me. He needs something visual. This tool must also work very well on mobile since he currently does not own a computer. It also must be graphical and easy to learn for someone that only knows Windows and MacOS.

To be more specific, I'm looking for something that allows me to track what we have done, what we're doing now and what we're going to do next. A calendar and some kind of notification system would be nice, but, as I say in the title, it must be free (I'm Brazil and our currency is worth nothing, so even the cheap is expensive for us...).

Google gives me dozens of results, reviews, etc, but it's hard to assess how good each tool is without experimenting it. And I would like to avoid learning an entire platform just to conclude it is subpar (I know this is largely unavoidable, but we can do better with a little help from our friends!).

Any suggestions? :D

^[1] Even though our projects are artistic, their execution involves many things that are not artistic at all, such as understanding, budgets, legislation, registering our works with the copywriting authority, participating in public contests, networking, etc. There are lots of menial tasks that are easy to forget.

I'd like your input for an article I'm writing.

Let’s say you’re starting a new IT project. It could be custom software; perhaps it’s a migration to cloud services; maybe it’s a shiny new IoT project.

The point is that you're here to build something great. You’re in charge of the design (or an important part of it), and making sure that the resulting system makes everybody happy.

How do you make sure that you are interviewing the right people to find out what “make them happy” looks like? What do you do to get input from the people who matter for the project’s success… without inviting so many suggestions that it’s impossible to deliver everything?

Case in point: Ten years ago I was in charge of an online tech community. The company I worked for hired custom developers to build the software platform, but the developers never talked to me. They interviewed the boss, two levels above me (who just so happened to be the person who signed the checks) even though she had never used this online community or any other. Needless to say, the community software they delivered was horrible, missing basic-to-me features.

Formally this process would be called “identifying the project stakeholders” or “master the requirements-gathering process” but that seems too corporate-speak. I’m looking for real-world examples of what works and what doesn’t, so I can write a genuinely useful article with practical guidelines.

Note that this is NOT about the questions to ask those stakeholders; that’s another discussion. Here I am writing merely (merely!) about making sure you are speaking to the people whose input you need.

My questions:
• How do you decide which people to ask for input? In what way do you find those people? How do you know when you have everyone you should?
• How do you decide whom NOT to invite? Where do you draw the line?
• Tell me about the manner in which you learned that lesson. (The hard way. Anecdotes are good.)
• If you want to be quoted (it's good for business!) tell me (via PM) how to refer to you in the article: Name, title, company name, short company description, URL.

Hey Tildes, I got a job directly supervising a small team of 4 software developers. I'm very excited at the prospect and would like to put my best foot forward. To that end, I would like to have a discussion around a few topics. Feel free to expand the scope if you believe the conversation would be beneficial. I'm sure I won't be the last person to be in this position. I've done research, read, and watched videos regarding several of these questions; however, since Tilde prioritizes high-quality discussion, I thought it would be a fun opportunity to chat with others about these topics.

• As a member of a software development team, what are things that your supervisor has done that has had the greatest (a) positive and (b) negative impact?
• Supervisors, when you joined your new team, what was your methodology for reviewing the team, projects, and processes? What was the scenarios behind your review and the outcome? What would you do differently?

I often try and work on projects and ideas, although I find it difficult to continue a project that takes longer than a day or two. I'm surely not the only person that experiences this. Does anyone know why this happens? How do you deal with and overcome this in your own life?