Answers: <p>Truth would be that should not happen in a DevOps environment
  .
  Your "project" will probably use Agile concepts, but there's nothing in DevOps telling how a project has to be run because DevOps is <em><a href="https://devopsguys.wordpress.com/2013/12/13/devops-and-the-product-centric-approach/" rel="noreferrer">product centric</a></em> (more details on the blog post and with search on this term).</p>
  
  <p>"DevOps" is about breaking silos and have a team composed of developers, architects, ops, exploitation peoples who handle a software on its lifetime, that is antagonistic with the waterfall project approach.</p>
  
  <p>To quote here Jez Humble:</p>
  
  <blockquote>
    <p>Products not projects</p>
  </blockquote>
  
  <p>So your answer would be : There's not responsibilities for a project manager on a DevOps product because the main idea behind devops is to have a team handling the product on long term and not on a planned project time only.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-08-22T18:00:13.413Z
Answers: Except maybe not go against the DevOps environment of the respective product just to get that particular project done :)
Answers: Dan Cornilescu
Answers: CC BY-SA 3.0
Answers: 2017-08-22T21:30:38.087Z
Answers: Usually if you form a project to change a devops managed product you break the engine running the product, just because you want to enforce a bunch of features in a counter productive way. The good approach should be to prioritize with the product owner the urgent features and keep the already running flow. Even a new product should not start in a project manner but should aim at building a team around the product with the business needs as a backlog IMHO
Answers: Tensibai
Answers: CC BY-SA 3.0
Answers: 2017-08-22T15:03:55.267Z
Answers: 2017-08-22T15:03:55.267Z
Answers: Tensibai
Body: <p>A project in DevOps should logically change the management mechanisms.
  What are the responsibilities of a project manager in a DevOps project ?</p>
  
  <p><strong>Note</strong>: A project DevOps of what I understand is a project that has a beginning and an end, it is a temporary effort to create a product or a unique result and that uses the concept DevOps to produce a software.</p>
  
Comments: CC BY-SA 3.0
Comments: 2017-07-02T17:09:28.050Z
Comments: That just sounds like a software project to me. Can you clarify the distinction?
Comments: Xiong Chiamiov
Comments: CC BY-SA 3.0
Comments: 2017-08-22T14:40:07.057Z
Comments: this is the link to this question at project mgmt SE but downvoted
  https://pm.stackexchange.com/questions/21883/what-are-the-responsibilities-of-a-project-manager-in-a-devops-project
Comments: Ta Mu
Comments: CC BY-SA 3.0
Comments: 2017-09-13T09:36:46.500Z
Comments: @XiongChiamiov I mean Software project in a DEVOPS context
Comments: AED
Tags: <project-management>
Title: What are the responsibilities of a project manager in a DevOps project?
UserDisplayName: AED
ThreadText: # What are the responsibilities of a project manager in a DevOps project?
  
  (Asked by: username_0 on 2017-06-21)
  
  A project in DevOps should logically change the management mechanisms.
  What are the responsibilities of a project manager in a DevOps project ?
  
  **Note**: A project DevOps of what I understand is a project that has a beginning and an end, it is a temporary effort to create a product or a unique result and that uses the concept DevOps to produce a software.
  
  **Tags:** project-management
  
  > **Comments:**
  > **username_1**: That just sounds like a software project to me. Can you clarify the distinction?  
  > **username_2**: this is the link to this question at project mgmt SE but downvoted https://pm.stackexchange.com/questions/21883/what-are-the-responsibilities-of-a-project-manager-in-a-devops-project  
  > **username_0**: @username_1 I mean Software project in a DEVOPS context  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2017-08-22. Score: 5
  
  Truth would be that should not happen in a DevOps environment
  .
  Your "project" will probably use Agile concepts, but there's nothing in DevOps telling how a project has to be run because DevOps is *[product centric](https://devopsguys.wordpress.com/2013/12/13/devops-and-the-product-centric-approach/)* (more details on the blog post and with search on this term).
  
  "DevOps" is about breaking silos and have a team composed of developers, architects, ops, exploitation peoples who handle a software on its lifetime, that is antagonistic with the waterfall project approach.
  
  To quote here Jez Humble:
  
  > Products not projects
  
  So your answer would be : There's not responsibilities for a project manager on a DevOps product because the main idea behind devops is to have a team handling the product on long term and not on a planned project time only.
  
  > **Comments:**
  > **username_4**: Except maybe not go against the DevOps environment of the respective product just to get that particular project done :)  
  > **username_3**: Usually if you form a project to change a devops managed product you break the engine running the product, just because you want to enforce a bunch of features in a counter productive way. The good approach should be to prioritize with the product owner the urgent features and keep the already running flow. Even a new product should not start in a project manner but should aim at building a team around the product with the business needs as a backlog IMHO  
  
  ---
  
  