𝔖 Scriptorium
✦   LIBER   ✦

πŸ“

Software Project Survival Guide

✍ Scribed by Steve McConnell


Publisher
Microsoft Press
Year
1998
Tongue
English
Leaves
298
Series
Pro -- Best Practices
Edition
1
Category
Library

⬇  Acquire This Volume

No coin nor oath required. For personal study only.

✦ Synopsis


Equip yourself with SOFTWARE PROJECT SURVIVAL GUIDE. It's for everyone with a stake in the outcome of a development project - and especially for those without formal software project management training. That includes top managers, executives, clients, investors, end-user representatives, project managers, and technical leads.Here you'll find guidance from the acclaimed author of the classics CODE COMPLETE and RAPID DEVELOPMENT. Steve McConnell draws on solid research and a career's worth of hard-won experience to map the surest path to your goal - what he calls "one specific approach to software development that works pretty well most of the time for most projects. Nineteen chapters in four sections cover the concepts and strategies you need for mastering the development process, including planning, design, management, quality assurance, testing, and archiving. For newcomers and seasoned project managers alike, SOFTWARE PROJECT SURVIVAL GUIDE draws on a vast store of techniques to create an elegantly simplified and reliable framework for project management success.So don't worry about wandering among complex sets of project management techniques that require years to sort out and master. SOFTWARE PROJECT SURVIVAL GUIDE goes straight to the heart of the matter to help your projects succeed. And that makes it a required addition to every professional's bookshelf.

✦ Subjects


Π‘ΠΈΠ±Π»ΠΈΠΎΡ‚Π΅ΠΊΠ°;ΠšΠΎΠΌΠΏΡŒΡŽΡ‚Π΅Ρ€Π½Π°Ρ Π»ΠΈΡ‚Π΅Ρ€Π°Ρ‚ΡƒΡ€Π°;Microsoft Office;Microsoft Project;


πŸ“œ SIMILAR VOLUMES


Software Project Survival Guide (Pro --
✍ Steve McConnell πŸ“‚ Library πŸ“… 1997 πŸ› Microsoft Press 🌐 English

Equip yourself with SOFTWARE PROJECT SURVIVAL GUIDE. It's for everyone with a stake in the outcome of a development project--and especially for those without formal software project management training. That includes top managers, executives, clients, investors, end-user representatives, project man

Death March: The Complete Software Devel
✍ Edward Yourdon πŸ“‚ Library πŸ“… 1997 πŸ› Prentice Hall PTR 🌐 Russian

I read the first edition years ago -- after the fact. I had just survived [barely] my first death march project, and I thought it offered some good, retrospective advice. It helped me recognize at the very least, a death march project when I see one. Reading the second edition reminded me of wha

Death March: The Complete Software Devel
✍ Edward Yourdon πŸ“‚ Library πŸ“… 2003 πŸ› Financial Times Prentice Hall 🌐 English

In the course of a career, practically every software developer will encounter several projects with outrageous staffing, schedule, budget or feature constraints--projects that seem "doomed to fail." Now, bestselling author Edward Yourdon brings his unique technology and management insight into thes

Software Design: A Comprehensive Guide t
✍ Murali Chemuturi (Author) πŸ“‚ Library πŸ“… 2018 πŸ› Chapman and Hall/CRC

<p>This book is perhaps the first attempt to give full treatment to the topic of Software Design. It will facilitate the academia as well as the industry. This book covers all the topics of software design including the ancillary ones.</p>

Software Project Secrets: Why Software P
✍ George Stepanek πŸ“‚ Library πŸ“… 2005 πŸ› Apress 🌐 English

Software Project Secrets: Why Software Projects Fail offers a new path to success in the software industry. This book reaches out to managers, developers, and customers who use industry-standard methodologies, but whose projects still struggle to succeed.Author George Stepanek analyzes the project m

Software Project Secrets Why Software P
✍ George Stepanek πŸ“‚ Library πŸ“… 2012 πŸ› Apress 🌐 English

Software Project Secrets: Why Software Projects Fail offers a new path to success in the software industry. This book reaches out to managers, developers, and customers who use industry-standard methodologies, but whose projects still struggle to succeed.