Postmortem 6

--Originally published at SW Quality and Testing

 

This week I was not a very useful teammate. I (along with one of my teammates) was really busy doing a project for another class. I will have to make up for this week’s undone work. Luckily next week seems like it will not be an intense one and I am going to be really prductive but who knows.

On another note, I feel a sense of tiredness among my teammates. I hope it is just a temporary post-partial effect and that it will not affect the development of the project.

Premortem 6

--Originally published at SW Quality and Testing

For this week I want to do what I could not do last week, which is deploying Alex’s part on the cloud and testing connection with the other parts of the system. I am not an expert using Docker nor Kubernetes so that will take me a lot, I think.

Luckily, this week we have Alex back so I can ask him about all the parts of his code that I do not understand.

 

Postmortem 5

--Originally published at SW Quality and Testing

This was our second sprint and we did what I estimated we were going to do in my premortem analysis. Mike and I deployed the project on the cloud and Martell could perfectly connect with the data base. I was asked to do something extra. I needed to deploy Alex’s part on the cloud as well but I could not because I did not understood well his code so we decided to do that next week. I think that we did a good job.
Art by lasi410, on Flickr
Art” (CC BY-NC-ND 2.0) by lasi410

 

Postmortem 4

--Originally published at SW Quality and Testing

This week we were all busy with exams and projects so I did not do much of what I estimated I could do. Mike and I just finished the logging service for the system but we did not deploy the project on cloud as it was planned. Also we did not joined our individual parts, all due to lack of time. We are going to need to reschedule that for the next week and try to stick to the schedule so we do not get behind.

Premortem 4

--Originally published at SW Quality and Testing

This week I am going to be working with Mike, today we made a logging service for the application and it worked.  I learned a lot and I want to learn more about Go. We are going to deploy the proyect so it can be reached by the other two parts, The raspberry/sensors and the web application. And we are going to test connectivity among every part.

 

Postmortem 3

--Originally published at SW Quality and Testing

 

This week I worked little on the project. I just did a Kubernetes and Go courses I found in Lynda. So far I like both, is something new to me. Mike gave me some Go lessons and he is being a good and patient teacher.

When the project started and I did not got the sensors part I was disappointed but now I am excited about learning something new and helping someone else learning something new too. And that was all my week now I want to implement the knowledge I have acquired.

 

Postmortem 2

--Originally published at SW Quality and Testing

So far, everything in the project is not going bad,  this week my premortem analysis was less accurate than my first one. I tried to do what I wrote, but in order to do it I need one of my teammates to finish something that is not done yet so I did other things.


I did the database scheme for the project and I also wrote the DDL, which was really easy because what we need is simple. Mike told me that he needs help with his part, so I am now  learning Go and Kubernetes (It is not that difficult but is completely new to me).


Now that I know that I suck at estimating, I think is up to me to not get behind and end up doing everything in the last moment. I need to work on that.