#martim monday

[undeadboyfriendsupportgroup]

Martim monday again, mis amores.

[martimweek]

[ID: A graphic announcing the prompts for martim week. The background is divided in three colours: rich mustard yellow, beige, and coral pink, on which stand two stickers: on the left a yellow cassette tape labeled with the handwritten word “epiphany” and on the right a yellow and orange coupe of milkshake with two stripped straws and a red cherry on top.  The text positioned at the top of the image reads: martim week, february 8th - february 14th. Below it are seven symmetrically placed rectangle text boxes, one for each day of the week, containing word prompts. Each box contains three prompts for that day, and they are as follows: on Monday: stakeout/follow up – boundaries – first time. On Tuesday: alternative meeting – jealousy – size kink/difference. On Wednesday : identity – club/pub/bar – bondage. On Thursday: triggers – og archival staff – body. On Friday: sleepover – sneaking around – slow down. On Saturday: alternative universe – dressed up/down – praise/degradation. On Sunday: family – epiphany – competitive. At the very bottom of the picture are listed the socials of the events, @martimweek on twitter and @martimweek on tumblr. /end ID]

Here are the prompts! Rules and FAQ to follow soon. 

We accept all kinds of fanworks, both sfw and not sfw. The tag we’ll follow for this event is #martimweek2021, so please post all of your responses with it, so we can reblog and enjoy them :)

Please direct all and any questions about the event to this blog.

[voiceless-terror]

Martim + tea as a love language for the three sentence prompts!

It’s Monday morning and Tim’s finally crawling back to work- whatever illness that struck him in Malaysia is tempered by the halls of the institute, much to his chagrin. He wishes he could go back in time and tear up his contract, cut ties with the lot of them and feel no remorse.

But he can only sit at his desk, take the warm mug of tea made by familiar hands and curse the way his mind automatically supplies ‘home.’

[newtownpentacle]

vestiges of

How many times a week can you say it’s Monday, huh?

– photo by Mitch Waxman

As described last week,my pal Val drove her Valmobile – with myself and a libertarian named Scott within it – out to a photogenic spot on the Kill Van Kull waterway which forms a busy martime shipping channel as well as the border betwixt… Staten Island… and Bayonne, New Jersey. After visiting this spot – known to my…

[ftmthor]

Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler

Chris Paul is having a hard time finding a way to move to his preferred place Miami Heats. The 34-year-old point guard recently arrived at Oklahoma City Thunder but instantly wants to move on.

Chris Paul wants an instant trade

The reason being that Oklahoma City is in for a long rebuilding process and the ageing point guard is least interested. Chris Paul was recently traded to the Thunders in place of Paul George from Rockets. Miami Heat is his preferred place as per reports.

Houston hoped to find third-team destination preferable to Chris Paul, but ultimately leaves it OKC to execute next step once Presti confers w/ CP3 agent Leon Rose. Miami remains possibility for Paul (3 years, $124M) — and OKC obviously has picks to incentivize deal, if needed.

— Adrian Wojnarowski (@wojespn) July 12, 2019

Brian Windhorst from ESPN recently commented about Paul’s preferred place. He thinks that Chris Paul would want to land up in Heat and team up with the recently acquired Jimmy Butler. But there’s more to it. The deal isn’t as forward as it seems. Windhorst talked about it on Sports Center on Monday night.

“When you talk about him potentially going to the Miami Heat, which is his preference, one thing I’ve been told in the talks; the fact that the Thunder hold the two of the Heat’s first-round picks in the talks; the fact that the Thunder hold the two of the Heat’s first-round picks in the future — unprotected 2021, protected 2023 — makes this a difficult conversation because the Heat want those picks back.”

The Russ-Paul trade has only one winner: the Rockets. They got rid of an undersized, old, point guard who doesn’t shoot that well and that is about to make $40 million/year in the coming years. His contract is horrible and I can’t imagine him playing in OKC that long. #ChrisPaul pic.twitter.com/2KOtRLKP12

