I don't know if I'd say that... For one, unless you are actually going to build vdevs and stuff any kernel you build is going to be a microkernel. In my experience, however, I would not say that message passing makes your life that much easier. In addition, it's probably a good idea to write an ELF compatible OS if you want a prompt. Writing a shell isn't that hard, but I wouldn't want to replicate the basic userland tools if I can just statically compile a busybox library. You should also plan to implement some sort of ramdisk if you want a useable environment (or virtual devs with drivers, but that would probably be harder). Actually, I'd recommend just building off QEMU, since that'll give you rudimentary device framework and keep you from having to debug on physical hardware (like I do).
I don't think I could have ever gotten my little OS to the self hosting stage without that.
It still took more time than I care to remember though :)
A virtual machine is a great tool as well, especially if it gives you access to the cpu contents of the running VM.
That will save you days if not weeks trying to find out why your switch from 'real' to 'protected' mode during the boot didn't work...
Kitten[1] is the LWK which I work with, although my focus is on the Palacios VMM. It's quite a simple OS that is by no means out of a good programmer's reach.
It's absolutely doable.
If you want to make your life easier go for a micro kernel with message passing. That will partition the tasks to the point where a single determined person can go all the way from MBR to prompt.
Runner up in the experience category: make a game from scratch that has multiple threads of execution, but use a single threaded process. That's almost the same experience but completely in userland, which should make your debugging life a lot easier.
But if you want to learn all there is to know about memory management, interrupts and interfacing with hardware as well as process scheduling build a kernel.
Older dr. Dobbs issues contain tons of useful information.
Here is some food for thought: http://ww.com/task.cc.html and http://ww.com/task.h.html
Other sources of inspiration: the early minix kernels and the early work on what is now known as FreeBSD by Bill and Lynne Jolitz (also described in dr Dobbs iirc)