authors are vetted experts in their fields 和 write on topics in which they have demonstrated experience. 我们所有的内容都经过同行评审,并由同一领域的Toptal专家验证.
It is common for a software product to transition from one development team to another during its lifetime. Different stages of the product may c所有 for a different type of development team: a consultancy to build the initial 版本, 一个独奏 自由开发人员 为了维护它,我们需要一个内部团队来扩大它的规模,或者一个专业设计师来添加一些“流行”元素。.
尽管这种情况经常发生, many non-technical founders 和 product owners find themselves unprepared 和 scrambling when the time comes to bring on the next team. 这通常会导致新团队无法快速进步, 浪费时间, 每个人都感到沮丧.
如果这听起来像是你干的, 要么现在,要么将来, 那你应该有点担心了. 幸运的是, we are going to walk through the steps you can take to prepare for this eventuality 和 make the transition as smooth as possible.
在本文中, 我将给你提供一份清单,上面的项目将帮助你为这样的变化做好准备. You will be getting to know your product on a more intimate level 和 gaining more control over 所有 the various services 和 technologies that go into making it, 什么能让你更自信、更轻松地加入一个新团队.
但如果你不替换整个团队呢? 你应该阅读这篇文章吗?
即使之前的一些团队成员仍然留在船上,他们也可能没有 所有 顺利过渡所需的答案和信息. 虽然他们可以提供连续性和 援助 在将知识从老团队转移到新团队的过程中, relying on incumbent team members is no substitute for the product owner taking charge 和 facilitating the transfer. 除了, 未能负责可能会导致新老团队成员之间的摩擦, 或者让老团队成员承担不必要的任务, forcing them to waste too much time communicating with new team members 和 resolving various issues.
仍然, 如果有团队成员留在船上, 在你的转型过程中,他们是无价的财富. 与他们协商, keep them in the loop 和 try to leverage their experience without inundating them with too many transition-related tasks. 不要指望他们做什么 所有 繁重的工作! 那是你的工作.
闲话少说,让我们开始吧!
Freelance developers are often asked to jump into an existing codebase that they’ve never seen before. 对于Toptal软件工程师来说尤其如此. Our goal is always to get up to speed as quickly as possible so we can start having a positive impact for our clients.
有办法清除, 关于项目的详细文档可以极大地加快入职过程, 并帮助开发人员避免可能阻碍前进的陷阱.
好的文档需要至少涵盖以下主题:
文档应该由具有以下经验的开发人员编写 亲身体验 设置应用程序并贡献代码库.
在任何转变发生之前, request that the previous development team facilitates the transfer of knowledge by creating a resource that touches on the topics above!
如果写作不是他们的强项, 要求他们录制一个或多个演示开发环境设置的屏幕视频, 部署, 等. 今天甚至有工具,如 流浪的 和 码头工人 哪一个允许将整个开发环境打包并分发给其他人. 在本质上, 而不是告诉别人怎么做锤子, 把锤子本身给他们.
The litmus test for how comprehensive 和 effective a project’s documentation is is how quickly a new developer can get his or her development environment setup 和 running your application.
Having great documentation does not excuse you from needing to know the basics of your own product’s technology. 作为软件产品的所有者, 尽你所能理解你的应用程序是你的责任, 即使你不是很懂技术.
以下问题很常见, 你不需要去查就能知道答案:
今天的软件开发过程利用了大量的第三方服务和工具. 无论您是否知道,您的应用程序也不例外.
在发展过程中, 你以前的团队可能代表你报名了, 甚至用他们自己的账户来获得所需的服务. Transitioning to a new team means that you must take ownership 和 be in control of every single one of the services 和 tools that your application relies on so that you can grant access to your new team without needing to go through a middleman or chase down the original developers.
The following is a list of the various external tools or services that your application might make use of:
询问即将离职的开发团队哪些是适用的. 对于任何服务 拥有 通过开发团队,要求他们将所有权转让给您. 如果不可能的话, then ask them to help you create a new account of your own 和 ensure that the application uses your account instead of theirs. 这应该只需要更改应用程序的一些配置设置.
不用说, make sure that every development contract protects your interests from day one 和 assures a smooth transition, 无论如何.
With a solid underst和ing of the ecosystem of your application 和 ownership over 所有 the various tools 和 services your application uses, 您现在可以为即将到来的团队或个人提供完全访问权限.
Most services will 所有ow you to add a collaborator to your account 和 grant them a particular level of access. 在这里保守一点没关系. 许多创业者, 尤其是个人创业者, prefer to give their developers full administrator access to their services 和 have them h和le everything. 这有一个负面的副作用,就是把你排除在圈子之外, 我们已经学过了, 会让未来的转型变得更加困难吗.
应该给开发人员完全的管理员权限吗? 这是你的决定,大多数人对这种方法没有问题. 然而, you always need to plan ahead 和 make sure your decision does not negatively affect a new development team. 如果在项目的早期阶段没有做到这一点,可能会在未来产生令人烦恼的后果.
既然你已经万事俱备了, 你需要管理好从一个团队到下一个团队的交接. 这里有一些基本的技巧,可以帮助你应对新员工和即将离职的员工.
生活中的任何转变都是可怕的, 带来的不确定性是否会成功, 对未知的恐惧, 等等....... 过渡到一个新的开发团队也是一样, 但是你可以而且应该采取措施让它变得更容易. 在大多数情况下,它只需要一点长期的计划.
对软件产品有更深入的技术和非技术理解, 开发过程, 所有 the things that went into the process will help make any transition from one team to the next as seamless 和 painless as possible.
最重要的是,你的新团队会尊重并感谢你的出色表现! 你可能会节省他们的时间和精力,这也意味着你会省钱. 此外,新团队越早意识到坚持高专业水准越好. 一旦他们接管了项目,他们很可能会继续执行这些实践, 确保下一个过渡顺利进行.
So let’s review the key points that should precede any transfer of ownership of your software product:
圣拉斐尔,加州,美国
2014年12月6日成为会员
世界级的文章,每周发一次.
世界级的文章,每周发一次.