— Martim Silva (@MartimTheGreat) July 12, 2019

Now he does think that Oklahoma City Thunder is ready to concede one of their picks but again are looking to seal one in future.

Problem between Paul George and Miami Heat

The Thunder agree to trade #RusselWestbrook to the Rockets for #ChrisPaul 😱😱 pic.twitter.com/p8WtSR2GC0

— Kollege Kidd (@KollegeKidd) July 12, 2019

Oklahoma City Thunder now has traded off both Paul George and Westbrook from their roster. They now have as many as 16 future first-round picks to choose. That’s a huge number for rebuilding a franchise and Thunder might end up picking a complete lineup of All-Stars by 2026. But some say that’s too big a number to strategize.

Heat seems to be the only viable option for Paul. Image : USATodaySports

Thunder nevertheless don’t want to give away any. Now what Miami Heat are asking to take up Chris Paul’s $124m is a better deal.

Oklahoma City Thunder are better positioned to rebuild than perhaps any team in league history from nba

Another issue with Chris Paul is that at his age, not many franchises are vying for him. Miami Heat is the only realistic option for now. Thunder would also like to increase their salary cap but Miami Heat has hardly any room after Butler signing.

So all in all, something has to give in to complete this one. This might take time for all permutations to be set right but expect Paul to reach Miami in some time.

The post Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler appeared first on Hiptoro.

source https://www.hiptoro.com/p/chris-paul-discontent-with-oklahoma-city-thunders-looks-to-team-up-with-butler/ source https://emmaleebruce.tumblr.com/post/186344630005

[hildaagular]

Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler

Chris Paul is having a hard time finding a way to move to his preferred place Miami Heats. The 34-year-old point guard recently arrived at Oklahoma City Thunder but instantly wants to move on.

Chris Paul wants an instant trade

The reason being that Oklahoma City is in for a long rebuilding process and the ageing point guard is least interested. Chris Paul was recently traded to the Thunders in place of Paul George from Rockets. Miami Heat is his preferred place as per reports.

Houston hoped to find third-team destination preferable to Chris Paul, but ultimately leaves it OKC to execute next step once Presti confers w/ CP3 agent Leon Rose. Miami remains possibility for Paul (3 years, $124M) — and OKC obviously has picks to incentivize deal, if needed.

— Adrian Wojnarowski (@wojespn) July 12, 2019

Brian Windhorst from ESPN recently commented about Paul’s preferred place. He thinks that Chris Paul would want to land up in Heat and team up with the recently acquired Jimmy Butler. But there’s more to it. The deal isn’t as forward as it seems. Windhorst talked about it on Sports Center on Monday night.

“When you talk about him potentially going to the Miami Heat, which is his preference, one thing I’ve been told in the talks; the fact that the Thunder hold the two of the Heat’s first-round picks in the talks; the fact that the Thunder hold the two of the Heat’s first-round picks in the future — unprotected 2021, protected 2023 — makes this a difficult conversation because the Heat want those picks back.”

The Russ-Paul trade has only one winner: the Rockets. They got rid of an undersized, old, point guard who doesn’t shoot that well and that is about to make $40 million/year in the coming years. His contract is horrible and I can’t imagine him playing in OKC that long. #ChrisPaul pic.twitter.com/2KOtRLKP12

— Martim Silva (@MartimTheGreat) July 12, 2019

Now he does think that Oklahoma City Thunder is ready to concede one of their picks but again are looking to seal one in future.

Problem between Paul George and Miami Heat

The Thunder agree to trade #RusselWestbrook to the Rockets for #ChrisPaul 😱😱 pic.twitter.com/p8WtSR2GC0

— Kollege Kidd (@KollegeKidd) July 12, 2019

Oklahoma City Thunder now has traded off both Paul George and Westbrook from their roster. They now have as many as 16 future first-round picks to choose. That’s a huge number for rebuilding a franchise and Thunder might end up picking a complete lineup of All-Stars by 2026. But some say that’s too big a number to strategize.

