Schedule Maintenance Plan - Request For a Good Sequence
It looks like your goal is to "chain" certain jobs: to run an integrity check, then an index optimization, then a backup.

First - it may make sense to take a backup before the check and index optimization. If something were to go horribly wrong during those steps, you could get back to the start to try to resolve things. If you take differential backups of this DB, you might want to take a final diff backup before, and a full backup after.

Second, the chaining seems reasonable in general. However, until you've run the jobs, you have no idea how long they'll take. If there's a chance that the DB check and the index optimization could take longer than an hour, I'd space things out more. Overlapping these things isn't necessarily a good idea.

If the tightest possible chaining is desirable, then move the job steps into a single job, and order them as desired. Or, as suggested by @AaronBertrand, only set and actual schedule for the first job; have the first job kick off the second as its final step, the second job kick off the third, and so forth.