4 ms·

Thanks for your reply knight. Treating matters from this perspective is always positive and I take it as good feedback. First, there are things that I agree wi

Thanks for your reply knight. Treating matters from this perspective is always positive and I take it as good feedback. First, there are things that I agree with and others that I don't agree with. Work organization methodologies are a first approach to real problems but they are not the final solution. The metrics that I present are nothing more than an approach from which to face the problem and have data to make better decisions. 1. Activity Days not only shows the modified lines or the affected units. It generates a report of all the activity in that sprint if you click on the blue button and it shows you all the tasks performed in that sprint with an associated impact value. 2. Impact is not associated with risk at any time, it is associated with an algorithm that determines among other things the level of dependencies affected, message of the commit or lines affected by a commit. 3. Code churn is nothing more than an approximation to know when there has been more flow of changes in a specific repository. 4. The flow of all work is something we are working on in scope.ink for the next releases. We will integrate exactly what you have written: how the entire flow of a task works from the moment it opens until it closes and how the work is connected between the software engineers. In any case, software factories help them know the average time of tasks to make better cost projections. Thank you for your contribution knight and we keep in touch!

knightofmars 7y ago
I see I was responding to someone from Scope. :D I realize looking at your responses my question is the following. What is a Project Manager expected to do with these metrics? A singular example, what's the point of knowing Impact? What action am I supposed to take if I know the Impact? My immediate inclination is to use it to determine risk.
- alesdonoso 7y ago
  Haha yes, you are :) What you should expect when viewing these metrics as Project Manager is to know the workflow of your engineers, not the risk associated with each of the tasks. In relation to your question, the impact determines the level of involvement of each PR within the repository. Not necessarily greater impact implies greater risk, but a better quality of the task in short. In the end, what we need is data to make decisions based on something palpable.
  - knightofmars 7y ago
    I appreciate your taking the time to respond to my inquiries. I'm genuinely curious how one is supposed to use the information your application provides. I agree with your statement, "In the end, what we need is data to make decisions based on something palpable." But the part I'm not convinced about is that the data being provided is the right data to use in making a decision. Does your response, "Not necessarily greater impact implies greater risk, but a better quality of the task in short." imply that there is a relationship between Impact and quality? I read through a number of your other blog posts and still don't have a clear understanding of what it is that a project manager (or others) should be doing with all of this information. Can you give me a use case example of how I (as a project manager) would use an Impact visualization in my decision making process? Thank you again for taking the time to answer my questions.
    - alesdonoso 7y ago
      Hi there again knight! As you can imagine, we are a Startup actually consolidating our product. We are in Seed stage so every feedback we receive (like yours) makes us very happy and prouds and helps us tons! So thank you again for taking your time to ask me questions! Since we are validating some of our visualizations and insights, not all people will find the value, while others do. In our case, some of our customers are using the "Impact" visualization to gamify some way the code process with the engineers so they are more motivated and have increased the quality of their processes overall. You are probably right by saying that our provided data could be not the right data to make decisions. It will depend on you and the value you find in that information we provide. As I told you, we are validating and you are free to talk to me and write me your pains if you have them! Thanks again knight!
      - knightofmars 7y ago
        > It will depend on you and the value you find in that information we provide. First, I understand that Scope is a startup and working a lot of this out so please take my response as constructive feedback. I suspect that you're missing my point. If you're selling this product to me then you need to sell me on how it's going to make my life as project manager, CTO, or engineer better. Saying that it's data for decision making is a start. But my perception on our conversation is that every time I've tried to pin down a concrete answer on "What decisions does this help me make?" you've responded along the lines of "This is the data and this is how it's created." That's not telling me what immediate actionable steps this data will allow me to make and to make better. Subsequently, how those actionable steps will lead to more productivity and better quality. Hopefully that gets across what I was attempting to understand. Best of luck to you and Scope!

knightofmars 7y ago

I see I was responding to someone from Scope. :D I realize looking at your responses my question is the following. What is a Project Manager expected to do with these metrics? A singular example, what's the point of knowing Impact? What action am I supposed to take if I know the Impact? My immediate inclination is to use it to determine risk.

alesdonoso 7y ago
Haha yes, you are :) What you should expect when viewing these metrics as Project Manager is to know the workflow of your engineers, not the risk associated with each of the tasks. In relation to your question, the impact determines the level of involvement of each PR within the repository. Not necessarily greater impact implies greater risk, but a better quality of the task in short. In the end, what we need is data to make decisions based on something palpable.
- knightofmars 7y ago
  I appreciate your taking the time to respond to my inquiries. I'm genuinely curious how one is supposed to use the information your application provides. I agree with your statement, "In the end, what we need is data to make decisions based on something palpable." But the part I'm not convinced about is that the data being provided is the right data to use in making a decision. Does your response, "Not necessarily greater impact implies greater risk, but a better quality of the task in short." imply that there is a relationship between Impact and quality? I read through a number of your other blog posts and still don't have a clear understanding of what it is that a project manager (or others) should be doing with all of this information. Can you give me a use case example of how I (as a project manager) would use an Impact visualization in my decision making process? Thank you again for taking the time to answer my questions.
  - alesdonoso 7y ago
    Hi there again knight! As you can imagine, we are a Startup actually consolidating our product. We are in Seed stage so every feedback we receive (like yours) makes us very happy and prouds and helps us tons! So thank you again for taking your time to ask me questions! Since we are validating some of our visualizations and insights, not all people will find the value, while others do. In our case, some of our customers are using the "Impact" visualization to gamify some way the code process with the engineers so they are more motivated and have increased the quality of their processes overall. You are probably right by saying that our provided data could be not the right data to make decisions. It will depend on you and the value you find in that information we provide. As I told you, we are validating and you are free to talk to me and write me your pains if you have them! Thanks again knight!
    - knightofmars 7y ago
      > It will depend on you and the value you find in that information we provide. First, I understand that Scope is a startup and working a lot of this out so please take my response as constructive feedback. I suspect that you're missing my point. If you're selling this product to me then you need to sell me on how it's going to make my life as project manager, CTO, or engineer better. Saying that it's data for decision making is a start. But my perception on our conversation is that every time I've tried to pin down a concrete answer on "What decisions does this help me make?" you've responded along the lines of "This is the data and this is how it's created." That's not telling me what immediate actionable steps this data will allow me to make and to make better. Subsequently, how those actionable steps will lead to more productivity and better quality. Hopefully that gets across what I was attempting to understand. Best of luck to you and Scope!