Heat seems to be the only viable option for Paul. Image : USATodaySports

Thunder nevertheless don’t want to give away any. Now what Miami Heat are asking to take up Chris Paul’s $124m is a better deal.

Oklahoma City Thunder are better positioned to rebuild than perhaps any team in league history from nba

Another issue with Chris Paul is that at his age, not many franchises are vying for him. Miami Heat is the only realistic option for now. Thunder would also like to increase their salary cap but Miami Heat has hardly any room after Butler signing.

So all in all, something has to give in to complete this one. This might take time for all permutations to be set right but expect Paul to reach Miami in some time.

The post Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler appeared first on Hiptoro.

Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler published first on http://www.hiptoro.com/ Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler posted first on http://www.hiptoro.com/

[claytoncoughlan]

Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler

Chris Paul is having a hard time finding a way to move to his preferred place Miami Heats. The 34-year-old point guard recently arrived at Oklahoma City Thunder but instantly wants to move on.

Chris Paul wants an instant trade

The reason being that Oklahoma City is in for a long rebuilding process and the ageing point guard is least interested. Chris Paul was recently traded to the Thunders in place of Paul George from Rockets. Miami Heat is his preferred place as per reports.

Houston hoped to find third-team destination preferable to Chris Paul, but ultimately leaves it OKC to execute next step once Presti confers w/ CP3 agent Leon Rose. Miami remains possibility for Paul (3 years, $124M) — and OKC obviously has picks to incentivize deal, if needed.

— Adrian Wojnarowski (@wojespn) July 12, 2019

Brian Windhorst from ESPN recently commented about Paul’s preferred place. He thinks that Chris Paul would want to land up in Heat and team up with the recently acquired Jimmy Butler. But there’s more to it. The deal isn’t as forward as it seems. Windhorst talked about it on Sports Center on Monday night.

“When you talk about him potentially going to the Miami Heat, which is his preference, one thing I’ve been told in the talks; the fact that the Thunder hold the two of the Heat’s first-round picks in the talks; the fact that the Thunder hold the two of the Heat’s first-round picks in the future — unprotected 2021, protected 2023 — makes this a difficult conversation because the Heat want those picks back.”

The Russ-Paul trade has only one winner: the Rockets. They got rid of an undersized, old, point guard who doesn’t shoot that well and that is about to make $40 million/year in the coming years. His contract is horrible and I can’t imagine him playing in OKC that long. #ChrisPaul pic.twitter.com/2KOtRLKP12

— Martim Silva (@MartimTheGreat) July 12, 2019

Now he does think that Oklahoma City Thunder is ready to concede one of their picks but again are looking to seal one in future.

Problem between Paul George and Miami Heat

The Thunder agree to trade #RusselWestbrook to the Rockets for #ChrisPaul 😱😱 pic.twitter.com/p8WtSR2GC0

— Kollege Kidd (@KollegeKidd) July 12, 2019

Oklahoma City Thunder now has traded off both Paul George and Westbrook from their roster. They now have as many as 16 future first-round picks to choose. That’s a huge number for rebuilding a franchise and Thunder might end up picking a complete lineup of All-Stars by 2026. But some say that’s too big a number to strategize.

Heat seems to be the only viable option for Paul. Image : USATodaySports

Thunder nevertheless don’t want to give away any. Now what Miami Heat are asking to take up Chris Paul’s $124m is a better deal.

Oklahoma City Thunder are better positioned to rebuild than perhaps any team in league history from nba

Another issue with Chris Paul is that at his age, not many franchises are vying for him. Miami Heat is the only realistic option for now. Thunder would also like to increase their salary cap but Miami Heat has hardly any room after Butler signing.

So all in all, something has to give in to complete this one. This might take time for all permutations to be set right but expect Paul to reach Miami in some time.

The post Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler appeared first on Hiptoro.

Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler published first on http://www.hiptoro.com/ Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler published first on http://www.hiptoro.com/

[anawiliams]

Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler

Chris Paul is having a hard time finding a way to move to his preferred place Miami Heats. The 34-year-old point guard recently arrived at Oklahoma City Thunder but instantly wants to move on.

Chris Paul wants an instant trade

The reason being that Oklahoma City is in for a long rebuilding process and the ageing point guard is least interested. Chris Paul was recently traded to the Thunders in place of Paul George from Rockets. Miami Heat is his preferred place as per reports.

Houston hoped to find third-team destination preferable to Chris Paul, but ultimately leaves it OKC to execute next step once Presti confers w/ CP3 agent Leon Rose. Miami remains possibility for Paul (3 years, $124M) — and OKC obviously has picks to incentivize deal, if needed.

— Adrian Wojnarowski (@wojespn) July 12, 2019

Brian Windhorst from ESPN recently commented about Paul’s preferred place. He thinks that Chris Paul would want to land up in Heat and team up with the recently acquired Jimmy Butler. But there’s more to it. The deal isn’t as forward as it seems. Windhorst talked about it on Sports Center on Monday night.

“When you talk about him potentially going to the Miami Heat, which is his preference, one thing I’ve been told in the talks; the fact that the Thunder hold the two of the Heat’s first-round picks in the talks; the fact that the Thunder hold the two of the Heat’s first-round picks in the future — unprotected 2021, protected 2023 — makes this a difficult conversation because the Heat want those picks back.”

The Russ-Paul trade has only one winner: the Rockets. They got rid of an undersized, old, point guard who doesn’t shoot that well and that is about to make $40 million/year in the coming years. His contract is horrible and I can’t imagine him playing in OKC that long. #ChrisPaul pic.twitter.com/2KOtRLKP12

— Martim Silva (@MartimTheGreat) July 12, 2019

Now he does think that Oklahoma City Thunder is ready to concede one of their picks but again are looking to seal one in future.

Problem between Paul George and Miami Heat

The Thunder agree to trade #RusselWestbrook to the Rockets for #ChrisPaul 😱😱 pic.twitter.com/p8WtSR2GC0

— Kollege Kidd (@KollegeKidd) July 12, 2019

Oklahoma City Thunder now has traded off both Paul George and Westbrook from their roster. They now have as many as 16 future first-round picks to choose. That’s a huge number for rebuilding a franchise and Thunder might end up picking a complete lineup of All-Stars by 2026. But some say that’s too big a number to strategize.

Heat seems to be the only viable option for Paul. Image : USATodaySports

Thunder nevertheless don’t want to give away any. Now what Miami Heat are asking to take up Chris Paul’s $124m is a better deal.

Oklahoma City Thunder are better positioned to rebuild than perhaps any team in league history from nba

Another issue with Chris Paul is that at his age, not many franchises are vying for him. Miami Heat is the only realistic option for now. Thunder would also like to increase their salary cap but Miami Heat has hardly any room after Butler signing.

So all in all, something has to give in to complete this one. This might take time for all permutations to be set right but expect Paul to reach Miami in some time.

The post Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler appeared first on Hiptoro.

Chris Paul discontent with Oklahoma City Thunders, looks to team up with Butler published first on http://www.hiptoro.com/

[sakimoonoo]

The MarTIM Postmortem

●     What went wrong?

  Communication

           Communication was one of the bigger struggles we encountered though we always would meet at least once a week, we were unable to use asynchronous communication methods effectively and this caused confusion and slowed production as we would be out of communication for longer periods of time that was intended.

   Lack of Vision Coherence

A lack of a cohesive vision caused confusion between the team and in the end led us a bit astray from the what the original products game play and mechanic were supposed to consist of. Some of the design team and art team also suffered from this and art assets where made in a way that initially caused the design team more restrictions that was intended though we managed to get on the same page in the end.

   Resource Management

           We suffered a lot from SourceTree in the beginning. When we tried to upload our individual work to the cloud,those changes conflicted with each other. After our dev team took charge of uploading, things became more organized.

 ●     What went right?

  Jamming

As a team, we decided to have a jam session on Mondays before submissions were due.  The result was a decisive increase in productivity and team cohesion.  The value of working in the same location was not lost on us.  The benefits of synchronous communication and being able to go back and forth on topics where we could look each other’s shoulder allowed us to get most of our systems to a presentable state with a more unified vision.

  Solid Level

Originally, we had wanted to do multiple small levels, but as a team, we decided to go another route. We put aside a solid day and sat together in a meeting room in order to reevaluate the decision, and worked together to instead create one fully functional level for our game. This level is longer, and more complete than the original levels we had thought about building first, and than the two levels that we had at the start of week 2. This was a very well done collaborative decision made by the entire team that lead to the profit of our build.

Implemented Feedback

We received a lot of feedback both externally and internally during our development of MarTIM.  With the great opportunity to present at the Student Game Expo we were able to get a playable build into the hands of players and collect valuable feedback. Reception of our game in its rough, unfinished state was far better than expected and gave us clarity on what aspects were fun and what aspects needed more focus. The rocket fist was an instant hit and an unintended bug that affected traversal was an unlikely source of praise. The feedback we received in class was equally valuable and led to us bringing back a planned feature we had scrapped earlier on in the project’s development: oxygen.

   ●     Conclusion

Overall the time that we put into this game has provided many insights to what it will take to properly handle making a game. From the issues we had with communication we were able to address these issues by implementing a Jam session on Monday’s before turn ins. This way any miscommunications or misunderstandings could be taken care of and squared away before turn-in. We also suffered from the lack of vision cohesion. It became apparent that the separate teams had different needs that weren’t apparent to the other teams and this caused issues through development. Yet, again thanks to the jam sessions and weekly meetings we could re focus and properly address the needs of the teams and individual members. Resource Management was also an issue since many members had little experience with SourceTree. Thankfully over the month we collectively became more comfortable with the SourceTree system. The great source that was feedback also became an important piece of the development cycle. Continued feedback throughout development, helped add many features and in the end improved our final product. We learned much from this game and we hope to take the lessons and experience we gathered to our future products.

[timsmithmastery-blog]

Team PostMortem for “The MarTIM”

The MarTIM Postmortem

What went wrong?

Communication

Communication was one of the bigger struggles we encountered though we always would meet at least once a week, we were unable to use asynchronous communication methods effectively and this caused confusion and slowed production as we would be out of communication for long periods of time that was intended.

Lack of Vision Coherence

A lack of a cohesive vision caused confusion between the team and in the end, led us a bit astray from the what the original products gameplay and mechanic were supposed to consist of. Some of the design team and art team also suffered from this and art assets were made in a way that initially caused the design team more restrictions that was intended though we managed to get on the same page in the end.

Resource Management

We suffered a lot from SourceTree in the beginning. When we tried to upload our individual work to the cloud, those changes conflicted with each other. After our dev team took charge of uploading, things became more organized.

What went right?

Jamming

As a team, we decided to have a jam session on Mondays before submissions were due.  The result was a decisive increase in productivity and team cohesion.  The value of working in the same location was not lost on us.  The benefits of synchronous communication and being able to go back and forth on topics where we could look each other’s shoulder allowed us to get most of our systems to a presentable state with a more unified vision.

Solid Level

Originally, we had wanted to do multiple small levels, but as a team, we decided to go another route. We put aside a solid day and sat together in a meeting room in order to reevaluate the decision, and worked together to instead create one fully functional level for our game. This level is longer and more complete than the original levels we had thought about building first, and than the two levels that we had at the start of week 2. This was a very well done collaborative decision made by the entire team that leads to the profit of our build.

Implemented Feedback

We received a lot of feedback both externally and internally during our development of MarTIM.  With the great opportunity to present at the Student Game Expo we were able to get a playable build into the hands of players and collect valuable feedback. Reception of our game in its rough, unfinished state was far better than expected and gave us clarity on what aspects were fun and what aspects needed more focus. The rocket fist was an instant hit and an unintended bug that affected traversal was an unlikely source of praise. The feedback we received in class was equally valuable and led to us bringing back a planned feature we had scrapped earlier on in the project’s development: oxygen.

Conclusion

Overall the time that we put into this game has provided many insights to what it will take to properly handle making a game. From the issues we had with communication we were able to address these issues by implementing a Jam session on Monday’s before turn ins. This way any miscommunications or misunderstandings could be taken care of and squared away before turn-in. We also suffered from the lack of vision cohesion. It became apparent that the separate teams had different needs that weren’t apparent to the other teams and this caused issues through development. Yet, again thanks to the jam sessions and weekly meetings we could refocus and properly address the needs of the teams and individual members. Resource Management was also an issue since many members had little experience with SourceTree. Thankfully over the month we collectively became more comfortable with the SourceTree system. The great source that was feedback also became an important piece of the development cycle. Continued feedback throughout development, helped add many features and in the end improved our final product. We learned much from this game and we hope to take the lessons and experience we gathered to our future products.

[undeadboyfriendsupportgroup]

What if...hear me out...MARTIM MONDAYS ANYONE????????

[martimweek]

RULES & FAQ

What kind of works do you accept for the week?  Anything goes! Fic, art, cosplay, anything audio or visual that has to do with martim and one of the prompts for the day is very welcome. That said, we won’t, under any circumstances, accept entries which depict rape, any type of noncon or dubcon, unhealthy relationship dynamics, incest, pedophilia, etc. This is non-negotiable. Any work promoting racist, transphobic, ableist, etc. ideas won't be accepted. Depicting difficult themes is still alright, although we do ask for it to be appropriately tagged on AO3 (trigger warnings, possible disturbing or heavy themes, e.g. dealing with trauma or such).

How do I enter my submission, then? Just post it on Twitter, Tumblr or AO3 (details of how the AO3 submissions are going to work will come later). Tag us (@/martimweek on both Tumblr and Twitter) and we will reblog your work! We will also track #martimweek2021, so remember to add it in the tags. 

Prompts have different colours. What does that mean?  That’s Lew’s (@twinliches) creative choice. Obviously, some prompts are nsfw, plain and simple. However, we’re leaving the prompts to your interpretation. For example, Monday’s prompt “first time” can be about Tim and Martin’s first time doing anything, like tap dancing. Go wild.

Does it have to focus on martim?  Well, yes. Relationship between Tim and Martin should be central to the submission. It can be explored as romantic or platonic, but it should be at the very centre of the work. We have a prompt for the OG Archival staff, in which you can explore martim in relation to Jon and/or Sasha!

Do I have to do every day if I want to participate? No! You can do one piece for one day and that’s it. You can do multiple things for the same day, just different prompt. 

Who are the organisers of this week? It was born in a wee server, and is now being modded by Zuza @hotjonrights, Lew @twinliches, Lizzie @babyyodablackwood and Cia @mcwebby. 

Where can I direct any further questions? This blog! Otherwise, feel free to message the mods. 

What do you consider an "unhealthy relationship dynamic"? As originally stated in the first answer, depiction of difficult themes is permitted. While "unhealthy" without proper explanation and examples might have been rightly confusing in some aspects, what we, as organisers, meant was that we won't accept any work that centers around difficult themes such as abuse in a fetishistic way. For example, a fic centered around jealousy, poor coping mechanisms or arguments is fine as long as there is understanding of the difference between fetishism and exploration. E.g. a character can experience bad thoughts/emotions and can even act in unhealthy ways, the point its that its explored and not used for shock value/fetish. To expand further, let's say Martin being mean to Tim and cutting him off because he is jealous is an unhealthy and unfair coping mechanism on his part, but once the author writes the part where Tim confronts him/asks him what's wrong/etc. and they talk it through then it's fine. But if the author writes it as resulting in an argument that leads to physical violence/abuse/noncon/etc. then it becomes a completely different thing. Any works that break these rules will not be reblogged here or accepted into the AO3 collection as part of the week. Moreover, expanding on what falls under "unhealthy": big age gaps, teacher/student type of dynamics (which is to say: one party holds an unequal and overwhelming amount of power over the other and exploits it). Additionally, we will not accept Elias/any of the archival staff or Peter/any of the archival staff as minor ships. post edited: 12/01/2021

[mxd113-blog]

Prototyping and Content Creation Team Postmortem

During this month my classmates and I were tasked to work together and complete a game.  This is the team postmortem we made for the game.

The MarTIM Postmortem

  ●      What went wrong?

  Communication

           Communication was one of the bigger struggles we encountered though we always would meet at least once a week, we were unable to use asynchronous communication methods effectively and this caused confusion and slowed production as we would be out of communication for long periods of time that was intended.

   Lack of Vision Coherence

A lack of a cohesive vision caused confusion between the team and in the end, led us a bit astray from the what the original products gameplay and mechanic were supposed to consist of. Some of the design team and art team also suffered from this and art assets were made in a way that initially caused the design team more restrictions that was intended though we managed to get on the same page in the end.

   Resource Management

           We suffered a lot from SourceTree in the beginning. When we tried to upload our individual work to the cloud, those changes conflicted with each other. After our dev team took charge of uploading, things became more organized.

 ●      What went right?

  Jamming

As a team, we decided to have a jam session on Mondays before submissions were due.  The result was a decisive increase in productivity and team cohesion.  The value of working in the same location was not lost on us.  The benefits of synchronous communication and being able to go back and forth on topics where we could look each other’s shoulder allowed us to get most of our systems to a presentable state with a more unified vision.

  Solid Level

Originally, we had wanted to do multiple small levels, but as a team, we decided to go another route. We put aside a solid day and sat together in a meeting room in order to reevaluate the decision, and worked together to instead create one fully functional level for our game. This level is longer and more complete than the original levels we had thought about building first, and than the two levels that we had at the start of week 2. This was a very well done collaborative decision made by the entire team that lead to the profit of our build.

Implemented Feedback

We received a lot of feedback both externally and internally during our development of MarTIM.  With the great opportunity to present at the Student Game Expo, we were able to get a playable build into the hands of players and collect valuable feedback. Reception of our game in its rough, unfinished state was far better than expected and gave us clarity on what aspects were fun and what aspects needed more focus. The rocket fist was an instant hit and an unintended bug that affected traversal was an unlikely source of praise. The feedback we received in class was equally valuable and led to us bringing back a planned feature we had scrapped earlier on in the project’s development: oxygen.

   ●      Conclusion

Overall the time that we put into this game has provided many insights to what it will take to properly handle making a game. From the issues we had with communication we were able to address these issues by implementing a Jam session on Monday’s before turn ins. This way any miscommunications or misunderstandings could be taken care of and squared away before turn-in. We also suffered from the lack of vision cohesion. It became apparent that the separate teams had different needs that weren’t apparent to the other teams and this caused issues through development. Yet, again thanks to the jam sessions and weekly meetings we could refocus and properly address the needs of the teams and individual members. Resource Management was also an issue since many members had little experience with SourceTree. Thankfully over the month we collectively became more comfortable with the SourceTree system. The great source that was feedback also became an important piece of the development cycle. Continued feedback throughout development, helped add many features and in the end improved our final product. We learned much from this game and we hope to take the lessons and experience we gathered to our future products.

[fullsailmistermas-blog]

The MarTIM Team Postmortem

What went wrong?

           1. Communication

           Communication was one of the bigger struggler we encountered though we always would meet at least once a week, we were unable to use asynchronous communication methods effectively and this caused confusion and slowed production as we would be out of communication for longer periods of time that was intended.

              2. Lack of Vision Coherence

             A lack of a cohesive vision caused confusion between the team and in the end led us a bit astray from the what the original products game play and mechanic were supposed to consist of. Some of the design team and art team also suffered from this and art assets where made in a way that initially caused the design team more restrictions that was intended though we managed to get on the same page in the end.

            3. Resource Management

           We suffered a lot from SourceTree in the beginning. When we tried to upload our individual work to the cloud,those changes conflicted with each other. After our dev team took charge of uploading, things became more organized.

 What went right?

                     1. Jamming

                      As a team, we decided to have a jam session on Mondays before submissions were due.  The result was a decisive increase in productivity and team cohesion.  The value of working in the same location was not lost on us.  The benefits of synchronous communication and being able to go back and forth on topics where we could look each other’s shoulder allowed us to get most of our systems to a presentable state with a more unified vision.

                  2.  Solid Level

                 Originally, we had wanted to do multiple small levels, but as a team, we decided to go another route. We put aside a solid day and sat together in a meeting room in order to reevaluate the decision, and worked together to instead create one fully functional level for our game. This level is longer, and more complete than the original levels we had thought about building first, and than the two levels that we had at the start of week 2. This was a very well done collaborative decision made by the entire team that lead to the profit of our build.

                  3. Implemented Feedback

                  We received a lot of feedback both externally and internally during our development of MarTIM.  With the great opportunity to present at the Student Game Expo we were able to get a playable build into the hands of players and collect valuable feedback. Reception of our game in its rough, unfinished state was far better than expected and gave us clarity on what aspects were fun and what aspects needed more focus. The rocket fist was an instant hit and an unintended bug that affected traversal was an unlikely source of praise. The feedback we received in class was equally valuable and led to us bringing back a planned feature we had scrapped earlier on in the project’s development: oxygen.

            Conclusion

            Overall the time that we put into this game has provided many insights to what it will take to properly handle making a game. From the issues we had with communication we were able to address these issues by implementing a Jam session on Monday’s before turn ins. This way any miscommunications or misunderstandings could be taken care of and squared away before turn-in. We also suffered from the lack of vision cohesion. It became apparent that the separate teams had different needs that weren’t apparent to the other teams and this caused issues through development. Yet, again thanks to the jam sessions and weekly meetings we could

[brolol07-blog]

The Martim individual postmortem--Prototyping and content creation

 In the game we as a class thought up of for this month, The MarTim, the game was a simple platformer based on Mars. Being a developer on it, I was tasked with working with the lead developer. The first week, I wanted to get the game engine setup, so we could start developing right away. The lead developer tasked me with getting the Git set up, so I downloaded the newest version of Unity out. I was just excited to get to work on the new project. Due to lack of communication between us, I setup the wrong version of Unity and the lead developer already had his own version control set up. In the future, I will make sure I communicate better with the leads to know exactly what they expect of me and want from me.

In week 2, I was assigned to work on the enemy script, so I did, and the producer and the lead developer was happy about it.

We as a team met several times throughout the weeks, but many teammates weren’t there because they were busy or had prior obligations. To get better work from teammates, I believe it’s vital to have everybody meet in face to know what is going on.

               In week 3, I was instructed to do the UI and projectile and wrote these scripts:

  We had a jamming section on the Monday before Tuesday’s class, that was fun because we finally get to talk and collaborate as a unit.

In the final week, we pulled everything together and consolidated our assets so that the game looks and felt like one solid level. I was instructed to implement the oxygen system for the game and I did it by adding on to the one and creating a separate one for the oxygen tank.

 To conclude what I learned from this experience, I learned communication with the team is very important even for such a small detail, to talk to the leads so they know what your doing and visa versa and to set scope low to get accomplished as much as the team decides. Things that went wrong were not enough communication between leads and their junior developers, that the game is always in flux even though your working on one aspect of it, but not the entire thing and the development of this game was last minute. Conversely, things that went right would be we made a solid level, communication was ok, and I could see this game going somewhere.

[missdasneves]

Today we said goodbye to a few of our friends that will be starting in a new classroom on Monday. Best of luck to Ricardo, Alex, Beatriz, Martim, Lara, Derick and Ms. Vera in their new classes. We will miss you in Room 217, but will see you around the school!